Work with JMS provider properties files

We can use properties files to create or change Java Message Service (JMS) provider properties.

Determine the changes to make to the JMS provider configuration or its configuration objects.

From the server profile bin directory, run wsadmin -lang jython

Using a properties file, we can create, modify, or delete a JMS provider object and its configuration properties.

Run administrative commands using wsadmin to create or change a properties file for a JMS provider, validate the properties, and apply them to your configuration.

for JMS provider properties files. We can create, modify,

Action	Procedure
create	Set properties and then run the applyConfigProperties command.
modify	Edit properties and then run the applyConfigProperties command.
delete	Uncomment #DELETE=true and run the deleteConfigProperties command.

Optionally, we can use interactive mode with the commands:

AdminTask.command_name('-interactive')

• Create a JMS provider and its properties.

  1. Create a properties file for a JMSProvider object.

     Open an editor and create a JMS provider properties file. We can copy the example properties file in this step into an editor and modify the properties as needed for the situation.

     An example properties file for a JMSProvider object named myProvider at cell scope follows:

     #
     # Header
     #
     ResourceType=JMSProvider
     ImplementingResourceType=JMSProvider
     ResourceId=Cell=!{cellName}:JMSProvider=myProvider
     #DELETE=true
      #
     #Properties
     #
     supportsASF=true #boolean
     classpath={}
     name=myProvider
     externalProviderURL=myEPURL
     nativepath={}
     description=WebSphere MQ Messaging Provider providerType=null #readonly
     externalInitialContextFactory=myEICFactory
      EnvironmentVariablesSection
     #
     #
     #Environment Variables
     cellName=WASCell06

  2. Run the applyConfigProperties command to create a JMS provider configuration.

     Running the applyConfigProperties command applies the properties file to the configuration. In this Jython example, the optional -reportFileName parameter produces a report named report.txt:

     AdminTask.applyConfigProperties(['-propertiesFileName myObjectType.props -reportFileName report.txt'])

• Modify an existing JMS provider.

  1. Obtain a properties file for the JMS provider to change.

     We can extract a properties file for a JMSProvider object using the extractConfigProperties command.

  2. Open the properties file in an editor and change the properties as needed.

     Ensure that the environment variables in the properties file match the system.

  3. Run the applyConfigProperties command to change a JMS provider configuration.

• If we no longer need a JMS provider, we can delete the entire JMS provider object.

  To delete the entire object, specify DELETE=true in the header section of the properties file and run the deleteConfigProperties command; for example:

  AdminTask.deleteConfigProperties('[-propertiesFileName myObjectType.props -reportFileName report.txt]')

Results

We can use the properties file to configure and manage the JMS provider object.

What to do next

Save the changes to the configuration.

Subtopics

• Work with WebSphere MQ topic properties files
  We can use properties files to create or change WebSphere MQ topic properties.

• Work with WebSphere MQ topic connection factory properties files
  We can use properties files to create or change WebSphere MQ topic connection factory properties.

• Work with WebSphere MQ queue properties files
  We can use properties files to create or change WebSphere MQ queue properties.

• Work with WebSphere MQ queue connection factory properties files
  We can use properties files to create or change WebSphere MQ queue connection factory properties.

• Work with mapping module properties files
  We can use properties files to create or change mapping module properties.

Related tasks

Extracting properties files

Create server, cluster, application, or authorization group objects using properties files and wsadmin scripting

Delete server, cluster, application, or authorization group objects using properties files

PropertiesBasedConfiguration (AdminTask)