1. Package Management Guide
  2. Understanding the Deployment Process for WLS

Understanding the Deployment Process for WLS

This is an overview of how business services are deployed to the business services server for WLS 11g and WLS 12c:

  1. When you click Deploy, the R98825F runs.

    Note: If you are deploying the package to both the enterprise server and the business services server, you select the enterprise server and click Deploy. R98825D deploys the package to the enterprise server and then calls R98825F to deploy the package to the business services server.

  2. The R98825F creates the scfjar folder.

  3. The scf_manifest.xml is created in the scfjar folder.

    This xml contains information that the package deployment process uses to communicate with the Server Manager.

  4. E1BSSVAuthenticator.jar is copied to the scfjar folder.

    E1BSSVAuthenticator.jar is a custom authenticator jar that is required to secure business services on Oracle WebLogic Server.

  5. The WLS .ear file is copied to the scfjar folder.

  6. The contents of the scfjar folder are combined to form the bssv_timestamp.jar file.

    Note: If errors occur, they are logged to the jas.log or jasdebug.log files that are configured through the jdelog.properties file in the E1_Install_Path\system\classes path. Errors are also logged in the Server Manager EnterpriseOne Agent logs on the machine on which WAS is installed and under which the business service instance is created.

  7. The jar file is uploaded to Server Manager and both the file and the scfjar folder are deleted from the deployment server.