Steps Used to Install Siebel Approval Manager

You can use the following steps to install the SAM application.

Note: From 25.8 onwards Siebel Approval Manager (SAM) supports both HTTPS enabled REST APIs for the service type. If you are updating from a version prior to 25.8, you must manually configure HTTPS within SAM to enable HTTPS REST calls after SAM has been installed or updated.
Before Installing/Updating SAM
  1. Get a copy of the keystore (jks) file used to configure REST calls to SAM. This is the .jks file you used for your Siebel Server installation.

  2. Get the password used for the keystore jks file if the file uses a password.

To install Siebel Approval Manager

  1. Navigate to the location of the SAM build that you downloaded.

    This example shows the location of the SAM build in a Microsoft Windows environment:

    <DOWNLOAD_DIRECOTRY>\runInstaller.bat

    This example shows the location of the SAM build in a Unix environment:

    <DOWNLOAD_DIRECOTRY>/runInstaller.sh
  2. Start the SAM installer by using one of the following options:

    • On Microsoft Windows, double-click the runInstaller.bat file.
    • On UNIX, enter the command ./runInstaller.sh

    The Siebel Approval Manager Installation window appears, displaying the installation process.

  3. In the Installation Location screen, choose the directory where you would like to install SAM and put this value in the Installation Directory field.
    Note: If you are simply updating SAM to the latest build, choose the directory where SAM is currently installed. If this is a new installation, choose the directory where you would like the new installation to be.
  4. Click Next.
  5. In the Component Selection Screen make sure these two checkboxes are checked (true).
    • Siebel Approval Manager
    • Siebel Approval Manager Configuration
  6. Click Next.
  7. In the Configuration Details screen, define how to connect to your existing Siebel installation. These values are the same that you used to install Siebel CRM.
    Field Example Value for Oracle Example Value for SQL Server
    Apache Tomcat Home Folder Required. Location the siebel.war is deployed. Location the siebel.war is deployed.
    Database Type Required. oracle mssql
    Database Server Name Required. slc09urt slc09urt
    Database Instance Name Required. qaurt1 BIN_INST1
    Database Name Required. Not applicable MSUIU128
    Database Port Details Required. 1551 34100
    Database Username Required. ORAURT108 MSUIU128
    Database Password Required. ORAURT108 MSSQL
    Database Table Owner Required. ORAURT108 dbo
    TNS Service Name For Oracle this is the TNS entry in your tnsnames.ora file. N/A
    Database ODBC Driver Name Oracle90 ODBC Driver 17 for SQL Server

    These values are independent of the database platform:

    Field Example Value
    Siebel Server Location Required. C:\Siebel\ses\siebsrvr
    SMTP Hostname Required. internal-mail-router.example.com
    SMTP Port Required. 25
    SMTP Email Account Username Required. DoNotReply@example.com
    SMTP Email Account Password Required. changeme
    Noreply Email ID Required. noreply@example.com
    MailTo Email ID Required. firstname.lastname@example.com
    Email ID Required. samuel.siebel@example.com
    Email ID Password Required. siebel
    Email Folder Required. inbox
    Email Server Required. mail.example.com
    Email Server Port Required. 993
  8. Click Next.
  9. In the Summary screen, review your choices. If you need to change anything, click Back. Once all the values entered are satisfactory, click Next.
  10. In the Installation Progress screen, click Install to begin installing SAM.
  11. In the Finish Installation screen, click Close to end the installer.
  12. Verify the WAR files to ensure they are deployed under the SAM application container.
    1. Access this location: <SIEBEL_INSTALL DIRECTORY>\applicationcontainer_internal\webapps.
    2. Check to ensure that sam.war and emailapprover.war files are in the webapps folder.
  13. Verify that the SAM URL is valid, as follows:
    1. Launch the SAM URL using this format: http://localhost:tomcatport/sam/login.

      For example: http://slc01qlu:8080/sam/login

    2. Enter the user name and password to log into the SAM application. (default: admin\admin)

      The SAM home page appears.

After Installing/Updating SAM
  1. Use the EncryptString.jar to encrypt the password. This jar file is found inside the SAM install home path.

    Sample command: 

    Windows:

    <SAM Install Home>\jre\bin\java.exe -jar "<SAM Home>\SAM Install 
    Home\EncryptString.jar" "<keystore jks password>"

    UNIX:

    <SAM Install Home>/jre/bin/java -jar "<SAM Install 
    Home>/EncryptString.jar" "<keystore jks password>"
  2. Copy the keystore jks file to the server in which SAM is installed.

    For Example:

    C:/siebel/ses/applicationcontainer_external/certs
  3. Go to the Tomcat server home path where SAM is installed.

  4. Open the database.properties file under <Tomcat home>/conf.

  5. Place the following entries to the bottom of the list of properties in the file:

    sam.keyStorePassword=<Encrypted keystore jks password from step 1>
    sam.keyStoreFilePath=<Path to the keystore jks file from step 2> 
    eg: C:/siebel/ses/applicationcontainer_external/certs/keystore.jks
Note: Once the changes are completed, bounce the Tomcat service where SAM is installed. You are now ready to configure a secured REST API under the Administration > System.