Loading a triggers file

To make the settings in your configurable modifier triggers file active, you must load the file into WSRR.

• Use the web UI. Perform the following actions:
  1. Switch to the Configuration perspective if necessary, by selecting Configuration in the Perspective list.
  2. Click Active Profile > Modifiers > Configurable Modifier.
  3. Click Browse, select the required file, and click Open.
  4. Enter Triggers for the configuration item name, and click OK.
• Use the loadConfiguration.jacl script. Run one or other of the following commands, depending on whether WSRR is deployed in a cluster configuration, or a stand-alone or federated node configuration. Run the commands from the <WAS_INSTALL_ROOT>\WSRR\admin\scripts_cell directory. You must enter the commands all on one line. The configuration name must be "Triggers", and the configuration type must be "CONFIGURABLE_MODIFIER_CONFIGURATION", as specified by the -configname and -configtype parameters that follow.
  • In a cluster configuration:

    <WAS_INSTALL_ROOT>\bin\wsadmin
    -f loadConfiguration.jacl -cluster <CLUSTERNAME> -filepath <FILEPATH>
    -filename <FILENAME> -configname Triggers 
    -configtype CONFIGURABLE_MODIFIER_CONFIGURATION -systemflag true

  • In a stand-alone or federated node configuration:

    <WAS_INSTALL_ROOT>\bin\wsadmin
    -f loadConfiguration.jacl -cell <CELLNAME> -node <NODENAME>
    -server <SERVERNAME> -filepath <FILEPATH> -filename <FILENAME>
    -configname Triggers -configtype CONFIGURABLE_MODIFIER_CONFIGURATION 
    -systemflag true

  For example:

  c:\WebSphere\AppServer\bin\wsadmin
  -f loadConfiguration.jacl -cluster cluster1 -filepath c:/tmp
  -filename triggers.xml -configname Triggers
  -configtype CONFIGURABLE_MODIFIER_CONFIGURATION -systemflag true

  Note: In parameters passed to wsadmin, directory paths must be specified using a forward slash (/) as shown in c:/tmp in the previous example.