Suggested Package Names

You should maintain two versions of each package, an A and a B version, so that you can alternate between these versions when you build packages. The advantage of this approach is that users always have a package available to them, even when you are building the latest version of that package. For example, package PRODB would be available to users while you are building PRODA. Then, after you release PRODA, you would build the next package into PRODB, and so on. This setup gives you two full packages (A and B) for production, as illustrated in this table:

Package Name	Description
PD920FA	Standard Production Full A
PD920FB	Standard Production Full B

Update packages might be named with the path code followed by "UA" or "UB" as shown:

Update Package Name	Description
PD920UA	Production Update Package 1
PD920UB	Production Update Package 2
PD920UA	Production Update Package 3
PD920UB	Production Update Package 4

A deployed server package cannot be revised, rebuilt, or deleted. It must be replaced with another package first. For this reason, you must have at least two server packages available so that you can alternate between them.

See also:

• "Understanding Security Workbench" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

Note: The maximum length for a package name is eight characters.