From time to time, you may encounter some limitations in using the deployment tools. In most situations, you can successfully work around these limitations.
Some known limitations are:
These limitations are discussed in the following sections.
In this release of WebSphere Integration Developer, the module deployment editor enables a user to configure WS-Security deployment options on Web service exports and imports. The data associated with the configured deployment options is stored in a deployment side file named ibm-deploy.scaj2ee, which is located in the root of the SCA module in the Physical Resources view of the Business Integration perspective. For example, MyModule/ibm-deploy.scaj2ee. The deployment side file can contain binding information, such as the port name and address of Web service imports and the port name and service name of Web service exports.
If the binding information of a Web service import or export is changed, then the copy of this binding data in the deployment side file will be invalidated. For example, if you manually change the address of a Web service import in the assembly diagram of the associated module, the binding data in the deployment side file will not reflect the new address of the Web service import.
To ensure that the deployment side file reflects any binding changes to your Web service imports or exports, you must open the deployment side file in a text editor and then manually update the deployment information to reflect the changes to the binding information.
If your Web services are unable to interoperate with .NET services, you may need to recreate your Web service proxies to work with .NET services as described in the topic "Creating proxies to work with .NET services."
If you are experiencing authorization exceptions when you start a server in WebSphere® Integration Developer, it is most likely because security is enabled for the server and the server connection type is RMI rather than SOAP. If you want to avoid authorization exceptions when you run your server, you must either change your server connection type to SOAP or disable security for the server. These tasks are described in the following steps:
In the test environment of WebSphere Integration Developer, you can choose to have your test environment server run your modules and resources in one of the following two ways.
These two ways of running your modules and resources are controlled by the Run server with resources within the workspace and Run server with resources on Server radio buttons respectively in the server configuration editor.
If the default Run server with resources within the workspace radio button is selected and you are thus running your server using the current modules and resources in your workspace, any relationship role tables will be automatically dropped as required when you remove your application from the server. However, if the Run server with resources on Server radio button is selected and you are thus running your server using an EAR file that contains a copy of the modules and resources in your workspace, the relationship role tables are not automatically dropped and you will need to manually drop them as needed.
Information about limitations and restrictions for the server tools is found in the Rational® Application Developer topic "Server tools limitations and restrictions."