Publishing a store archive using the publishstore utility
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. Only one store can be published at a time.
Important:
- If you change the Web application Context path, you must ensure that it matches the path defined in the WebSphere Commerce Server.
- When you open a 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 Site Administrator, you cannot browse a store based on the Deprecated featureadvanced B2B direct starter store. 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.
If you are using WebSphere Commerce development environment, the servlet caching is disabled by default.
Procedure
What to do next
- If you are publishing your version 7 store
into the same environment as a previously migrated version 5.6.1 store,
you see a warning message. The migrated version 5.6.1 environment
has the JSTL Expression Language (EL) set to ignore.
Your application currently has the JSTL Expression Language (EL) feature disabled, any starter stores that are ready for this feature will not function correctly. Refer to the online documentation on how to correct this behavior. Do you want to continue with the store publish?
To use the new store, first enable EL, then publish the store.Note: Changing this setting allows your version 7 store to function correctly, but will prevent your 5.6.1 store from working until you migrate your JSP files, described in step c.To enable EL:- Edit the following two files:
- WAS_installdir/profile/profile_name/installedApps/cell_name/EAR_name/Stores.war/WEB-INF/web.xml
- WAS_installdir/profile/profile_name/config/cells/cell_name/applications/EAR_name/deployments/application_name/Stores.war/WEB-INF/web.xml
<jsp-property-group> <url-pattern>*.jsp</url-pattern> <el-ignored>true</el-ignored> </jsp-property-group>
- Restart your WebSphere Commerce server.
- To use the old WebSphere Commerce version 5.6.1 store and the new version 7.0 store concurrently, you must migrate the old 5.6.1 store JSP files in your development environment. To migrate your JSP files, see Migrating JSP files and store properties files.
- Edit the following two files: