Create database schemas using RCU. RCU is available only on Linux and Windows platforms. Use Linux RCU to install for UNIX supported databases and Windows RCU for supported Windows databases.

1. Navigate to the directory into which RCU is installed. For example:

   UNIX: $rcuHome/bin/rcu

   Windows: <rcuHome>\BIN

2. Start the application.

   UNIX: ./rcu

   Windows: rcu.bat

   The Repository Creation Utility welcome screen appears.

3. Click Next. The Create Repository page appears.
4. Make sure Create Repository is selected, then click Next. The Database Connection Details page appears. For simplicity, many users use their sys name here. Enter database details in the fields provided (Database Type, Host Name, Port, Service Name, Username, Password, Role).

   Database Type

   Select the database type as Oracle Database.

   Host Name

   Specify the name of the server where your database is running in the following format: host.example.com.

   Port

   Specify the port number for your database.

   Service Name

   Specify the service name for the database. For example, rdbms.host.example.com.

   Username

   Enter the user name for your database. The default user name is SYS.

   Password

   Enter the password for your database user.

   Role

   Select the database user's role from the drop-down list: Normal or SYSDBA.

5. Click Next. The Installer checks the prerequisites. When the prerequisite checks are complete, click OK. Click Next. The Components screen appears.
6. Click the Create a new prefix option and choose a schema prefix (for example: tenant1).
7. Select the accompanying components Metadata Services and Oracle Platform Security Services, in addition to the components selected by default. Click OK.
8. Click Next. The Schema Passwords page appears.
9. Select Use same passwords for all schemas.
10. Enter your password in the field provided and confirm it.
11. Click Next. The Map Tablespaces page appears. Click Manage Tablespaces, if you want to modify existing tablespaces.
12. For this installation, click Next. A Repository Creation notification appears. Click OK. Tablespaces are created, and the progress will be displayed in a pop-up notification. When the operation is completed, click OK. The Summary page appears.
13. Click Create. The schema is created. A Completion Summary screen appears.
14. Click Close.

Use the Oracle WebLogic Server Remote Console to set up a JDBC data source in the WebLogic Server instance for your applications.

1. Log in to the Oracle WebLogic Server Remote Console.
2. In the WebLogic Server Remote Console page, select JDBC > Data Sources. Click New.
3. In the JDBC Data Source Properties page:
   • In the Name field, enter the name of the unique JDBC data source. For example, mds-owsm-tenant1.
   • In the JNDI field, enter the name of the connection. For example, mds/owsm/tenant1.
   • For the Database Type, select Oracle.
   • For the Database Driver, select Oracle Driver (thin)
4. Click Next.
5. In the Transactions Options page, accept the default options and click Next.
6. In the Connection Properties page:
   • For Database Name, enter the Oracle SID. For example, rdbms.example.com.
   • For Host Name, enter the machine name of the database. For example, host.example.com
   • Enter the port number used to access the database.
   • Enter the user name as the Schema name created earlier, for example TENANT1_MDS. Enter the schema password for the database. Click Next.
7. In the Test Database Connection page, click Test Configuration to test the connection.
8. In the Select Targets page, select the server for which the JDBC data source is to be deployed.
9. Click Finish.

You can create OWSM security artifacts by using online WLST commands.

connectWSMRest('weblogic','password','example.com:22001')
startWSMTenantContext('tenant1')
beginWSMSession()
createWSMPolicySet('myPolicySet','rest-resource','Domain("*")')
attachWSMPolicy("oracle/multi_token_rest_service_policy")
commitWSMSession()
listWSMPolicySets()
endWSMTenantContext()

connectWSMRest('weblogic','password','example.com:22001')
startWSMTenantContext('tenant2')
beginWSMSession()
createWSMPolicySet('myPolicySet','rest-resource','Domain("*")')
attachWSMPolicy("oracle/http_jwt_token_service_policy")
commitWSMSession()
listWSMPolicySets()
endWSMTenantContext()

While running REST Commands for creating OWSM artifacts, pass the tenant id value in the X-RESOURCE-IDENTITY-SERVICE-GUID header.

curl -i -H "X-RESOURCE-IDENTITY-SERVICE-GUID:tenant1" -H "Content-Type:application/json" -u username:password -X POST -d @- http://example.com:22001/wsm-pmrest/v2/policyset
[{
  "name": "myPolicySet",
  "type": "rest-resource",
  "scope": "Domain('*')",
  "policyReferences":[{
                     "uri":"oracle/multi_token_rest_service_policy",
                      "status":"enabled"
                      }
                      ] 
}]

curl -i -H "X-RESOURCE-IDENTITY-SERVICE-GUID:tenant2" -H "Content-Type:application/json" -u username:password -X POST -d @- http://example.com:22001/wsm-pmrest/v2/policyset
[{
  "name": "myPolicySet",
  "type": "rest-resource",
  "scope": "Domain('*')",
  "policyReferences":[{
                        "uri":"oracle/http_jwt_token_service_policy",
                        "status":"enabled"
                        }
                        ] 
}]