Reviewing and deploying

A log window is displayed after the job container progress bars. Use the tabs to view the different logs.

When the installation is complete, you can check the resources to verify a successful deployment.

1. Check the provisioning results in the Business Automation Configuration Container console.

   On the deployment results page, if the provision is successful, the service URL is listed on the result page and you can click the link to open the service.

   Tip: You can download the configuration file from the main menu and download the execution logs.
2. You can also view the Helm releases for each product and component in the IBM Cloud Private Admin console.
   • Click Menu > Workloads > Helm Releases, and then search for the name you entered for the release.
   • Click the Launch menu to open the services.
     Tip: If deployed, Content Search Services is accessible through the Content Platform Engine URL.

If any product or component fails during deployment, a redeployment option that is named Edit and redeploy products is enabled on the main menu.

1. Click Edit and redeploy products.
2. Select which product to redeploy. You can select products from the configuration that successfully installed and the products that failed.
   Restriction: After you select a product to redeploy, you cannot go back to the Deployment Progress page to make a different selection, even though the edit and redeployment did not start. You must proceed with the redeployment.

   Before the redeployment starts a selected product, the previous installation and configuration files from the Persistent Volumes (PVs) are removed.

   If clean-up of a database is needed, you are notified. For IBM FileNet® Content Manager, if an initialization or verification fails and these options are chosen for redeployment then all of the provisioned components are redeployed.

   Tip: It is good practice to drop and re-create the databases before redeployment.
3. Click Submit. The configuration page for the selected products and components is displayed.
4. Modify any of the configuration parameters you want.
5. Click Deploy to start the redeployment.

If a component fails as a result of network latency or the LDAP and database servers are not available, you can click Rerun from the Actions menu of a job. Look at the logs to make sure that the job did not fail because of incorrect parameter values. Using the Rerun option, you cannot modify the configuration before redeployment.

If you click the Rerun action, Business Automation Configuration Container starts to redeploy the selected job. It does not delete the failed run because doing so removes the possibility to find the root cause of it failing. You can manually delete a release in the IBM Cloud Private Admin console after you found the root cause and you no longer need the logs.

For a IBM FileNet Content Manager deployment that includes verification and initialization, clean up the corresponding Content Platform Engine file store volume.