Hybrid Integration 10.1 | Integrating On-Premises Applications | Document Conventions | Building Java Services in Your Own IDE
 
Building Java Services in Your Own IDE
 
How Java Services are Organized on Integration Server
Requirements for the Java Service Source Code
IData Object for Java Service Input and Output
Adding Comments to Your Java Code for the jcode Utility
Using the jcode Utility
As an alternative to creating Java Services using the Designer Java Service Editor, you can use your own IDE.
Note: For information about creating Java services using Designer, see Building Java Services.
When you use your own IDE, you must create the Java code yourself, compile it, and store the compiled class file and other service information in Integration Server. To help you with these tasks, Integration Server provides the jcode utility.
The following describes the basic steps for building a Java service with your own IDE.
1. Understand how Java service are stored in Integration Server. For a description, see How Java Services are Organized on Integration Server .
2. Optionally create an empty Java service using Designer that you can use as a guideline for coding your own service. For more information, see Building Java Services.
3. Write the Java code for your service using your own IDE.
*Define the input and output parameters for the service. The service must use an IData object for service input and output. For more information, see IData Object for Java Service Input and Output.
*Ensure your code meets requirements described in Requirements for the Java Service Source Code.
*Add comments to the code that identify various fragments, for example, imports or service inputs and outputs. For more information, see Adding Comments to Your Java Code for the jcode Utility. These comments are used by the jcode utility, which you use in the next step.
4. Use the jcode utility to compile the Java service and store its service information in Integration Server.
5. Reload the package to load the compiled Java service into memory so that it is executable.
Copyright © 2015- 2017 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.