Assembling and Deploying Your ATG Applications

Follow the instructions below for the application server you are using to assemble and deploy the ATG publishing and production server instances.

WebLogic

To assemble and deploy your ATG applications on WebLogic:

  1. In the CIM MAIN MENU, select [3] Application Assembly & Deployment.

  2. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [A] ATGProduction - Production with a Server Lock Manager.

  3. In the ENTER EAR FILE NAME(S) menu, enter the name ATGProduction.ear.

  4. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [D] Deploy Production with a Server Lock Manager ATGProduction.ear to Weblogic Online.

  5. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [R] Register Datasources on WebLogic Online.

  6. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.

  7. In the WEBLOGIC CLASSPATH MODIFICATION menu, select [U] Update the <WebLogic_user_domain>/bin/setDomainEnv.sh file.

  8. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [P] Post Deployment Actions on WebLogic Online.

  9. In the POST DEPLOYMENT OPTIONS menu, select [W] Weblogic JVM Optimization.

  10. In the WEBLOGIC JVM OPTIMIZATION menu, select [U] Update the initial and maximum heap size values in the following start up files.

  11. In the POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar.

  12. In the WEBLOGIC POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar to Production with a Server Lock Manager ATGProduction.ear to Weblogic Online.

  13. In the POST DEPLOYMENT OPTIONS menu, select [D] Done.

  14. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [O] Configure Another Server Instance.

  15. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [P] ATGPublishing - Publishing with a Server Lock Manager.

  16. In the ENTER EAR FILE NAME(S) menu, enter the name ATGPublishing.ear for the ATG Commerce Store Production with Server Lock Manager.

  17. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [D] Deploy Publishing with a Server Lock Manager ATGPublishing.ear to Weblogic Online.

  18. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [R] Register Datasources on WebLogic Online.

  19. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.

  20. In the WEBLOGIC CLASSPATH MODIFICATION menu, select [U] Update the [WebLogic_domain]/bin/setDomainEnv.sh file.

  21. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [P] Post Deployment Actions on WebLogic Online.

  22. In the POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar.

  23. In the WEBLOGIC POST DEPLOYMENT OPTIONS menu, select [C] Copy protocol.jar to Publishing with a Server Lock Manager ATGPublishing.ear to Weblogic Online.

  24. In the POST DEPLOYMENT OPTIONS menu, select [D] Done.

  25. In the WEBLOGIC ONLINE DEPLOYMENT MENU, select [O] Configure Another Server Instance.

  26. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [D] Done.

  27. In the CIM MAIN MENU, enter q to exit CIM.

  28. Continue with the section Starting the Publishing and Production Servers.

JBoss

To assemble and deploy your ATG applications on JBoss:

  1. In the CIM MAIN MENU, select [3] Application Assembly & Deployment.

  2. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [A] ATGProduction - Production with a Server Lock Manager.

  3. In the ENTER EAR FILE NAME(S) menu, enter the name ATGProduction.ear.

  4. In the SELECT JBOSS SERVER TO USE menu, select [C] CIM should create a new server for me.

  5. In the SELECT JBOSS SERVER TEMPLATE TO USE menu, select [D] default.

  6. Accept the default, ATGProduction, for the JBoss server name.

  7. In the JBOSS DEPLOYMENT MENU, select [D] Deploy Production with a Server Lock Manager ATGProduction.ear to JBoss.

  8. In the JBOSS DEPLOYMENT MENU, select [R] Register Datasources on JBoss.

  9. In the JBOSS DEPLOYMENT MENU, select [A] Add database driver to app server classpath.

  10. In the JBOSS JDBC DRIVER JAR COPY menu, select [C] Copy file.

  11. In the JBOSS DEPLOYMENT MENU, select [P] Post Deployment Actions on JBoss.

  12. In the POST DEPLOYMENT OPTIONS menu, select [J] JBoss JVM Optimization.

  13. In the JBOSS JVM OPTIMIZATION menu, select [U] Update JBoss run.conf file.

    Note: On Windows, this step is called [U] Update JBoss run.conf.bat file.

  14. In the POST DEPLOYMENT OPTIONS menu, select [D] Done.

  15. In the JBOSS DEPLOYMENT MENU, select [O] Configure Another Server Instance.

  16. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [P] ATGPublishing - Publishing with a Server Lock Manager.

  17. In the ENTER EAR FILE NAME(S) menu, enter the name ATGPublishing.ear.

  18. In the SELECT JBOSS SERVER TO USE menu, select [C] CIM should create a new server for me.

  19. In the SELECT JBOSS SERVER TEMPLATE TO USE menu, select [D] default.

  20. Accept the default, ATGPublishing, for the JBoss server name.

  21. In the JBOSS DEPLOYMENT MENU, select [D] Deploy Publishing with a Server Lock Manager ATGPublishing.ear to JBoss.

  22. In the JBOSS DEPLOYMENT MENU, select [R] Register Datasources on JBoss.

  23. In the JBOSS DEPLOYMENT MENU, select [A] Add database driver to app server classpath.

  24. In the JBOSS JDBC DRIVER JAR COPY menu, select [C] Copy file.

  25. In the JBOSS DEPLOYMENT MENU, select [P] Post Deployment Actions on JBoss.

  26. In the POST DEPLOYMENT OPTIONS menu, select [D] Done.

  27. In the JBOSS DEPLOYMENT MENU, select [O] Configure Another Server Instance.

  28. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [D] Done.

  29. In the CIM MAIN MENU, enter q to exit CIM.

  30. Continue with the section Starting the Publishing and Production Servers.

WebSphere

  1. In the CIM MAIN MENU, select [3] Application Assembly & Deployment.

  2. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [A] ATGProduction - Production with a Server Lock Manager.

  3. In the ENTER EAR FILE NAME(S) menu, enter the name ATGProduction.ear for the Production with a Server Lock Manager ear file.

  4. Select [2] <host>Node01 for the node.

  5. In the SELECT WEBSPHERE SERVER TO USE menu, select [C] CIM should create a new server for me.

  6. Accept the default, ATGProduction, for the WebSphere server name.

  7. In the WEBSPHERE DEPLOYMENT MENU, select [D] Deploy Production with a Server Lock Manager ATGProduction.ear to WebSphere.

  8. In the WEBSPHERE DEPLOYMENT MENU, select [R] Register Datasources on WebSphere.

  9. In the WEBSPHERE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.

  10. In the WEBSPHERE APP SERVER CLASSPATH menu, select [C] Continue.

  11. In the WEBSPHERE DEPLOYMENT MENU, select [O] Configure Another Server Instance.

  12. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [P] ATGPublishing - Publishing with a Lock Server.

  13. In the ENTER EAR FILE NAME(S) menu, enter the name ATGPublishing.ear for the Publishing with a Server Lock Manager ear file.

  14. Select [2] <host>Node01 for the node.

  15. In the SELECT WEBSPHERE SERVER TO USE menu, select [C] CIM should create a new server for me.

  16. Accept the default, ATGPublishing, for the WebSphere server name.

  17. In the WEBSPHERE DEPLOYMENT MENU, select [D] Deploy Publishing with a Server Lock Manager ATGPublishing.ear to WebSphere.

  18. In the WEBSPHERE DEPLOYMENT MENU, select [R] Register Datasources on WebSphere.

  19. In the WEBSPHERE DEPLOYMENT MENU, select [A] Add database driver to app server classpath.

  20. In the WEBSPHERE APP SERVER CLASSPATH menu, select [C] Continue.

  21. In the WEBSPHERE DEPLOYMENT MENU, select [O] Configure Another Server Instance.

  22. In the DEPLOYMENT SERVER INSTANCE SELECTION menu, select [D] Done.

  23. In the CIM MAIN MENU, enter q to exit CIM.

  24. Continue with the section Setting DeploymentManager Properties (DB2 Only)

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved.

Legal Notices