WAS v8.5 > Script the application serving environment (wsadmin) > Use properties files to manage system configuration > Manage specific configuration objects using properties files > Work with JMS provider properties files

Work with mapping module properties files

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

Determine the changes to make to your mapping module configuration or its configuration objects.

Start the wsadmin scripting tool. To start wsadmin using the Jython language, run the wsadmin -lang jython command from the bin directory of the server profile. Using a properties file, we can create, modify, or delete a mapping module object and its configuration properties.

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

Actions for mapping module properties files. We can create, modify, and delete mapping module configuration properties.

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 mapping module and its properties.

  1. Create a properties file for a MappingModule object.

     Open an editor and create a mapping module properties file. We can copy the example properties file in this step into an editor and modify the properties as needed for the situation. The example defines a mapping module under a MQQueueConnectionFactory with jndiName myJName. The factory is defined under a JMSProvider at cell scope:

     #
     # Header
     #
     ResourceType=MappingModule
     ImplementingResourceType=JMSProvider
     ResourceId=Cell=!{cellName}:JMSProvider=WebSphere MQ JMS Provider:MQQueueConnectionFactory=jndiName#myJName:MappingModule=
     AttributeInfo=mapping
     #DELETE=true
     #
     #Properties
     #
     authDataAlias=myADA
     mappingConfigAlias=myMCA
     
     EnvironmentVariablesSection
     #
     #
     #Environment Variables
     cellName=WASCell06

  2. Run the applyConfigProperties command to create a mapping module 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 mapping module.
  1. Obtain a properties file for the mapping module to change.

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

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

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

  3. Run the applyConfigProperties command.

• If you no longer need a mapping module, we can delete the entire mapping module 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 manage the mapping module object.

Save the changes to your configuration.

Related

Extracting properties files using wsadmin.sh
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

Reference:

PropertiesBasedConfiguration command group for AdminTask using wsadmin.sh

+

Search Tips   |   Advanced Search