You can set up a transaction to be triggered by the Sterling Selling and Fulfillment Foundation agents.
To create a time-triggered extended transaction:
Control | Description |
---|---|
Runtime Properties | |
Agent Server | The server on which this instance of the transaction is to be run. To add new Agent Servers, click the Add Servers button next to this field. This is a parameter used to start the agent server. |
Alert Queue Name | The name of the alert queue. |
JMS Queue Name | The name of the JMS queue that contains messages to be processed by this transaction. |
No. of Threads | The number of concurrent threads with which this transaction should be run. |
Initial Context Factory | The class providing an Initial Context implementation for your
application server to enable remote Java clients
to connect. Select WebSphere® MQ if you are using MQSeries® accessed through a IBM® WebSphere IIOP URL. This sets the class name to: com.ibm.websphere.naming.WsnInitialContextFactory. Select File if you are using MQSeries accessed through a file URL, as with Oracle WebLogic. This sets the class name to com.sun.jndi.fscontext.RefFSContextFactory. Select WebLogic if you are using Oracle WebLogic JMS. This sets the class name to weblogic.jndi.WLInitialContextFactory. Select Jboss if you are using JBoss JMS. This sets the class name to org.jnp.interfaces.NamingContextFactory. If you defined an initial context factory code for ActiveMQ, select the entry you created for it. For more information about setting up other JMS vendors, such as ActiveMQ, which are not included in the default set, see Section A.2 "Configuring Communication Between an Agent and a JMS Server". Note: You
can override this value by configuring the yfs.agent.override.icf property
in the <INSTALL_DIR>/properties/customer_overrides.properties file.
Note: You can configure your own initial context
factory settings to be used here. For more information about defining
initial context factory codes, see Defining initial context factory codes.
|
Connection Factory | The name of the connection factory. This name corresponds with
a JMS connection factory configured in the application server cluster
running Sterling Selling and
Fulfillment Foundation. Note: You can override this value by configuring
the yfs.agent.override.qcf property in the <INSTALL_DIR>/properties/customer_overrides.properties file.
|
Provider URL | The URL containing the protocol and address used to access
the JMS queue. If you use Oracle WebLogic JMS, enter the following value:
If you use MQSeries through a JNDI file, enter the following value:
For example, if the path to the .bindings file is /home/yantra/MQ_HSmith/java/jndi, use:
If you use MQSeries through IBM WebSphere JNDI, enter the following value:
If you use JBoss JMS, enter the following value: jnp://<IP address and port of the JBoss instance> Note: You can override
this value by configuring the yfs.agent.override.providerurl property
in the <INSTALL_DIR>/properties/customer_overrides.properties file.
The Provider URL format is: t3://<ip Address>:<port> For clustered JMS configurations, use a comma-separated value comprising the host/IP and port of each node in the cluster. For example:
|
Enable JMS Security | Check this box if you want JMS Security to be enabled. Once
selected, the JMS Security Parameters tab is enabled to configure
destination and/or JNDI based JMS security. Note: Oracle WebLogic 12.1.2 only supports JNDI based JMS security.
If destination based security is enabled, it is altogether bypassed.
Therefore, you must configure JNDI based JMS security if using Oracle
WebLogic 12.1.2.
Note: You can override
this value by configuring the yfs.agent.override.auth.enabled property
in the <INSTALL_DIR>/properties/customer_overrides.properties file.
|
Schedule Trigger Message | Check this box to configure the agent to run the agent trigger
periodically from within the Agent Server during runtime. When there are no messages for the agent to process, a new trigger message is sent to the agent at specified time intervals. |
Schedule Trigger Message Interval (Min) | Enter the desired time interval in minutes. |
Service to Execute on Completion of Work | Enter the service to be run upon completing the execution of
the selected agent. You can select the required service by using the Search icon. Note: In case of agent implementations that extend
AbstractPurgeAgent or AbstractEnterpriseAgent, which performs multi
level GET for configured agent criteria, the completion of work service
will get executed for each of the GET calls that results in execute
messages. In this case, the completion of work just indicates the
completion of work for that criteria or GET operation.
|
Criteria Parameters | |
Parameter Name | The name of parameter sent to the transaction. This is a parameter used to trigger the transaction, for more information about this parameter, see "Time-Triggered Transaction Reference". |
Parameter Value | The value of the parameter sent to the transaction. For valid names and parameters, see "Time-Triggered Transaction Reference". |
JMS Security Properties Tab This is enabled upon selecting Enable JMS Security in the runtime properties tab. You can override the JMS security properties specified here by enabling the agent and flow authorization parameters in yfs.properties. Note: You
can override the JMS security parameters (userid and password) by
configuring the following parameters in the <INSTALL_DIR>/properties/customer_overrides.properties file:
For more information about the application server-specific security mechanisms, see Setting up the JMS Security Properties. |
|
Parameter Name | Enter the name of the security parameter. |
Parameter Value | Enter the value of the security parameter. |