Professional Documents
Culture Documents
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.provider.url=ormi://pluto:12401
java.naming.security.principal=oc4jadmin
java.naming.security.credentials=serene1
[JAVA]
DLL = C:\Program Files\Java\jre1.6.0_02\bin\client\jvm.dll
CLASSPATH =
D:\sba80ucm\siebsrvr\CLASSES\Siebel.jar;D:\sba80ucm\siebsrvr\CLASSES\Sieb
elJI_enu.jar;D:\product\10.1.3.1\OracleAS_1\j2ee\home\oc4jclient.jar;D:\produ
ct\10.1.3.1\OracleAS_1\j2ee\home\lib\jms.jar;D:\product\10.1.3.1\OracleAS_1\j
2ee\home\lib\jta.jar;D:\product\10.1.3.1\OracleAS_1\opmn\lib\optic.jar;D:\sba8
0ucm\javaee.jar;D:\sba80ucm;.
VMOPTIONS = -Xrs -Djava.compiler=NONE
Testing ReceiveDispatchSend
1. After restarting the Siebel server, place the following xml in the demoQueue:
2. Run the following command on server manager command line utility:
start task for comp JMSReceiver with ReceiverConnectionSubsystem=
JMS_Q1ReceiveDispatchSend, ReceiverDataHandlingSubsystem=JMSEcho,
ReceiverMethodName=ReceiveDispatchSend
3. The component goes into endless loop as it interprets the response sent from
Siebel to the same queue as the next request. Query for the task with the
command ‘list task for component JMSReceiver’ and kill the task with the
command ‘stop task <taskid>’
4. Test the message in the ‘demoQueue’ queue. It should have a new xml sent
from Siebel.
Testing SendReceive