Upgrades without Separate Transaction and Security Database Servers

This section provides upgrade instructions for sites that want to maintain their Transaction and Security databases on the same database server. To initiate this type of upgrade, perform the following steps:

  1. Perform Steps 1 through 5 as in Simphony Upgrade Procedures.
  2. Certificate Location: Throughout the Simphony 18.2 upgrade process, the Simphony installation application checks for the entry of a valid Service Host Name. The following parameters review the installation application’s Service Host Name validation behavior:
    1. If Microsoft Internet Information Services (IIS) is selected for the Certificate Location field, note that the Service Host Name (to be entered on the next installation screen) is based on the installed secure certificate's Common Name (CN) field.
    2. Certificate: To add a new certificate, select New, click Select, enter or select the certificate location, and then enter the Password for the certificate.
    3. To use an existing certificate, select Existing, and then select the installed certificate from the drop-down list.
    4. If you are using a Load Balancer server and using the Import/Export Service or plan to use the Oracle Hospitality Simphony Engagement Cloud Service, select LoadBalancer for the Certificate Location field. Note that the Service Host Name (to be entered on the next installation screen) is based on the Full Qualified Domain Name (FQDN) of your application server.
    5. Https IP Address: Enter the application server’s IP address.
    6. Service Host Secure Port: If you enter a port number other than the default of 443, you need to enable that port on the Load Balancer server and then click Next.
  3. When using IIS, enter (or verify) the Service Host Name (for the Simphony application server). If the Service Host Name does not match the installed secure Certificate’s CN text, a warning message dialog appears.
    1. Do not ignore the message; select No, and then correct the invalid Service Host Name.
    2. Enter the Default Gateway IP address and Default Net Mask in their corresponding fields, and then click Next.
  4. When using LoadBalancer, enter (or verify) the Service Host Name (for the Simphony application server). If the Service Host Name does not match the FQDN of your computer, a warning message dialog appears.
    1. Do not ignore the message; select No, and then correct the invalid Service Host Name.
    2. Enter the Default Gateway IP address and Default Net Mask in their corresponding fields, and then click Next.
  5. Enter (or verify) the Service Host Name for the Simphony application server, Default Gateway IP address, and Default Net Mask in their corresponding fields, and then click Next.
  6. Enter the following information that is used to connect to the existing security database, and then click Next:
    1. Server Name: Enter the name of the security database server.
    2. Service Name: (Oracle Database users) Enter the name of the service (TNS alias).
    3. Instance Name: (Microsoft SQL Server users) Enter the Microsoft SQL Server’s database name (usually contains the database server’s name).
    4. Username: Enter your security database access user name.
    5. Password: Enter your security database access password.
    6. Database Port: Enter the port number used to access the security database server, and then click Next.
  7. Enter the following information to connect to the reporting database:
    1. Server Name: Enter the name of the reporting database server.
    2. Service Name: (Oracle Database users) Enter the name of the service (TNS alias).
    3. Instance Name: (Microsoft SQL Server users) Enter the Microsoft SQL Server’s database name (usually contains the database server’s name).
    4. Username: Enter (or verify) your reporting database access user name.
    5. Password: Enter your reporting database access password.
    6. Database Port: Enter the port number used to access the reporting database.
    7. Username: Enter (or verify) your reporting database access user name.
    8. Password: Enter your reporting database access password, and click Next.
  8. Enter a database administrator’s logon credentials, click OK, and then click Next.
    • If you are using an Oracle Database, enter the credentials for the sys user.

    • If you are using a Microsoft SQL Server database, enter the credentials for the sa user.

  9. Click Confirm. The installation application creates a new user and security database on the secondary database server and drops them from the original database server. When the upgrade is complete, click Finish.