Draft Document for Review July 28, 2004 7:33 pm

6320ch_DEV_post_migration.fm

Any code, referring to the types using the old package names must be updated to work with WebSphere Commerce V5.6.

8.2.10 Rule server administration commands

A number of changes have been made to the structure and behavior of the rule service administration commands. Refer to Migration Guide for WebSphere Commerce Developer - migrating from WebSphere Commerce Studio V5.1 for details about the changes.

8.2.11 JSP and property file changes

Several improvements have been done to the login and register functionality. These improvements are reflected in new error codes which the JSPs must be able to deal with. For our example the new changes are split up in three sections:

1.Dealing with new error codes for logging in. This is dealt with in file myAccount.jsp

2.Dealing with new error codes when registering. This is dealt with in file register.jsp

3.Adding text for the new error codes for logging in and registering. This is dealt with in file user_text_en_US.properties

Note: The changes applied to the JSP files below are examples from our store which is based on the WebSphere Commerce Suite V5.1 sample store InFashion. For other stores the filenames may differ.

Refer to the WebSphere Commerce V5.6 InfoCenter under the relevant commands and their error codes to ensure that all necessary changes are applied.

Changes to myAccount.jsp

Several new error codes has been added to WebSphere Commerce V5.6 during login. To be able to deal with the new error codes, the file myAccount.jsp must be modified. In our example myAccount.jsp does not handle these new error codes and needs to be modified in order to display the error messages to the user during failed login.

To JSP file myAccount.jsp located in:

<was5_home>\installedApps\hostname\app_name\Stores.war\store_name

in our example:

Chapter 8. Post-migration steps

155

Page 173
Image 173
IBM SG24-6320-00 Rule server administration commands, JSP and property file changes, Changes to myAccount.jsp, Our example