The PDC database must have the appropriate local time zone setting.

For more information on setting the time zone, see the Oracle Database Globalization Support Guide.

Table 3-1 and Table 3-2 provide recommended database parameters for tuning your database for the PDC installation. These are the minimum requirements for PDC.

WebLogic Server is a component of the Oracle Fusion Middleware media pack. For the compatible version of WebLogic Server, see BRM Compatibility Matrix.

For information on installing Oracle WebLogic Server and the patches (if any), see the Oracle WebLogic Server documentation on the Oracle Help Center:

http://docs.oracle.com

Copy the needed jar files to your PDC implementation.

1. Apply patch p26626168_122140_Generic.zip on top of your WebLogic Server installation.

2. If you will be installing the PDC software, copy the following files to a directory on your PDC machine:

   • The ojdbc8.jar file from your Oracle database installation

   • Middleware_home/oracle_common/modules/oracle.pki/oraclepki.jar

   • Middleware_home/oracle_common/modules/oracle.osdt/osdt_cert.jar

   • Middleware_home/oracle_common/modules/oracle.osdt/osdt_core.jar

   where Middleware_home is the ORACLE_HOME directory of your WebLogic Server installation.

3. If you will be installing the BRM Integration Pack, copy the following files to a directory on your PDC machine:

   • The ojdbc8.jar file from your Oracle database installation

   • Middleware_home/oracle_common/modules/oracle.idm/identitystore.jar

   • Middleware_home/oracle_common/modules/oracle.jps/jps-api.jar

   • Middleware_home/oracle_common/modules/oracle.nlsrtl/orai18n.jar

   • Middleware_home/oracle_common/modules/oracle.nlsrtl/orai18n-collation.jar

   • Middleware_home/oracle_common/modules/oracle.xdk/xmlparserv2.jar

   • Middleware_home/oracle_common/modules/oracle.xdk/xml.jar

   • Middleware_home/oracle_common/modules/com.sun.xml.bind.jaxb-impl.jar

   • Middleware_home/oracle_common/modules/com.sun.xml.bind.jaxb-core.jar

   • Middleware_home/oracle_common/modules/oracle.pki/oraclepki.jar

   • Middleware_home/oracle_common/modules/oracle.osdt/osdt_cert.jar

   • Middleware_home/oracle_common/modules/oracle.osdt/osdt_core.jar

   • Middleware_home/oracle_common/modules/javax.jms.javax.jms-api.jar

   • Middleware_home/wlserver/modules/javax.transaction.javax.transaction-api.jar

   • Middleware_home/wlserver/server/lib/wlthint3client.jar

   • Middleware_home/wlserver/server/lib/wlclient.jar

   • Middleware_home/wlserver/server/lib/wljmsclient.jar

   • Middleware_home/wlserver/server/lib/wljmxclient.jar

   • Middleware_home/wlserver/server/lib/wlnmclient.jar

   • Middleware_home/wlserver/server/lib/wlsafclient.jar

4. During the PDC and BRM Integration Pack installation process, the installer will prompt you for the directory in which your prerequisite libraries are located. You will need to enter the path where you copied the JAR files.

Install Patch 33903365 on top of your WebLogic Server installation.

To apply the WebLogic Server patch:

1. Apply patch p33903365_122140_Generic.zip on top of your WebLogic Server 12.2.1.4.0 installation.

2. Restart WebLogic Server.

Oracle Application Development Runtime must be installed on the machine on which you will install PDC. For more information on the compatible version, see BRM Compatibility Matrix.

Download Oracle Application Development Runtime from the following page:

https://www.oracle.com/tools/downloads/application-development-framework-downloads.html

For information on installing Oracle Application Development Runtime, see Oracle Fusion Middleware Installation Guide for the appropriate version.

Before creating a WebLogic Server domain, use the Oracle Fusion Middleware Repository Creation Utility (RCU) to create the required Oracle Identity and Access Management (IAM) database schema. See Fusion Middleware Repository Creation Utility User's Guide for more information on RCU.

To create a WebLogic Server domain in which to deploy PDC, see the description of using the Configuration Wizard in the Oracle WebLogic Server documentation. You can use the Configuration Wizard in graphical mode or console mode.

Table 3-3 shows the values to choose when creating the WebLogic Server domain for PDC.

Create the WebLogic Server domain with at least one managed server configured along with the administration server because Oracle recommends that you deploy PDC on a managed server in the production environment.

See Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite for the appropriate version to see more information on WebLogic Server domains.

You can now start the administration server manually and log in to WebLogic Administration Console.

If you want to enable secure communication for PDC, you must configure SSL for the WebLogic Server domain in which you deploy PDC.

To configure SSL for the WebLogic Server domain:

1. Generate the server-side KeyStore file by using the recommended version of the JRE/JDK keytool utility. See Key and Certificate Management Tool for more information.

2. Export the public certificate from the server-side KeyStore file by using the recommended version of the JRE/JDK keytool utility. See Key and Certificate Management Tool for more information.

3. Generate the client-side KeyStore file from the exported public certificate by using the recommended version of the JRE/JDK keytool utility. See Key and Certificate Management Tool for more information.

   Note:

   Note the path of the client-side KeyStore file. You need to provide this path during the PDC installation if you choose to use SSL.

   If you are installing PDC and BRM Integration Pack on different machines, copy the client-side KeyStore file to the machine on which you want to install BRM Integration Pack.

4. Configure SSL for the server on which you want to deploy PDC in WebLogic Server Administration Console. See the Oracle WebLogic Administration Console Help for more information.

5. Enable Java Secure Socket Extension-based SSL for the server on which you want to deploy PDC in WebLogic Server Administration Console. See the Oracle WebLogic Server Administration Console Help for more information.

In order to use TLS 1.3 with the PDC REST Services Manager, you must create a self-signed certificate and perform other configuration.

To enable TLS 1.3 in PDC REST Services Manager:

1. Create a directory to contain the certificate, for example PDC_RSM_home/rsm_cert.

2. Change to your new directory and generate an SSL certificate. You can use an OpenSSL command such as the following:

   openssl req -x509 -newkey rsa:4096 -keyout openSSLKey.pem -out cert.pem
       -days 365 -nodes

   See "openssl-req" in the OpenSSL documentation for more information about the OpenSSL req command.

3. Generate a PKCS12 KeyStore file. For example, the following OpenSSL command creates a KeyStore file named keystore.p12:

   openssl pkcs12 -export -out keyStore.p12 -inkey openSSLKey.pem -in
       cert.pem

   See "openssl-pkcs12" in the OpenSSL documentation for more information about the OpenSSL pkcs12 command.

4. Change to the PDC_RSM_home/apps/bin directory and generate the hashed KeyStore passphrase using the following command:

   RestServicesManager.sh hash password

   where password is the password you entered when generating the PKCS12 KeyStore file.

   Note:

   If you get the error: "Error: Could not find or load main class io.helidon.config.encryption.Main," update the version of helidon-config-encryption.jar in the hash method in the RestServicesManager.sh file.

5. Add ssl-protocols, keystore-path and keystore-passphrase in the application.yaml file. For example:

   server:
     ...
     ssl-protocols:
       - "TLSv1.2"
       - "TLSv1.3"
     ssl:
       private-key:
         keystore-path: "file_path/certificate.p12"
         keystore-passphrase: "${passPhrase}"

   where file_path is the path to the KeyStore file and passphrase is the hashed passphrase you created using RestServicesManager.sh.

   See "PDC REST Services Manager Security" in Security Guide for more information about the application.yaml file.