Deployment steps and package content
The deployment steps depend on the type of content that is in a package. For some content, manual steps are required.
The database content is classified as structural content or nonstructural content. Structural content is content that must be reflected in the database schema as tables, views, columns, keys, and indexes. Nonstructural content is all other database content, which is typically stored in records in a table.
The content that is outside the database consists of files that are on the application server file system, such as Java™ class files and properties files. These files are the compiled sources.
When you deploy a package, compiled sources must be downloaded first. Next, structural changes are processed. Finally, nonstructural changes are processed. However, the specific steps that must occur depend on the contents of the package. Deployment might involve manual steps, such as switching the system to administration mode to restrict user access, downloading compiled sources, deploying EAR files, and restarting the system. When manual steps are required, the deployment pauses and prompts you to do the steps.
| Type of content in the package | Steps required during deployment |
|---|---|
| Nonstructural content | No manual steps are required in the deployment of packages that contain only nonstructural content, such as workflow process definitions. |
| Structural content | If a package contains only structural content, such as object, attribute, or index definitions, the deployment pauses after data loading is complete. You must enable administration mode to apply the structural changes to the database. |
| Nonstructural and structural content | If a package contains both nonstructural and structural content, such as object, attribute, or index definitions and workflow process definitions, the deployment pauses after data loading is complete. You must enable administration mode to apply the structural changes to the database. After the structural changes are applied, the nonstructural content is loaded. |
| Compiled sources | If a package contains only compiled sources, such as custom Java packages and Java class files, the deployment pauses to enable the download of the compiled sources to a client computer. If the compiled sources include Java classes, you must rebuild the product EAR file and deploy the new EAR file. You then continue the deployment to confirm that the compiled sources have been deployed to the application server. |
| Compiled sources and nonstructural content | If a package contains compiled sources, such as custom Java packages and Java class files and workflow process definitions, the deployment pauses to enable the download of the compiled sources to a client computer. If the compiled sources include Java classes, you must rebuild the product EAR file and deploy the new EAR file. You then continue the deployment to confirm that the compiled sources have been deployed to the application server, and then nonstructural content is loaded. |
| Compiled sources, structural content, and nonstructural content | If a package contains compiled sources, such as custom Java packages and Java class files, structural content, such as object, attribute, or index definitions, and nonstructural content, such as workflow process definitions, the deployment pauses to enable the download of the compiled sources to a client computer. If the compiled sources include Java classes, you must rebuild the product EAR file and deploy the new EAR file. You then continue the deployment to confirm that the compiled sources have been deployed to the application server. The deployment pauses a second time after data loading is complete. You must enable administration mode to apply the structural changes to the database. After the structural changes are applied, the nonstructural content is loaded. |