Calling Integration Server Services from Application Platform Projects

webMethods and Intelligent Business Operations 10.2 | Designing and Implementing Composite Applications | webMethods Application Platform User’s Guide | Developing with Application Platform in Designer | About Using Services in Application Platform | Calling Integration Server Services from Application Platform Projects

Coding Considerations

You can expose your Integration Server Java services and Integration Server flow services to your Application Platform projects. Java source file binding classes are code-generated to facilitate calling the IS services.

In Application Platform, you can create Java source files that are essentially client stubs used to invoke Integration Server Java services and Integration Server flow services from an Application Platform project.

To call Integration Server services from your Application Platform project:

1. Right-click your project and select App Platform, and then select IS Tools.

2. Click IS Service Wizard.

Note: You can also launch the IS Service Wizard by pressing Ctrl+Shift+Z.

3. Select a destination project from the Project drop-down list box.

You can select only projects with an enabled IS Service Extensions project facet.

4. Select the required IS services. If you see no IS services, or less IS services than you expect, try one of the following:

Right-click the required node and click

Right-click the required node and click Refresh tree contents.

You can select one or more IS services. You must use only user-developed services with valid IO specifications.

Note: None of the Integration Server product services, contained in packages that begin with Wm*, are visible in the wizard. Therefore, you will see no services for selection before you have created at least one custom service.

5. Click Finish.

Java bindings are created for the selected IS services. You can find the source files in the source directory, as defined for the IS Service Extensions project facet. The default location is genSource. The package name is determined from the IS service and its parent folder name(s). Each IS service you select has its own dedicated Java package. This ensures that there is no overlap with the generated input and output classes.

Important: If you deploy a project that calls IS services to the production server, you must set the generated source directory to src/main/java.