Calling services from a remote client
Making a service implementation accessible for a client application in a service oriented architecture. The method may include extracting an interface definition language file from the service implementation, which defines the interface information to be provided by the client application to access the service implementation during runtime. The method may further include extracting a server-side mapping file from the service implementation, which defines how the interface information provided by the client application is mapped when accessing the service implementation during runtime.
1. A method for making a service implementation accessible for a client application in a service oriented architecture, the method comprising:
utilizing a computer to perform:
extracting and storing an interface definition language (IDL) file from the service implementation, wherein the service implementation is a pre-existing server program in the service oriented architecture, wherein the IDL file defines interface information to be provided by the client application to access the service implementation during runtime; and
extracting and storing a server-side mapping file from the service implementation, wherein the server-side mapping file defines how the interface information provided by the client application is mapped when accessing the service implementation during runtime;
wherein the IDL file and the server-side mapping file are used to perform client communication with the service implementation without requiring changes to the pre-existing server program; and
wherein said extracting the IDL file and/or extracting the server-side mapping file from the service implementation comprises using an extractor wizard for extracting necessary information for generating the interface definition language file and/or the server-side mapping file, wherein said using the extractor wizard comprises presenting a mapping editor to a user.
2. The method of claim 1 , wherein the interface information provided by the client application is mapped to a format required by the service implementation.
3. The method of claim 2 , wherein the server-side mapping file comprises a mapping from parameter and data-type information comprised in the interface definition language file to the parameters and data-types expected by the service implementation.
4. The method of claim 1 , wherein the service implementation is implemented in a 3GL programming language.
5. The method of claim 1 , wherein the service implementation is implemented in the programming language COBOL.
6. The method of claim 1 , wherein a remote procedure call server has access to the server-side mapping file in order to call the service implementation using the server-side mapping file during runtime.
7. The method of claim 6 , wherein the server-side mapping file is accessible for the remote procedure call server by a deployment wizard.
8. The method of claim 6 , wherein the server-side mapping file is accessible for the remote procedure call server using FTP and a IDCAMS utility.
9. The method of claim 1 , further comprising:
receiving a remote call with interface information from the client application, wherein the remote call is in accordance with an interface definition language file for the service implementation;
mapping the interface information provided in the remote call according to the mapping described in a server-side mapping file; and
executing a service implementation using the mapped interface information.
10. The method of claim 9 , wherein said receiving is performed by a remote procedure call server and wherein the method further comprises:
the remote procedure call server calling the service implementation for execution after mapping the interface information according to the server-side mapping file.
11. The method of claim 1 ,
wherein the interface definition language file and the server-side mapping file are useable to enable the client application created in a first programming language to interface to the server implementation created in a second programming language.
12. A non-transitory computer-accessible memory medium comprising program instructions for making a service implementation accessible for a client application in a service oriented architecture, wherein the program instructions are executable to:
extract an interface definition language file from the service implementation, wherein the service implementation is a pre-existing server program in the service oriented architecture, wherein the IDL file defines interface information to be provided by the client application to access the service implementation during runtime; and
extract a server-side mapping file from the service implementation, wherein the server-side mapping file defines how the interface information provided by the client application is mapped when accessing the service implementation during runtime;
wherein the interface definition language file and the server-side mapping file are useable to enable the client application created in a first programming language to interface to the server implementation created in a second programming language without requiring changes to the pre-existing server program; and
wherein said extracting the IDL file and/or extracting the server-side mapping file from the service implementation comprises using an extractor wizard for extracting necessary information for generating the interface definition language file and/or the server-side mapping file, wherein said using the extractor wizard comprises presenting a mapping editor to a user.
13. The non-transitory memory medium of claim 12 , wherein the interface information provided by the client application is mapped to a format required by the service implementation.
14. The non-transitory memory medium of claim 13 , wherein the server-side mapping file comprises a mapping from parameter and data-type information comprised in the interface definition language file to the parameters and data-types expected by the service implementation.
15. The non-transitory memory medium of claim 12 , wherein the service implementation is implemented in a 3GL programming language.
16. The non-transitory memory medium of claim 12 , wherein the service implementation is implemented in the programming language COBOL.
17. The non-transitory memory medium of claim 12 , wherein a remote procedure call server has access to the server-side mapping file in order to call the service implementation using the server-side mapping file during runtime.
18. The non-transitory memory medium of claim 12 , wherein the program instructions are further executable to:
receive a remote call with interface information from the client application, wherein the remote call is in accordance with an interface definition language file for the service implementation;
map the interface information provided in the remote call according to the mapping described in a server-side mapping file; and
execute a service implementation using the mapped interface information.
19. A system for making a service implementation accessible for a client application in a service oriented architecture, the system comprising:
a processor;
a memory medium coupled to the processor, wherein the memory medium stores:
a. a first extractor unit extracting an interface definition language file from the service implementation, wherein the service implementation is a pre-existing server program in the service oriented architecture, wherein the IDL file defines interface information to be provided by the client application to access the service implementation during runtime;
b. a second extractor unit extracting a server-side mapping file from the service implementation, wherein the server-side mapping file defines how the interface information provided by the client application is mapped when accessing the service implementation during runtime;
wherein the IDL file and the server-side mapping file are used to perform client communication with the service implementation without requiring changes to the pre-existing server program; and
wherein the first and/or the second extractor unit further comprises an extractor wizard for extracting necessary information for generating the interface definition language file and/or the server-side mapping file, wherein the extractor wizard comprises a mapping editor adapted to be presented to a user during the generation of the interface definition language file and/or the server-side mapping file.
20. The system according to claim 19 , wherein the first and/or the second extractor unit are configured to analyse source code of the service implementation and determining settings and/or input and output parameters.
21. The system according to claim 19 , further comprising a remote procedure call server adapted to access the server-side mapping file in order to call the service implementation using the server-side mapping file during runtime.