Deploying the Application

After you have prepared the database instance for 3DOrchestrate, you can use the deployment utility to configure the application in TomEE+.

In this task you run the 3DOrchestrate deployment utility and choose Oracle Pre-configured as the Database type.

  1. First you must determine the location in which the 3DOrchestrate Distribution Server will be deployed in TomEE+. The exact directory/folder name is determined by the Server name you choose in the deployment utility.

    Start the deployment utility GUI from the command line by executing the following batch or script file:

    <server_install_dir>\win_b64\reffiles\SMAExeServer\deploy\smaexe-deploy.bat
<server_install_dir>/linux_a64/reffiles/SMAExeServer/deploy/smaexe-deploy.sh

  2. In the General Settings tab, choose the Server name to be given to the 3DOrchestrate Distribution Server application. You can accept the default of exe1 or enter something else:



  3. Also in the General Settings tab, choose Oracle Pre-configured as the Database type.
  4. Switch to the Oracle Settings Predefined tab. Enter the following settings:

    • SID
    • Schema user name
    • Schema user's password (note that this field will hide the password by showing *** characters)
    • Host (enter the host name of the machine your Oracle database is running on)
    • Connect port

    The database administrator and system administrator can work together here (or via desktop sharing) to enter these values. When the DBA enters the Schema user's password, the password will be hidden by asterisk (*) characters in order to maintain proper security. When the deployment utility is executed (in the next step), the clear-text password will not be saved to the utility's deploy.param file.

  5. Switch to the Deploy tab. Select only the Server Actions shown below:



    Be sure that none of the Combined Actions or Database Actions are selected. The database actions are only for use in the normal mode of the deployment utility.

  6. Click Execute.

After the deployment completes, you can verify that the TomEE+ datasource configuration does not contain clear-text passwords, for example:

<Resource id="fiper/jdbc/nonXADataSource" type="DataSource">
    JdbcDriver oracle.jdbc.OracleDriver
    JdbcUrl jdbc:oracle:thin:@172.25.106.142:1521:COS
    UserName COSADMIN
    Password Y6hkhSDBQk2ACeFp2ypQvw==
</Resource>

In addition, no clear-text passwords are stored in the application server logs or in the deployment utility's deploy.param file.