Unable to create Queue Connection factory

Hello All,
I am configuring JMS listner with my enterprise appliaction using Sun application Server 8.2 PE.
Let me tell you my setup first: I have created a connection factory *'TCSQCF'* on appliaction server (sun app ser 8.2) which is directing to Sun MQ 4.1 broker listning on port 7677 using this address list 'mq://10.44.5.14:7677/'
My JNDI configurations through which I can acess and post a mess on queues using my simple application employing following setup. (My simple app contains appserv-admin.jar, appserv-rt.jar, imqjmsra.jar and j2ee.jar files ONLY in lib directory)
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"com.sun.appserv.naming.S1ASCtxFactory");
props.setProperty(Context.PROVIDER_URL,"iiop://10.44.5.14:3700");
String jmsConnectionFactoryName = "TCSQCF";
Object obj = jmsContext.lookup(jmsConnectionFactoryName);
Now when i copy all these four jar files into my enterprise application *'ext'* directory and uses the same setup as shown above I am having the following error??:(
2008-12-03 16:11:57,104 [JMSListener-Thread-12] DEBUG jmslistener - JMSListener.run(), Listener thread started
2008-12-03 16:11:57,119 [JMSListener-Thread-12] INFO jmslistener - **** JMSListener version 1.1.1 ****
2008-12-03 16:11:57,119 [JMSListener-Thread-12] DEBUG jmslistener - Input Queue : INQ
2008-12-03 16:11:57,119 [JMSListener-Thread-12] DEBUG jmslistener - Output Queue : OUTQ
2008-12-03 16:11:57,119 [JMSListener-Thread-12] DEBUG jmslistener - Dead Letter Queue :
2008-12-03 16:11:57,119 [JMSListener-Thread-12] DEBUG jmslistener - Use transactional queues : false
2008-12-03 16:11:57,120 [JMSListener-Thread-12] DEBUG jmslistener - Number of threads : 5
2008-12-03 16:11:57,120 [JMSListener-Thread-12] DEBUG jmslistener - JNDI Factory Name : TCSQCF
2008-12-03 16:11:57,120 [JMSListener-Thread-12] DEBUG jmslistener - JNDI Initial Factory : com.sun.appserv.naming.S1ASCtxFactory
2008-12-03 16:11:57,132 [JMSListener-Thread-12] DEBUG jmslistener - JNDI Provider URL : iiop://10.44.5.14:3700
2008-12-03 16:11:57,133 [JMSListener-Thread-12] DEBUG jmslistener - JNDI Security Principal :
2008-12-03 16:11:57,133 [JMSListener-Thread-12] DEBUG jmslistener - JNDI Security Credentials :
2008-12-03 16:11:57,133 [JMSListener-Thread-12] DEBUG jmslistener - ****
2008-12-03 16:12:01,878 [JMSListener-Thread-12] ERROR commonjms - jndiLookup : JNDI lookup failed for:TCSQCF:
javax.naming.CommunicationException: serial context communication ex [Root exception is com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to look up ConnectorDescriptor from JNDI]
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:317)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.temenos.tocf.commonjms.JMSUtil.jndiLookup(Unknown Source)
at com.temenos.tocf.commonjms.JMSUtil.getQueueConnectionFactory(Unknown Source)
at com.temenos.plugin.jmslistener.JMSListener.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to look up ConnectorDescriptor from JNDI
at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:68)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:293)
... 5 more
2008-12-03 16:12:01,881 [JMSListener-Thread-12] ERROR jmslistener - run : Unable to create a queue connection factory... Stopping
Please Note that my enterprise 'ext' directory contains 20-30 other jar files and I researched on it that MIGHT BE one of the existing 'jar' file are conflicting with the new 4 jar files i have mentioned. I am unable to find out whats wrong and I do not have nay idea which one is causing this issue and how to resolve it.???
Please reply if you have information regarding this issue and if you need anyother information please let me know.
Thanks.

Finally I found the problem which takes me over a week to understand and its SILLY. I am posting here for all of us to never forget this atleast :-)
anyway the above problem as i mentioned earlier is that my newly added JAR files and existing were conflicting somehow.
I just had to add a class path of all of my new four JAR files to force my application to use these jar only not any other
which was missing and my application fails but test application works using ECLIPSE as i did not had anyother files in its 'lib' directory. I edit my script code from BEFORE to After and it all worked. (SILLY SILLY SILLY)
Before _
java -jar ../lib/MyApplication.jar $*
After_
java -cp ../ext/appserv-admin.jar:../ext/appserv-rt.jar:../ext/imqjmsra.jar:../ext/j2ee.jar:../lib/MyApplication.jar $*Hope this helps for people like me :-(
Thanks for your help. Best of luck
Regards

Similar Messages

  • Unable to create a connection in SQL developer

    hii
    I'm unable to create a connection in SQL developer..it says I/O Exception, Network Adapter could not establish a connection...i provided the username and password which i used for SQL*Plus, which is working fine. And i gave the host as localhost. I don't know how to fill the connection name field..can anyone help me in connecting to the database...By the way I'm using Oracle 11g. Thankssssss

    you could try to change the connection type to TNS and pick the database name available to you in the Network Alias drop-down list.
    Edited by: Alex Nuijten on Sep 5, 2008 10:13 AM

  • Unable to create Metadata connection for Dictionary Provider

    Hi,
    I am getting the following error while I try to run a Web Dynpro Application;
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
        at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
        at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
        at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
        at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
        at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
        ... 37 more
    The JCo Connections are tested and pinged, they work fine.
    Can anyone please tell what the error could be?

    The details exception list is as below:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.dow.dc.model.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 34 more

  • RFC Error: Unable to create Metadata connection for Dictionary Provider

    I configured two RFC ('WD_XXX__MODELDATA_DEST and WD_XXX_RFC_METADATA_DEST). I tested it and it shown green light.
    When I run my application that coonnect to CRM using RFC, I got the following errors:
    <i>com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.xxx.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_ICEBERG_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:443)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:381)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:410)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:311)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:347)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.dictionary.runtime.DdException: 'WD_XXX_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 49 more</i>
    I understand that I need to configured the Metadata Dictionary type for the RFC. For this, I need to configure the Message Server properties (for load balancing).
    But my Basis guy told me that CRM is an application server, so we only can configured with application server properties. Is this true? (I really doubt it) That is no Message Server connection to CRM system now.
    If it is true, how can I create a RFC connection to CRM system?
    Thanks for help.
    Kent

    Hi KC,
    Try the following links, they may help you.
    http://help.sap.com/saphelp_nw04s/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
    JCO connection
    Using the SAP Enterprise Connector for generating BAPI Proxy Classes
    points if useful
    Thanks
    Suresh

  • Unable to set up connection factory for stand-alone resource adapter

    I'm testing out JCA 1.5 in OC4J P4, and I try to register a resource apapter by configuring oc4j-ra.xml like this:
    <connector-factory location="MySomething" connector-name="Something">
    However, I get the following error:
    05/09/28 17:14:24 Notification ==> Warning. Unable to set up connection factory
    to location MySomething for a resource adapter deployed as stand-alone.
    Is this a bug, or just me?
    Would appreciate it if someone knew what was wrong.
    Regards
    -am

    Looks like you need to tell us more...
    How is your adapter packaged?
    Which files are included (deployment descriptors, etc)?
    --olaf                                                                                                                                                                                                                                                                                   

  • Bug - unable to create new connections on SQL Developer 4.0.0.13

    Upgraded to SQL Developer 4.0 and we are unable to create new connections in the Connections pane on the left hand side.
    Clciking the green plus button and right clicking Connections and 'New Connection' doesn't bring up the New Database Connection dialog box.

    Sounds like an 'install' problem.
    Can you extract the zip to a new directory and try again? You did extract v4 to a fresh directory, yes?

  • Unable to receive Queue Message Unable to create Queue in MDM 2.0.1

    Hi All,
    I am getting below exception when i am trying to read JMSQueue from weblogic server to MDM 2.0.1
    Steps i configured as below:
    Created XAI JNDI server : XAI JNDI Server(Demo), Provider URL(http://localhost:7001), Initial Connection Factory(weblogic.jndi.WLInitialContextFactory)
    created XAI JMS Connection:XAI JMS Connection(DemoConn), XAI JNDI Server(Demo), JNDI Connection Factory(weblogic.jms.XAConnectionFactory)
    created XAI JMS Queue: XAI Queue Name(DemoQueue), Queue Name(TestQueue), XAI JNDI Server(Demo)
    created XAI Receiver DemoRx mapped with XAI Class JMSRCVR and with above configurations
    MPL is creating intial context factory for jndi server properly and intializing queues properly.
    But getting namenotfound exception at Receiver DemoRx
    [Thu May 26 15:01:46 IST 2011] Receiver DemoRx - Read interval is 10 seconds.
    [Thu May 26 15:01:47 IST 2011] Receiver "DemoRx" initialization failed:Unable to receive Queue MessageUnable to create Queue: javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '']; remaining name 'TestQueue'
    com.splwg.mpl.receiving.ReceiverInitException: Unable to receive Queue MessageUnable to create Queue: javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'TestQueue'. Resolved '']; remaining name 'TestQueue'
         at com.splwg.mpl.jms.queue.JMSReceiver.prepareConnection(JMSReceiver.java:394)
         at com.splwg.mpl.jms.queue.JMSReceiver.init(JMSReceiver.java:266)
         at com.splwg.mpl.receiving.AsyncReceiverManager$1.call(AsyncReceiverManager.java:232)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:662)
    Please help me in this regard
    Thanks in advance,
    sukumar

    Hi Suraj,
    I would prefer to discuss the problems in the forum. There are maybe other that have the same problem and they could then participate from the discussion.
    No back to your problem:
    As fare as I know there is no build in function to read directly from file system.
    MPL is no longer supported in this product and this was the only module for reading the file system.
    You have to develop an application to fetch the files form the file system or you must use an Enterprise Service Bus
    like OSB or ServiceMix.
    To enable the system for the IMD import you have to publish a Business Object or Script via XAI Inbound service.
    The recommended way is to use the D1-IMDSeeder BO.
    There is a chapter in the MDM Configuration Guide, explaining how to setup the XAI Inbound service.
    There is also a service script available. The advantage of the service script is, that you can import IMDs for more than on device (D1-IMDEvtUpl and DM-IMDEvtUpl). The DM-IMDEvtUpl is eventually only in the demo database available.
    The disadvantage of the IMDSeeder is, that you have to setup a lot of configurations in the system. There is another thread in the forum explaining the setup.
    My preferred way is to use the D1-InitialLoadIMDScalar or D1-InitialLoadIMDInterval BO but you have to do a lot of things by your own.
    /Markus

  • Unable to create a connection for Discussion Forums.

    Hi,
    I have my WC_Spaces and WC_Colloboration Servers running actively. When I try to create a new connection by right-clicking Connections in Applications Resources and choose Discussion Forums and too I entered the URL and admin fields, I find its unable to create a new connection. The error displayed is : "Failed to verify connection". Please help me with this.
    Regards,
    Dinesh Vishnu Kumar

    Hi,
    In your webcenter application you have created the discussion forum connection and you have connections.xml file in your application.Open the connections.xml in jdeveloper and check the discussion forum connection entry.
    For example here I have written down my entry on forum connection-
    <Reference name="Discussion Forum Connection" className="oracle.adf.mbean.share.connection.webcenter.forum.ForumConnection" xmlns="">
    <Factory className="oracle.adf.mbean.share.connection.webcenter.forum.ForumConnectionFactory"/>
    <RefAddresses>
    <StringRefAddr addrType="forum.url">
    <Contents>http://localhost:8890/owc_discussions</Contents>
    </StringRefAddr>
    <StringRefAddr addrType="admin.user">
    <Contents>weblogic</Contents>
    </StringRefAddr>
    <StringRefAddr addrType="connection.time.out">
    <Contents/>
    </StringRefAddr>
    <StringRefAddr addrType="policy.uri.for.auth.access">
    <Contents/>
    </StringRefAddr>
    <StringRefAddr addrType="policy.uri.for.public.access">
    <Contents/>
    </StringRefAddr>
    <StringRefAddr addrType="recipient.key.alias">
    <Contents/>
    </StringRefAddr>
    <StringRefAddr addrType="adapter.name">
    <Contents>Jive</Contents>
    </StringRefAddr>
    </RefAddresses>
    </Reference>
    Change the required entries with your values(for serveraddress,port and admin user).
    One more thing need to consider that is -
    in jdeveloper proxy ,add the server address in exception list and restart the jdeveloper.
    Sometimes it will show you up as "failed to verify the connection". But it will work atleast functionality-wise it will work.
    Apart from this,I have a query on "Have you used any VPN connection to connect collaboration server to create forum connection?"
    Hope it works for you.
    Regards,
    Hoque

  • Unable to create UCM Connection in JDeveloper

    I am trying to create UCM connection but getting the following error:
    oracle.stellent.ridc.protocol.ProtocolException: Unable to initialize connection idc://myhost:4444
    Unable to initialize connection idc://myhost:4444
    java.net.ConnectException: Connection refused: connect
    Connection refused: connect
    can any solve this problem?
    Regards:    

    I am trying to create UCM connection but getting the following error:
    oracle.stellent.ridc.protocol.ProtocolException: Unable to initialize connection idc://myhost:4444
    Unable to initialize connection idc://myhost:4444
    java.net.ConnectException: Connection refused: connect
    Connection refused: connect
    can any solve this problem?
    Regards:    

  • Runtime binding of JMS object(Queue, COnnection Factory)

    I want to knwo whether runtime binding the JMS Objects(Connection Factory & Destinations)
    is possible in WebLogic server?
    According to Weblogic it only binds JMS Object at the startup of the server using
    a Startup class?
    Thanks a million

    Destinations can be created dynamically.
    check:
    http://edocs.bea.com/wls/docs61/jms/implement.html#1189112
    viswa
    "Rakesh Jaiswal" <[email protected]> wrote:
    >
    I want to knwo whether runtime binding the JMS Objects(Connection Factory
    & Destinations)
    is possible in WebLogic server?
    According to Weblogic it only binds JMS Object at the startup of the server
    using
    a Startup class?
    Thanks a million

  • Error creating JCA connection factory in NWA

    Hi,
    I need to load an file with idoc content into a XML.
    So parameter IDOCXmlToFlatConvertor is required  and it's necessary to create a JCA Connection Factory in NWA.
    I'm trying to do it using :
    /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
    http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm
    But, when i try to create a JCA Connection Factory in NWA, systems returns next error:
    com.sap.engine.services.connector.exceptions.BaseDeploymentException: Can not set authentication user store "null" in security context "MRD_300" for connector "MRD_300" in application "sap.com/tc~sapjra".
    at com.sap.engine.services.connector.deploy.util.security.SecurityUtils.deploySecurity(SecurityUtils.java:507)
    However, creating JCA connection as indicated in this blog, security tab doesn't allow any change  and field user store can't be modified.
    How to do it?
    Carme

    Hello Carme,
    From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
    This beautiful blog by William will surely help you rectify the problem.
    /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
    Kindly check if you have done the following in your configuration:
    1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15" 
    2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
    3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
    I hope this should solve your problem.
    Regards, Gaurav.

  • 11g 64-bit unable to create ODBC connection

    Hello,
    I am currently facing issue related to ODBC connection. Details of configuration is as follows
    OS: Vista 64 Home Premium
    Oracle DB 11g 64bit: ver 11.1.0.6.0,plus the addition of the fix for bug 7389110 (as per release notes)
    ODBC driver location: C:\app\oracle\product\11.1.0\db1\BIN\sqora32.dll
    It appears and works well from 32 bit ODBC connection manager. However, it's not visible/available from 64 bit ODBC connection manager. Oracle installation repository appears under 64 bit area ("Program Files") and not under "Program Files (x86)". Assuming it might be a problem with installation I have also tried copying registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC with no luck.
    Any help to create ODBC connection is much appreciated
    Thanks,
    Hemant
    Please do not respond to this question here. I am moving it to ODBC forum area
    Edited by: user6868322 on Aug 5, 2009 2:04 PM

    Opening new tread under ODBC forum and closing this

  • Unable to create a connection in data modeler with oracle 9i

    While creating a connection to my 9i db I am getting the following error
    Status : Failure -Test failed: oracle.i18n.text.converter.CharacterConverterOGS.getInstance(I)Loracle/i18n/text/converter/CharacterConverter;

    Hi,
    This problem when importing from Data Dictionary can occur intermittently if you have the Oracle 9i or 10g database software installed on your computer.
    Ivan provided a workaround in a previous message in this forum Re: Error when testing database connection :
    Try to create a batch file (datamodeler.bat) under Data Modeler installation folder and put the following two lines in it:
    set ORACLE_HOME=%CD%
    start datamodeler.exe
    Then double click on this file to start Data Modeler.
    Ivan

  • Unable to create new connection using SAP Business One

    Hi all,
    I am unable to make a connection using the new SAP Business One connetion provided with the 8.8 release of SAP Business One Crystal Report Integration Package.
    There are no Companies available to select from.  When I try to manually type in the company name, the logon fails.  If I then press "Cancel", I get a message that Crystal reports encountered a problem and needs to close.  The details of the error refers to the following DLL: crdb_b1.dll.
    The connection is successful from another PC that only has the Client installed (and uses the License server on our server, which also contains the databases.)
    I have a local installation with my own license server.  I am not even able to connect to the database on my local PC.
    Please can anyone explain why this isn't working?
    Regards,
    Rikard

    Hi Rikard,
    You may get better help if you post your question to the Business One forum. I can' t move your post.
    Thank you
    Don

  • Unable to create TNS connection in SQL Developer

    This is my first time install SQL Developer 1.5 on my computer and when I try to create a connection using TNS Connection Type to connect to Oracle database, I get this error message:
    Status: Failure -lo exception: SO exception was generated.
    Do you know how to resolve this error?
    Thanks,
    Lily

    Hi Lily,
    This error is due to a tns entry that is unusual/malformed.
    Note that
    1/sqldeveloper picks up tnsnames.[a variety of endings not just ora] rather than just tnsnames.ora .
    2/We recently released 1.5.1[.54.40] is that the release you are using
    Can you post the 'problem' tns entry with ip and service name replaced by a stub?
    ie something like:
    XE =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = my.machine)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = my_service_name)
    -Turloch

Maybe you are looking for