Create JMS Resources

If you are using Model in Image, Java Messaging Service (JMS) resources can be created using the provided templates.

To identify whether a version uses the Model in Image source type, see the Supported Image column in Patches Included in Oracle WebLogic Server for OKE.

JMS resources can be added to both JRF and non-JRF domains. It is recommended to use JDBC persistent stores for JMS and Transaction stores to be in the database. So, we need to create a datasource and corresponding leasing table for JDBC store for both the JRF and non-JRF domains.

Complete the following steps:

1. Create a table for database leasing:
2. Format of the tablename should be: <datasourceschemausername>.<tablename>
   Example:

   create table mydbuser.mytable
   (
   SERVER VARCHAR2(255) NOT NULL,
   INSTANCE VARCHAR2(255) NOT NULL,
   DOMAINNAME VARCHAR2(255) NOT NULL,
   CLUSTERNAME VARCHAR2(255) NOT NULL,
   TIMEOUT DATE,
   PRIMARY KEY (SERVER, DOMAINNAME, CLUSTERNAME)
   );

3. The tablename has to be specified in the model template yaml for AutoMigrationTableName

The sample model template yaml files for are located at /u01/shared/scripts/pipeline/templates:

• jrf_domain_jms_resources.yaml
• non_jrf_domain_jms_resources.yaml

These are basic sample template model yaml files that can be used and has to be modified according to your requirement. These are not the final model template.

Note:

Irrespective of the number of managed servers, increase the initial and max capacity of mydatasource to a higher value.

For best practices about creating JMS resources, see Best Practices for JMS Beginners and Advanced Users in Administering JMS Resources for Oracle WebLogic Server.