1. Database Upgrade Guide
  2. End to End Process Steps

End to End Process Steps

Here is the end-to-end steps from start to finish:

  1. Installation

    • Initiate the installation using setup executable.

    • Pick the home location for Siebel installation.

    • Pick relevant languages.

    • Select Installation Components, Siebel Enterprise Components, New Database Repository (master repository) and Configuration Tasks Enterprise Container Configuration and Application Interface Container Configuration .

    • Assign unused ports for application containers.

    • Set temporary credentials for SMC Login (Example: admin/admin).

    • Provide KeyStore and TrustStore jks file and their respective passwords.

    • Save the response file and Click on install.

  2. Deployment

    • Keep the required server info ready.

    • Prepare SMC URL.

    • Register Gateway host and port.

    • Update TLS port (Example: 9111).

    • Update database details for the Gateway security profile.

    • Enter the database credentials for SADMIN user.

    • Re-login to SMC using the database credentials.

    • Setup Gateway registry.

    • Create Enterprise Profile.

    • Enter the TNS name for Oracle if applicable.

    • Deploy Enterprise Profile.

    • Wait for deployment status to turn green in the deployment tree.

    • Create Siebel Server Profile.

    • Select Siebel Enterprise Application Integration, Siebel Web Tools.

    • Select the default application of your choice.

    • Deploy Siebel Server.

    • Pick the relevant languages.

    • Wait for Siebel Sever deployment to turn green.

    • Once the deployment is successful, Force Delete the Siebel Server deployment.

  3. Preparation

    • Open a fresh OS session (New terminal in case on non-Windows).

    • Shutdown Applicationcontainer_internal (non-Windows: Use command).

    • Shutdown Gateway Services (non-Windows: Use command).

    • Shutdown Applicationcontainer_external (non-Windows: Use command).

    • Startup Applicationcontainer_internal (non-windows: Use command).

  4. Execution

    • Prepare required payload data for Upgrade Factory Trigger.

    • Download and place the relevant ancestor repository on the server.

    • Open any REST API client (Example: Boomerang chrome extension).

    • Create JSON payload with all required information.

    • Prepare Upgrade Factory REST API endpoint URI.

    • Verify if Siebel application container external is up and running.

    • Provide basic Database authentication details for the API Requests.

    • Trigger POST request with required input JSON payload.

    • Trigger GET request to retrieve the current status of execution.

    • Once the RepAnalyzer execution is complete, launch Summary URL from the response.

    • Conflict Summary is available on the home screen.

    • Drilldown on the infolet to get the critical conflict details.

    • Check the filter buttons to view attention and info records.

    • Table shows only the Critical conflicts.

    • Process starts UpgRep execution.

    • Upon completion of UpgRep, process is paused for database backup.

    • Process can be resumed once database backup is done and STATS gathered.

    • Trigger a PUT request to resume the process after backup.

    • Trigger GET request to know the latest status of execution.

    • After completionof the merge, the database is prepared to launch Web Tools.

    • Process is paused to complete conflict resolution using Web Tools.

    • Launch SMC portal for enabling Web Tools.

    • Re-deploy the Siebel Server Profile that was deleted during preparation.

    • Select relevant languages.

    • Wait for deployment status to turn green.

    • Create External Application Interface Profile.

    • Fill in all the required details.

    • Add Applications URLs for Web Tools Object Manager.

    • Deploy Application Interface Profile.

    • Launch Web Tools using the Web Tools URL.

    • Navigate to the Upgrade Conflicts screen and make changes as appropriate.

      • Change the Resolution value using Override slider button.

      • Update multiple records using Change Records button.

    • Once the conflicts are resolved, click on Conflict Resolution Complete.

    • Web Tools Application is logged out.

    • Take a database backup and Trigger a PUT request to resume the process.

    • Trigger GET request to know the latest status of execution.

    • After FullPublish completion, the final Upgrade process UpgPhys is kicked off.

    • Upgrade is complete with the completion of UpgPhys.

    • Launch the upgraded applications to verify the database upgrade has successfully completed.