Migration Considerations for XML/SOAP Components

This document applies to EntireX version 8 and above and describes migration steps for the following components:


RPC Server for XML/SOAP

Update the start script to set the paths to current installation. If the properties file contains a path to the configuration file, you may need to adjust the path. The properties and configuration files can be used as before. See Configuration File in the RPC Server for XML/SOAP documentation for more information.

XML/SOAP Wrapper

Update the start script to set the paths to current installation.

Listener for XML/SOAP

The migration steps depend on the Web server you are using:

  • Using the Software AG Web Server based on Apache Tomcat / Software AG Runtime from Software AG Installation
    Save your Web services (AAR files) and modified configuration files (that is, axis2.xml). You do not need to re-generate your Web services (AAR files). If the configuration was modified, perform the same modifications for the new installation and restart Software AG Web Server. Redeploy the web services (AAR files).

    Note:
    The new installation will use another port by default, which means that the Web clients need to be adjusted.

  • Using another Web Server
    Save your Web services (AAR files) and modified configuration files (that is, axis2.xml). You do not need to re-generate your Web services (AAR files). For deployment of file wsstack.war and copying file entirex.jar to Web Services Stack, see the separate Web Services Stack documentation in the Software AG Infrastructure Administrator's Guide, also available under http://documentation.softwareag.com > Guides for Tools Shared by Software AG Products.

    If configuration was modified, perform the same modifications for new installation and restart the Web server. Redeploy the Web services (AAR files).