Although the primary method of publishing a store archive is through the Administration Console, you can also publish a store archive using the command line.
To publish using the command line, do the following:
- Ensure that you have Site Administrator access.
At an AIX command line, type:
cd /usr/WebSphere/CommerceServer55/bin
At a Solaris or Linux command line, type
cd /opt/WebSphere/CommerceServer55/bin
At the iSeries qsh command line, type
cd /QIBM/ProdData/CommerceServer55/binThen, type:
./publishstore.sh hostname userId password storeArchiveFilename
where:
- hostname
- is the fully qualified TCP/IP name of your WebSphere Commerce Server and the tools port number (optional) for your instance. You can find the tools port number in the Configuration Manager, under Instance properties> WebSphere. By default this is hostname:8000.
- userId
- is the user ID for the Site Administrator. You must have Site Administrator access to publish a store archive.
- password
- is Site Administrator's password for WebSphere Commerce.
- storeArchiveFilename
- is full path of the store archive on the host machine. For example,
/usr/CommerceServer/samplestores/ConsumerDirect/ConsumerDirect.sar
/QIBM/ProdData/CommerceServer55/samplestores/ConsumerDirect/ConsumerDirect.sar
- Open Internet Explorer. Go to the following Web address:
http://hostname/webapp/wcs/stores/store directory/index.jsp
Your store displays.
Note: Compiling the JavaServer Pages (JSP) files in your site or store before launching it will significantly reduce the amount of time needed to load each store page. As a result, it is recommended that you batch compile your store or sites JSP files after publishing a store archive. To batch compile the store's JSP files, see Compiling your JavaServer Page files.
If you publish the B2B Direct store archive (ToolTech), you must stop and restart the commerce server before viewing the store, or the registration page will not display properly. For more information, see Starting and stopping WebSphere Commerce. In order to prevent unnecessary exceptions displaying, delete the SendTransactionMsg job from the scheduled jobs. For more information, see Deleting a scheduled job.
- In order to enable caching in the sample stores, you must merge the
cachespec.xml file from the following directory:
WAS_installdir/samples/dynacache/businessmodelname
WAS_user_dir/Base/WAS_instance_name/installedApps/ cellname/WC_instance_name.ear/
Stores.war/WEB-INFwith the cachespec.xml file in the following directory:
WAS_installdir/installedApps/hostname/WC_ instancename.ear/Stores.war/WEB-INF
WAS_user_dir/InstalledApps/ hostname/WC_instancename.ear/Stores.war/WEB-INF You must edit the existing cachespec.xml file in the WEB-INF directory with the changes in the first file, rather than replace it.
If you have problems displaying your store, see Troubleshooting publishing.
Important:
- If you are running your Web server on a separate node than the WebSphere Commerce node, complete the following steps after publishing a store archive:
- If you change the Web application Context path, you must ensure that it matches the path defined in the WebSphere Commerce Server.
- Only one store archive at a time can be published.
- When you launch the FashionFlow store from Administration Console, you are logged into the store with the same user name and password that you used to log into Administration Console. If you change your password in the store, you are also changing it for Administration Console. Instead, to test the features in the store, including changing your password, save the site address, close all browser windows, then log on to the store again. For more information, see Limitations when using multiple browsers windows.
- If you are logged in as the default administrator, you cannot browse a store based on the B2B direct sample store (ToolTech). Instead create a new user that belongs to the default organization, then browse the store.
- If you plan to make changes to your JSP files after publishing your store, you should disable servlet caching in the WebSphere Application Server. For more information see the "Dynamic caching" chapter in the WebSphere Commerce Administration Guide. If you are using WebSphere Commerce Studio, the servlet caching is disabled by default.