...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<ejb-jar-bnd>
...
<session name="CRMProcessRewardSettlementBean" simple-binding-name="ejb/CRMProcessRewardSettlement" />
...
</ejb-jar-bnd> |
The process must also be added in the CrmEJB/ejbModule/META-INF/ibm-ejb-jar-ext.xml to define how much time the process could been executing on WebSphere server as follows:
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
...
<session name="CRMProcessProcessSmsRun">
<global-transaction transaction-time-out="86400" />
<time-out value="86400" />
</session>
...
|
Then the process, should be mentioned in CrmEJB/ejbModule/META-INF/jboss-ejb3.xml file where we declare in enterprise beans, the process and in assembly descriptor we mention the timeout of the execution on WildFly server as follows:
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
...
<session>
<ejb-name>CRMProcessProcessSmsRunBean</ejb-name>
<ejb-class>com.crm.process.provisioning.sms.CRMProcessProcessSmsRunBean</ejb-class>
<session-type>Stateless</session-type>
</session>
...
<container-transaction>
<method>
<ejb-name>CRMProcessProcessSmsRunBean</ejb-name>
<method-name>*</method-name>
<method-intf>Local</method-intf>
</method>
<tx:trans-timeout>
<tx:timeout>86400</tx:timeout>
<tx:unit>Seconds</tx:unit>
</tx:trans-timeout>
</container-transaction>
...
|