JAX-RPC web services consist of one or more bundles, deployed
within a CBA and an EAR.
Before you begin
To use JAX-RPC web services, both of these parts must be deployed
in addition to the CBA containing the development project.
Procedure
- Deploy the CBA. For more information, see ../com.ibm.mdmhs.wb.tools.models.doc/c_Addition_and_Extension_Deployment_in_OSGi_Framework.html
- Uninstall the existing JAX-RPC web services EAR that was
installed with the product to allow you to replace it with the newly
generated EAR.
- Open the IBM® WebSphere® Application Server admin
console
- Select .
- Select the checkbox next to MDM-old-web-services-xxxx and
click Uninstall.
- Deploy the JAX-RPC Web Services CBA project (default name WSCBA). For more information, see Deploying a CBA to the operational server from the MDM Workbench or Deploying a CBA to the operational server from IBM WebSphere Application Server admin console
- Update the JAX-RPC EAR security settings
- Within the JAX-RPC EAR project, open the file META-INF/ibm-application-bnd.xml.
- In the Design tab, click .
- Run As (mdmadmin).
- In the right-hand panel, set the Password to
your mdmadmin password.
- Save and close the file.
- Right-click on the JAX-RPC EAR project, then click .
- Deploy the JAX-RPC EAR project to the server, either through
the Servers view in the MDM Workbench or
through the IBM WebSphere Application Server admin
console.
Note: When using the MDM Workbench in IBM Rational® Application Developer version
8.5.1, the Prepare for Deployment operation
does not generate all of the required artifacts for the web services.
In this case, the JAX-RPC web services EAR must be deployed through
the IBM WebSphere Application Server admin
console. To do this, take the following steps:
- Ensure the maximum heap size of the server is set to
at least 1GB; otherwise out-of-memory errors are likely to occur during
deployment
- Export the EAR from the workspace.
- Install the EAR through the IBM WebSphere Application Server admin
console, enabling the deploy web services in
the installation options.
- Restart IBM WebSphere Application Server.