Creation of an Enterprise Messae Source Type

Question

Hi guys,
has anyone of you tried before connecting BAM to Joram. Joram should be used as JMS provider. I'll post my confirguration:
Display name:
Joram
ID:
EMST.JORAM
CLSID of Admin implementation:
{CAC27017-40A2-4AD4-9BAC-16D01578A192}
CLSID of Receiver implementation:
{CAC27017-40A2-4AD4-9BAC-16D01578A192}
CLSID of Sender implementation:
{CAC27017-40A2-4AD[/i]4-9BAC-16D01578A192}
Startup parameter:
JMS*".;C:\Oracle\OracleBAM\OC4J\j2ee\home\oc4j.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\oc4jclient.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\oc4j-internal.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\ejb.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\servlet.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\jta.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\javax88.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\javax77.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\jmxri.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\jmx_remote_api.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\lib\adminclient.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\ojspc.jar;C:\Oracle\OracleBAM\OC4J\j2ee\home\jazn.jar;C:\Oracle\OracleBAM\OC4J\opmn\lib\optic.jar;C:\Oracle\OracleBAM\OC4J\rdbms\jlib\aqapi.jar;"".;c:\TIBCO\JMS\clients\java\tibjms.jar;c:\TIBCO\JMS\clients\java\jms.jar;c:\TIBCO\JMS\clients\java\jndi.jar;c:\TIBCO\JMS\clients\java\jta-spec1_0_1.jar;c:\TIBCO\JMS\clients\java\jcert.jar;c:\TIBCO\JMS\clients\java\jnet.jar;c:\TIBCO\JMS\clients\java\jsse.jar;c:\TIBCO\JMS\clients\java\tibcrypt.jar;"".;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;"".;C:\Program Files\SonicSoftware\SonicMQ\lib\sonic_Client.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\gnu-regexp-1.0.6.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jaxp.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\xerces.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\tools.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\providerutil.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\fscontext.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\sslj.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jsafe.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\certj.jar;"".;C:\bea\weblogic700\server\lib\weblogic.jar;"".;C:\eGate\client\classes\stcjms.jar;C:\eGate\client\JRE\1.3\lib\ext\fscontext.jar;C:\eGate\client\JRE\1.3\lib\ext\providerutil.jar;C:\eGate\client\ThirdParty\sun\jms.jar;C:\eGate\client\ThirdParty\sun\jndi.jar;C:\eGate\client\ThirdParty\sun\jta.jar;"".;C:\JNDI-Directory_WebMethods\fscontext.jar;C:\JNDI-Directory_WebMethods\providerutil.jar;C:\JNDI-Directory_WebMethods\javax.jms.jar;C:\Program Files\webMethods6\Broker\lib\BrokerJMS60.jar;C:\Program Files\webMethods6\common\lib\client60.jar;C:\Program Files\webMethods6\Broker\lib\xerces.jar;C:\Programme\SOPware\Devbox\devbox-modules\joram\ship\lib\joram-client.jar;C:\Programme\SOPware\Devbox\devbox-modules\joram\ship\lib\joram-shared.jar;C:\Programme\SOPware\Devbox\devbox-modules\joram\ship\lib\ow_monolog.jar;C:\Programme\SOPware\Devbox\devbox-modules\joram\ship\lib\JCup.jar;"
The next step is the creation of the Enterprise Message Source:
[i]Name:
MyEMS
Owner:
VM\admin
Type:
Joram
InitialContextFactory:
fr.dyade.aaa.jndi2.client.NamingContextFactory
JNDI Service Prvider URL:
localhost:16400
TopicConnectionFactory Name:
TopicConnectionFactory
Topic Name:
Topic
JMS Message Type:
TextMessage
with one field as a String with filesize=4000.
When I create a plan to insert in a simple Grid and update this plan I am getting the following error:
Unable to create Message Receiver COM object.
[Oracle BAM Enterprise Link error code:  0x75 -- 0x1, 0x75 -- 0x4B]
[W32 HRESULT: 0x80004002]
Interface not Supported
Error creating Message Receiver COM object.
[Oracle BAM Enterprise Link error code:  0x75 -- 0x1, 0x75 -- 0x4C]
Error while processing the data for the step 'Oracle BAM Enterprise Message Receiver'
[Oracle BAM Enterprise Link error code:  DC -- 0x1, DC -- 0x83]
Error while processing the data for the step 'Oracle BAM Enterprise Message Receiver'
[Oracle BAM Enterprise Link error code:  DC -- 0x1, DC -- 0x83]
Unable to create Message Receiver COM object.
[Oracle BAM Enterprise Link error code:  0x75 -- 0x1, 0x75 -- 0x4B]
[W32 HRESULT: 0x80004002]
Interface not Supported
Error creating Message Receiver COM object.
[Oracle BAM Enterprise Link error code:  0x75 -- 0x1, 0x75 -- 0x4C]
Error while processing the data for the step 'Oracle BAM Enterprise Message Receiver'
[Oracle BAM Enterprise Link error code:  DC -- 0x1, DC -- 0x83]
Update of Plan "NotificationReceiverPlan" failed.
[Oracle BAM Enterprise Link error code:  PlanMgr -- 0x1, PlanMgr -- 0xD5]
Did I miss anything in my configuration?
Regards,
Christoph

Answer 1

Hi,
I dont see a point in having this statement
swc_set_table event_container 'INTERNAL_TABLE' t_cnp_container. Infact it is not needed !!
SWE_EVENT_CREATE like any other FM, take a
lt_var type standard table of SWCONT.
ls_var type SWCONT.
fill your ls_var with all fields and append it to lt_var each time and pass lt_var to event_table of SWE_EVENT_CREATE. It should work !!
However, suggested way is to use SAP_WAPI_CREATE_EVENT instead of SWE_EVENT_CREATE  from ECC 5.0 onwards. There are fe concerns with SWE_EVENT_CREATE mainly with respect to commit and persistancy. Better we should use SAP_WAPI* as much as possible from ECC 5.0.
Try above and Good Luck !!
Regards
Krishna Mohan