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 service integration properties files

Work with SIB engine properties files

We can use properties files to create, modify, or delete a service integration bus (SIBus) messaging engine. SIBus is the default JMS messaging provider for the product.

Determine the property values to set for the SIB engine configuration.

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 SIB engine and its configuration properties.

Actions for SIB engine properties files. We can create, change, or delete SIB engine configuration properties.

Action Procedure
create Specify commandName=createSIBusEngine in the properties file. Run the applyConfigProperties command.
modify Specify commandName=modifySIBEngine in the properties file. Run the applyConfigProperties command.
delete Specify commandName=deleteSIBEngine in the properties file. Run the applyConfigProperties command.
create Property Not applicable
delete Property Not applicable

  1. Create modify, or delete a SIB engine.

    • Create a SIB engine.

      Open an editor, specify commandName=createSIBEngine in the header, specify the SIB engine properties, and save the file.

      We can copy the following SIB engine configuration to the properties file and edit the properties as needed.

      #
      # Header
      #
      CreateDeleteCommandProperties=true
      commandName=createSIBEngine
      #
      
      #
      # Properties
      #
      initialState=null #String
      node=myNode #String
      defaultBlockedRetryTimeout=null #java.lang.Long
      server=myServer #String
      highMessageThreshold=null #java.lang.Long
      bus=myBus #String,required
      engine=null #String
      cluster=null #String
      description=null #String

    • Modify a SIB engine.

      Open an editor, specify commandName=modifySIBEngine in the header, change the SIB engine properties as needed, and save the file. Set the required property to be modified. Also set cluster or node and server properties. The engine property is not required if it is a single engine.

      #
      # Header
      #
      CreateDeleteCommandProperties=true
      commandName=modifySIBEngine
      #
      
      #
      # Properties
      #
      initialState=null #String
      node=myNode #String
      defaultBlockedRetryTimeout=null #java.lang.Long
      server=myServer #String
      highMessageThreshold=null #java.lang.Long
      bus=myBus #String,required
      engine=null #String
      cluster=null #String
      description=null #String
    • Delete a SIB engine object.

      Open an editor, specify commandName=deleteSIBEngine in the header, specify the bus and any other required properties, specify cluster or node and server properties, and then save the file.

      #
      # Header 
      #
      CreateDeleteCommandProperties=true
      commandName=deleteSIBEngine
      #
      
      #
      # Properties
      #
      cluster=null #String
      bus=myBus #String,required
      engine=null #String
      node=myNode #String
      server=myServer #String

  2. Run the applyConfigProperties command.

    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 mySIBEngine.props -reportFileName report.txt'])

    Optionally, we can use the command in interactive mode:

      AdminTask.applyConfigProperties('-interactive')


Results

We can use the properties file to manage the SIB engine.

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