Go to primary content
Oracle® Retail RICS Data Viewer (APEX/DDS) RICS Data Viewer Guide
Release 19.3.000
F79086-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

5 Deploying DDS Web Application

This chapter describes the steps you should take to deploy DDS Web Application.

Preparing the Database for DDS Installation

Before you begin installing the DDS Web Application, make sure you have a valid DDS Data Source available. DDS assumes that the tables created, in the DDS data schema configured, are valid.

Deploying DDS Web Application on the WebLogic Servers

To deploy the DDS Web Application ear, take the following steps:

  1. Download DynamicDataService19.1.000ForAll19.x.xApps_eng_ga.zip

  2. Unpack the folder. A folder dds_home will be available.

  3. Edit the dds-deployment-env-info.json as follows:

            cd dds_home/conf/        vi dds-deployment-env-info.json
    
  4. Modify the DataSourceDef and MiddlewareServerDef with information that is specific to your environment.

    By default, the JSON files should have placeholders for the DDS, RIB Error Hospital, OCDS and RFI connections, namely DDSDataSource, RibErrorHospitalDataSource, OCDSDataSource and RFIDataSource. If you plan on using either of these connections, delete the other connections that are not in use.

    The table below summarizes the values that need to be changed specific to the environment

    Table 5-1 DataSourceDef and MiddlewareServerDef Values

    Value Description

    DDSDataSource -> jdbcUrl

    Database details of the server where the DDS default data source schema is hosted.

    RibErrorHospitalDataSource -> jdbcUrl

    Database details of the server where the database schema for the RIB Error hospital table is hosted.

    OCDSDataSource -> jdbcUrl

    Database details of the server where the database schema for the OCDS application is hosted.

    RFIDataSource -> jdbcUrl

    Database details of the server where the database schema for the RFI application is hosted.

    DDSAppServer -> weblogicDomainName

    Name of the domain where the DDS application will be deployed.

    DDSAppServer -> weblogicDomainHome

    Absolute path to the domain. (starts from the root directory)

    DDSAppServer -> weblogicDomainAdminServerUrl

    Admin server URL link of the domain.

    DDSAppServer -> weblogicDomainAdminServerProtocol

    Web Protocol to be used in the domain. (Can be t3, unsecure or t3s, secure)

    DDSAppServer -> weblogicDomainAdminServerHost

    Admin server host name. (domain.example.name.com)

    DDSAppServer -> weblogicDomainAdminServerPort

    Admin server host port number

    DDSAppServer -> weblogicDomainTargetManagedServerName

    Name of the managed server where DDS will be deployed.

    DDSAppServer -> DDSAdminUiUrl

    The complete URL link to the deployed DDS application. (http://<host_name>:<managed_sever_port>/)



    Note:

    The alias names in the configuration files should not be changed.

    The following is an example configuration:

    "DataSourceDef":{
    "DDSDataSource":{
    "dataSourceName":"DDSDataSource",
    "dataSourceClass":"oracle.jdbc.pool.OracleDataSource",
    "dataSourceJndiName":"jdbc/DDSDataSource",
    "jdbcUrl":"jdbc:oracle:thin:@//dbhost.example.com:1522/pdborcl",
    "jdbcUserAlias":"DDSAdminDataSourceUserAlias",
    "jdbcUser":"GET_FROM_WALLET",
    "jdbcPassword":"GET_FROM_WALLET",
    },
     
    "RibErrorHospitalDataSource":{
    "dataSourceName":"RibErrorHospitalDataSource",
    "dataSourceClass":"oracle.jdbc.pool.OracleDataSource",
    "dataSourceJndiName":"jdbc/RibErrorHospitalDataSource",
    "jdbcUrl":"jdbc:oracle:thin:@//dbhost.example.com:1522/pdborcl",
    "jdbcUserAlias":"RibErrorHospitalDataSourceUserAlias",
    "jdbcUser":"GET_FROM_WALLET",
    "jdbcPassword":"GET_FROM_WALLET",
     
    },
     
    "OCDSDataSource":{
    "dataSourceName":"OCDSDataSource",
    "dataSourceClass":"oracle.jdbc.pool.OracleDataSource",
    "dataSourceJndiName":"jdbc/OCDSDataSource",
    "jdbcUrl":"jdbc:oracle:thin:@//dbhost.example.com:1522/pdborcl",
    "jdbcUserAlias":"OCDSDataSourceUserAlias",
    "jdbcUser":"GET_FROM_WALLET",
    "jdbcPassword":"GET_FROM_WALLET",               
    },
     
    "RFIDataSource":{
    "dataSourceName":"RFIDataSource",
    "dataSourceClass":"oracle.jdbc.pool.OracleDataSource",
    "dataSourceJndiName":"jdbc/RFIDataSource",
    "jdbcUrl":"jdbc:oracle:thin:@//dbhost.example.com:1522/pdborcl",
    "jdbcUserAlias":"RFIDataSourceUserAlias",
    "jdbcUser":"GET_FROM_WALLET",
    "jdbcPassword":"GET_FROM_WALLET",   
    }
    }
    "MiddlewareServerDef":{
    "DDSAppServer": {
    "weblogicDomainName": "dds_domain",
    "weblogicDomainHome": "home/oracle/middleware_1221/user_projects/domains/dds_domain",
    "weblogicDomainAdminServerUrl": "t3://ddsdomainhost.example.com:7001",
    "weblogicDomainAdminServerProtocol": "t3",
    "weblogicDomainAdminServerHost": " ddsdomainhost.example.com ",
    "weblogicDomainAdminServerPort": "7001",
    "weblogicDomainAdminServerUserAlias": "DDSAdminServerUserAlias",
    "weblogicDomainTargetManagedServerName": "dds_managed_Server",
     
     
    "DDSAdminUiUrl":"http://ddsdomainhost.example.com:7003",
    "DDSAdminUiUserGroup":"DdsAdminGroup",
    "DDSAdminUiUserAlias":"DDSAdminUiUserAlias",
    "DDSAdminUiUser":"GET_FROM_WALLET",
    "DDSAdminUiPassword":"GET_FROM_WALLET",
     
    "DDSOperatorUiUserGroup":"DdsOperatorGroup",
    "DDSOperatorUiUserAlias":"DDSOperatorUiUserAlias",
    "DDSOperatorUiUser":"GET_FROM_WALLET",
    "DDSOperatorUiPassword":"GET_FROM_WALLET",
     
    "DDSMonitorUiUserGroup":"DdsMonitorGroup",
    "DDSMonitorUiUserAlias":"DDSMonitorUiUserAlias",
    "DDSMonitorUiUser":"GET_FROM_WALLET",
    "DDSMonitorUiPassword":"GET_FROM_WALLET"
     
    }
    } ,
    "DDSAdminApplication":{
    "DDSAdminAppUses":[
    "DDSAppServer"
    ]
            }
    
  5. Run the deployer script to create the datasource and deploy the DDS Web Application.

    $cd dds_home/bin/
    $sh dds-deployer.sh -setup-credentials -deploy-dds-app
    
  6. Enter the parameter value that is prompted by the script.

  7. Bounce the WebLogic Server hosting the DDS Web Application.

  8. Restrict Access to the DDS home folder:

    $cd ..$chmod -R 700 dds-home
    

Note:

To deploy the DDS application on a clustered environment, change the following in the config JSON file:
  1. weblogicDomainTargetManagedServerName - give the cluster name as the name of the managed server here.

  2. DDSAdminUiUrl - give the port number of the managed server which have been linked to the cluster on which DDS is to be deployed.


Redeploying DDS Web Application

If you have already configured the credentials and can use the same credentials (typically when redeploying the app), you can run the deployer with the -use-existing-credentials option as follows, and you will not be prompted for the credentials again for the deployment.

sh dds-deployer.sh -use-existing-credentials -deploy-job-admin-app

Testing the Deployment

After you deploy the server successfully, the DDS Web Application can be accessed using the following URL:

http://<host-server>:<managed-server-port>/dynamic-data-service-ui