Creating a Customized Deployment jar for Disconnected Installer
After adding a new language on the web server, the disconnected installer must be customized. The customized code that was added on the web server must be packaged for deployment onto each disconnected system. For language customizations, you must package all of the newly added. json files, all of the new .class files that were generated by compiling the .java resource files, and all the .ser files that were created after compiling the rbInfo files.
1. Create a jar or zip with relative paths. For example, if you have customized following files:
◦ <WT_HOME>/codebase.war/delivery/app/translations/el_GR.json
◦ <WT_HOME>/src/com/ptc/sc/resource/SCEnterpriseAttributesRB_el_GR.java
◦ <WT_HOME>/src/com/ptc/sce/cart/LWCSCEShoppingCartModelRB_el_GR.rbInfo
The artifacts to be deployed would be the .json file, the .class file and the .ser file respectively.
2. Zip these three files into a jar or zip file to be included in customized disconnected installer.
For example InService_Greek_Language_cust.zip which contains following files:
◦ codebase.war/delivery/app/translations/el_GR.json
◦ codebase.war/WEB-INF/classes/com/ptc/sc/resource/SCEnterpriseAttributesRB_el_GR.class
◦ codebase.war/com/ptc/sce/cart/LWCSCEShoppingCartModelRB_el_GR.ser