Package Build Considerations

Before beginning to build a language package, verify that the language installation is complete. To build the language package, first define the package. Building the package can take several hours, depending on the size of the package and the number of languages used. This task is completed on the Deployment Server, logged on as user JDE in DEP920.

To include language specifications in your package, specify the language in the package definition. The package build process then uses the language preference code. This code is specified as a parameter when building the package. It uses the relational database tables to build the form design aid text and report design aid text specifications. A language package can be a full, update, or partial package.

Caution: When building the client package with translated processing option text, run the build using Microsoft Windows with the system locale set to the appropriate language. If the system locale on the operating system does not match the installed language, the translated text in processing options (POTEXT) will be corrupted.

Building server packages that include languages other than English requires that the LocalCodeSet value of the Release 9.2 client matches the LocalCodeSet value of the JDE.INI on the Enterprise Server. If the LocalCodeSet value on the local client differs from the one specified on the Enterprise Server, the server package build fails and errors are logged in the JDE.LOG on the Enterprise Server.