Renaming an alias name after you install Mod Pack 3

If you installed WebSphere Commerce Version 8 Mod Pack 3 (8.0.3.0), then you need to update an alias name.

Note: You need to complete this procedure only if you installed Mod Pack 3 (8.0.3.0). The alias name ForceHttps was renamed to StoreServer in the AliasConfig.xml file. Therefore, you need to update some store files to synchronize with the new change.

If you do not complete this procedure, then you might encounter aliasName errors during storefront service requests. For example,

[10/5/16 16:03:40:304 EDT] 00000187 AliasTag      1 com.ibm.commerce.foundation.internal.client.taglib.AliasTag setAlias(String aliasName) aliasName: ForceHttps
[10/5/16 16:03:40:304 EDT] 00000187 AliasTag      1 com.ibm.commerce.foundation.internal.client.taglib.AliasTag setVar(String var) var: forceHttps
[10/5/16 16:03:40:304 EDT] 00000187 SystemErr     R   java.lang.NullPointerException
[10/5/16 16:03:40:305 EDT] 00000187 SystemErr     R       at com.ibm.commerce.foundation.internal.client.taglib.AliasTag.getClassConfig(AliasTag.java:322)
[10/5/16 16:03:40:305 EDT] 00000187 SystemErr     R       at com.ibm.commerce.foundation.internal.client.taglib.AliasTag.doEndTag(AliasTag.java:218)

Procedure

In your WebSphere Commerce Developer environment, open the following files in an editor.
- WCDE_installdir/workspace/Stores/WebContent/storedir/Common/EnvironmentSetup.jspf
- WCDE_installdir/workspace/Stores/WebContent/storedir/Widgets/Header/Header_Data.jspf
- WCDE_installdir/workspace/Stores/WebContent/storedir/Widgets/Header/DepartmentDropDown.jsp
In each file, find <wcst:alias name="ForceHttps" var="forceHttps" /> and replace the alias name "ForceHttps" with "StoreServer".
The result is
```
<wcst:alias name="StoreServer" var="forceHttps" />
```
Deploy the updated files to your production environment.