Deploying on WebSphere

This topic describes how to deploy a J2EE application using WebSphere (UNIX and Windows).

Before you begin: Before deploying ENOVIA to an IBM WebSphere Application Server, the Java Virtual Machine memory settings must be set to either “medium-sized” or “large-sized” system settings, as follows:
AIX Operating System
Medium-sized system settings:
-Xss512k -Xmso768k -Xms768m -Xmx1536m -Xcompressedrefs -Xdisableexplicitgc
Large-sized system settings:
-Xss512k -Xmso768k -Xms1024m -Xmx2048m -Xcompressedrefs -Xdisableexplicitgc
LINUX, Solaris and Windows Operating Systems
Medium-sized system settings:
-Xss512k -Xms1536m -Xmx1536m -Xmn512m 
-XX:PermSize=128m -XX:MaxPermSize=128m 
-XX:SurvivorRatio=3 -XX:+DisableExplicitGC 
-XX:+UseCompressedOops
Large-sized system settings:
-Xss512k -Xms2048m -Xmx2048m -Xmn1024m
-XX:PermSize=128m -XX:MaxPermSize=128m -XX:SurvivorRatio=3 
-XX:+DisableExplicitGC -XX:+UseCompressedOops

To set these Java Virtual Machine parameters, you can use WebSphere’s Administration Console and follow the menu selections:

Application Server > SERVER_NAME > process definition > Java virtual machine > Generic JVM arguments.

Once these parameters have been set, and after this WebSphere’s configuration change has been saved, you must restart the Application Server so that these parameters take effect. Only after the Application Server has been re-started can the ENOVIA web application be deployed in the Application Server.

Related Topics
Deploying on Tomcat
Deploying on WebLogic
Deploying on Sun Java System Application Server (UNIX Only)

  1. Start your WebSphere server. For example: 

    ../IBM/HTTPServer/bin/apachectl start
../IBM/WebSphere/AppServer/bin/startServer.sh server1

  2. Start a browser and access http://SERVER_NAME:9060/ibm/console

    Login so that the changes you make are attributed to you.

  3. Expand Applications and click Install New Application.

    If you have previously deployed the ENOVIA application and need to update it, click Enterprise Applicationsand then click ematrix in the list of installed applications.

  4. Select the appropriate file system:


    • If your browser is on the server machine, select Local File System.
    • Otherwise, select Remote File System.

  5. Click the Browse button next to your selection and browse to the path for your .ear file. Select the .ear file and click Open.

  6. Once the page has updated, select Show me all installation options and parameters > Next.

  7. Continue clicking Next until you get to Step 2: Map modules to servers.

  8. On Step 2, select the module (such as ematrix) and continue to click Next until you reach Step 6: Map virtual hosts for Web Modules.

  9. On Step 6, select the module (such as ematrix) and continue to click Next until you reach the summary page. Then click Finish.

  10. When the process finishes, you see a message stating Application ematrix installed successfully.


    • For first-time deployment click the Manage Applications link to continue editing.
    • If you are updating your deployment, click the Save to Master Configuration link.

  11. If you are not already on the page for Enterprise Applications, click Enterprise Applications > ematrix in the list of applications.

  12. Scroll down and click on the Class Loading and update detection link under the Detailed Properties section.

  13. Scroll down to WAR Classloader Policy and select Class loader for each .war file in application (if not already selected). Then click Apply.

  14. When the next page displays, click the Save link at the top of the page and then click the Save button.

  15. Expand Servers, then click on Web Server. Select your web server and click on Propagate Plug-in.

    This generates the plugin-cfg.xml file, with the new web application description as part of the file.

  16. For first time deployment, start the application by clicking Enterprise Applications, selecting the checkbox in front of ematrix, and then clicking the Start button.

  17. If you are using ENOVIA Matrix Web Navigator, open the httpd.conf file in IBMHttpServer/conf/ and comment out the following lines as shown below:

    #AfpaEnable
#AfpaCache on
#AfpaLogFile "C:\IBMHttpServer/logs/afpalog" V-ECLF

  18. Move static pages to the web server by copying the WEBAPPNAME_static.zip file (for example, ematrix_static.zip) from the SERVERHOME/distrib/ directory to the doc root of your web server.

  19. Unzip WEBAPPNAME_static.zip in the doc root.

    The ematrix/ directory is created.

  20. Add an entry for the new directories in plugin-cfg.xml in WEBSPHEREHOME/AppServer/config/cells/. For example:

    <default_host_server1_host_Cluster_URIs">
<Uri Name="/ematrix/*/*.jsp"/>
<Uri Name="/ematrix/servlet/*"/>
<Uri Name="/ematrix/common/*"/>
<Uri Name="/ematrix/*"/>

    Add this entry under <UriGroup Name=>.

  21. Stop and restart the server.