Deprecated feature

Disabling the separation of a separated store archive

If you no longer want the store archive for your site to be separated from the WebSphere Commerce EAR, you can undo the store separation process. After you complete this process, your site uses the original store web archive (WAR) within the WebSphere Commerce EAR.

Procedure

  1. Uninstall the new store EAR from your system.
    If you created a backup of your WebSphere Application Server administrative configuration and assets before you separated your store archive, you can recover this backup to restore your initial WebSphere Commerce application configuration. For more information, see Backing up and recovering the application server environment
    1. Open the WebSphere Integrated Solutions Console.
    2. Expand Applications > Application Types. Click WebSphere enterprise applications.
    3. In the list of Enterprise Applications, select the check box for the WebSphere Commerce server and store application. Click Stop.
    4. Select the check box for the store application, for example WCStores_instance_name. Click Uninstall > OK.
    5. Click Save directly to the master configuration.
  2. Enable the original store WAR within the WebSphere Commerce EAR.
    1. In the Enterprise Applications page of the WebSphere Application Server admin console, click your WebSphere Commerce application.
      For example, your application can be named WC_instance_name.
    2. In the Modules section, click Manage Modules.
    3. Ensure that your Stores module maps to both the WebSphere Application Server, server1, and your web server, webserver1.
      If your module does not map to both servers,
      1. Select the check box for your Stores module.
      2. In the Clusters and servers: input field, set the module to map to both servers. Enter the following into the input field and click Apply.
        WebSphere:cell=WC_demo_cell,node=WC_demo_node,server1
        WebSphere:cell=WC_demo_cell,node=WC_demo_node,webserver1
        
        Where server1 and webserver1 are the names of your servers.
      3. Click Save directly to the master configuration.
    4. In the Enterprise Applications page, click your WebSphere Commerce application.
    5. In the section, click Context Root for Web Modules.
    6. Change the context root for your application to be the correct path.
    7. Click Save directly to the master configuration.
  3. Delete you custom class loader.
    1. In the WebSphere Application Server admin console, expand Servers > Server Types. Click WebSphere application servers.
    2. Click your WebSphere Application Server.
      For example, server1.
    3. In the Server Infrastructure section, expand Java and Process Managemenet. Click Class loader.
    4. Select the check box for your custom class loaders. Click Delete.
    5. Click Save directly to the master configuration.
  4. Remove the shared library.
    1. In the WebSphere Application Server admin console, expand Environment. Click Shared libraries.
    2. Select the check box for your custom asset shared library, Customer_shared_lib, and the default shared library, Shared_lib. Click Delete.
    3. Click Save directly to the master configuration.
  5. Update the configuration file for the web server to map the WebSphere Commerce store alias to the store WAR within the WebSphere Commerce EAR.
    • IBM HTTP Server
      1. Go to the following directory in your file manager:
        • SolarisLinuxAIXFor IBM i OS operating systemWC_installdir/instance/instance_name/httpconf
        • WindowsWC_installdir\instance\instance_name\httpconf
      2. Open the httpd.conf configuration file for editing.
      3. Locate the wcsstore alias mapping in the file:
        Alias/wcsstore "WAS_installdir/profiles/demo/installedApps/WC_instance_name_cell/
        WCStores_instance_name.ear/Stores.war"
        Change the value for the wcsstore alias to be the path to the store WAR location within the WebSphere Commerce EAR. For example:
        Alias/wcsstore	"WAS_installdir/profiles/demo/installedApps/WC_instance_name_cell/
        WC_instance_name.ear/Stores.war"
    • Sun ONE web server
      1. In your file manager, Locate and open the obj.conf web server configuration file for editing.
      2. Locate the following code:
        NameTrans fn="pfx2dir" from="/wcsstore" dir="WAS_installdir/profiles/instance_name/installedApps/
        WC_instance_name_cell/WCStores_instance_name.ear\Stores.war "
      3. Update the configuration to map to the store WAR location within the WebSphere Commerce EAR:
        NameTrans fn="pfx2dir" from="/wcsstore" dir="WAS_installdir/profiles/instance_name/installedApps/
        WC_instance_name_cell/WC_instance_name.ear/Stores.war"
    • WindowsInternet Information Services (IIS) Manager web server
      In the IIS Manager, change the value for the physical path to the WebSphere Commerce store, wcsstore, from the following path:
      WAS_installdir\profiles\instance_name\installedApps\WC_instance_name_cell\
      WCStores_instance_name.ear\Stores.war
      To be the path to the store WAR location within the WebSphere Commerce EAR. For example:
      WAS_installdir\profiles\instance_name\installedApps\WC_instance_name_cell\
      WC_instance_name.ear\Stores.war"
  6. Regenerate the WebSphere Application Server web server plug-in configuration file.
  7. Optional: If your web server is remote and the plugin-cfg.xml file is changed, Copy the new generated plugin-cfg.xml file to your remote web server.
  8. Update the SRCHCONFEXT table to ensure that the web content index points to the new store WAR location in the WebSphere Commerce EAR.
    1. Open a connection to the WebSphere Commerce database.
    2. Run the following SQL statement to update the path to Stores.war archive:
      update srchconfext set config='SearchServerName=commerce.wttedns01.usri.ibm.com,BasePath=WAS_installdir\profiles\
      instance_name\installedApps\WC_instance_name_cell\WC_instance_name.ear\Stores.war\
      Aurora\StaticContent\en_US\,SearchServerPort=3737,StoreId=10101' where INDEXSUBTYPE='WebContent'
  9. Restart the WebSphere Application Server.
  10. Restart the web Server.