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.

Similar Messages

  • Error saving JCA Connection factory in PI NWA

    Hi All,
    I am facing an  issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
    error details : CF_XD1_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
    The logs details : com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration failed, reason: "Can not set authentication user store "null" in security context "CF_XD1_180" for connector "CF_XD1_180" in application "sap.com/tc~sapjra".".
    at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.addComponent(ConnectorContainerImpl.java:1005
    i posted this  in SAP PI forum also...
    Error saving connection factory
    Regards
    ashutosh r

    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.

  • SFTP receiver channel error :Failed to create JCA connection.

    Hi All,
    Facing below error in SFTP receiver channel.
    This is the first run of SFTP adapter on our PI server.
    Message could not be forwarded to the JCA adapter. Failed to create JCA connection. Reason: c:\temp\sample_ra_output.5.txt (The system cannot find the path specified)
    Exception caught by adapter framework: Adapter call failed. Reason: c:\temp\sample_ra_output.5.txt (The system cannot find the path specified)
    SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Adapter call failed. Reason: c:\temp\sample_ra_output.5.txt (The system cannot find the path specified).
    Please help.
    Thanks & Regards,
    Nida Fatima

    Hi Heiko,
    Thanks for correcting me.
    PFB the screenshot of my channel.
    After this change channel is giving different error :
    Transmitting the message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Cannot lookup the ra connectionFactory. Reason: Object not found in lookup of com.sap.aii.adapter.sftp.ra. 
    Pleas guide.
    Regards,
    Nida

  • Problem while creating JCA connection to MDM server

    Hi All,
    I have restarted my mdm connector(com.sap.mdm.tech.connector) along with the applications related to Enrichment Controller. All applications restarted successfully. After that I tried accessing the URL
    http://MDMSERVER:50000/MDM_EnrichmentController/WorkflowPolling?process=Monitor
    but I am getting following exception in this page
    Polling Repository
        name=Vijaybabu_Repo_on_MDMSERVER, status=No repository connection, error description=com.sap.mdm.net.ConnectionException: Problem while creating JCA connection to MDM server MDMSERVER
            Enrichment Request Threads
    Could somebody help me pointing if something I have missed..
    Thanks and Regards,
    Manoj

    hi Swarna,
    I have verified the repository and found 0 fatal errors, 0 non-fatal erros and 0 warnings. I also checked the MDM Factory and Connector service is running fine.
    The detailed exception is
    Sep 2, 2008 12:49:40 PM com.sap.mdm.logging.MdmLogger error
    SEVERE: Problem while creating JCA connection to MDM server 'KOLAPON'
    com.sap.mdm.net.ConnectionException: Can not resolve JCA connection
         at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:119)
         at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnectionAccessor(JcaConnectionUtil.java:62)
         at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:70)
         at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:59)
         at com.sap.mdm.repository.commands.GetRepositoryStatusCommand.execute(GetRepositoryStatusCommand.java:67)
         at com.sap.mdm.enrichment.common.ECAdminUtils.getRepositoryStatus(ECAdminUtils.java:125)
         at com.sap.mdm.enrichment.common.EnrichmentUtils.validateRepostiryConfiguration(EnrichmentUtils.java:889)
         at com.sap.mdm.enrichment.common.EnrichmentUtils.getCatalogManager(EnrichmentUtils.java:144)
         at com.sap.mdm.enrichment.workflowpolling.PollingThread.getCatalogManager(PollingThread.java:166)
         at com.sap.mdm.enrichment.workflowpolling.PollingThread.run(PollingThread.java:102)
    Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
         at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:223)
         at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:108)
         ... 9 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
         at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:122)
         at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:213)
         ... 10 more
    Regards,
    Manoj
    Edited by: Manoj Kumar Nanda on Sep 2, 2008 9:21 AM

  • 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

  • Error creating a connection pool (No suitable driver)

    I have just installed WLS6.1 SP3
    I try to create a connection with the following parameters
    URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
    DriverName = oracle.jdbc.driver.OracleDriver
    every thing else is left as the defaults,
    when I click create everything is OK.
    I then go to the "Targets" tab and select myserver,
    move it to the chosen column and click apply.
    I then get the error
    <Error> <JDBC> <Cannot startup connection pool "myCP" No suitable driver>
    I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
    Under the section "Setting environment for your third party driver"
    it implys that if your using sybase jconnect or oracle thin drivers
    you do not need to do anything else.
    I looked in the weblogic.jar file and the OracleDriver.class file
    is there under oracle\jdbc\driver.
    the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    I would have thought that the driver class in the jar file
    would have be picked up given the path & classname match the
    driver name enter in the console.
    Any ideas on how to fix this problem?

    "Robert Towler" <[email protected]> wrote in message
    news:3dd3ea04$[email protected]..
    Thanks Slava, you were correct,
    I really appreciate it.Glad to help :)
    Regards,
    Slava Imeshev
    "Slava Imeshev" <[email protected]> wrote:
    Hi Robert,
    Looks like colon is missing after jdbc:oracle:thin. The url should be
    jdbc:oracle:thin:@myOracleServer:1521:myOracleSID
    Regards,
    Slava Imeshev
    "Robert Towler" <[email protected]> wrote in message
    news:3dd3e3c6$[email protected]..
    I have just installed WLS6.1 SP3
    I try to create a connection with the following parameters
    URL = jdbc:oracle:thin@myOracleServer:1521:myOracleSID
    DriverName = oracle.jdbc.driver.OracleDriver
    every thing else is left as the defaults,
    when I click create everything is OK.
    I then go to the "Targets" tab and select myserver,
    move it to the chosen column and click apply.
    I then get the error
    <Error> <JDBC> <Cannot startup connection pool "myCP" No suitable
    driver>
    >>>
    I looked at the doc edocs.bea.com/wls/docs61/jdbc/thirdparty.html
    Under the section "Setting environment for your third party driver"
    it implys that if your using sybase jconnect or oracle thin drivers
    you do not need to do anything else.
    I looked in the weblogic.jar file and the OracleDriver.class file
    is there under oracle\jdbc\driver.
    the CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    I would have thought that the driver class in the jar file
    would have be picked up given the path & classname match the
    driver name enter in the console.
    Any ideas on how to fix this problem?

  • Error on JCA connection with R/3 (Failure: ConnctorService)

    Hi all,
    i'm working with <b>SAP EP 6 SP 2</b>. I've developed an custom application that calls an BAPI on R/3 by the JCA connection.
    the custom component works well in the develop enviroment but it go bad in quality enviroment.
    when i execute it i've the following error message:
    <b>Failure: ConnctorService- getConnectionFactory(), retrieving the ConnectionFactory</b>
    any ideas?
    thanks a lot!
    gennaro

    Hello,
       In order to access the connector service of portal, we need to configure this system information in the portal.
       System Administration --> System Configuration
       After this, you will have also have do User mapping to this system.
       When you configure this system in the above way, you can also test for the connections validity.
       You can find relevant information on portal guide http://help.sap.com/saphelp_nw04/helpdata/en/ea/d4df3df2ad685ae10000000a11405a/frameset.htm
       Hope this helps.
    Best Regards,
    Padma

  • Error: Creating a Connection Pool: issue with valid transaction levels

    Server: SunOS 5.8 Generic_117350-27 sun4u sparc SUNW,UltraAX-MP
    App Server: Sun Java System Application Server 8.2
    Jar: ojdbc14.jar
    Datasource Classname: oracle.jdbc.pool.OracleConnectionPoolDataSource
    Resource Type: javax.sql.ConnectionPoolDataSource
    [Issue]
    Using /SUNWappserver/lib/ojdbc14.jar, when I create my connection pool in Sun Java System Application Server 8.2, I return the following error each time I try to start the domain:
    [#|2006-07-28T14:53:56.169-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=11;|RAR5117 : Failed to obtain/create connection. Reason : The isolation level could not be set: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels|#]
    When I change the value to "SERIALIZABLE" in my domain.xml file, I receive the following error in my server.log:
    Caused by: org.xml.sax.SAXParseException: Attribute "transaction-isolation-level" with value "SERIALIZABLE" must have a value from the list "read-uncommitted read-committed repeatable-read serializable ".
    So, I'm stuck!
    I can't use the values READ_COMMITTED or SERIALIZABLE since the valid values are "read-uncommitted read-committed repeatable-read serializable ".
    Case sensitivity matters.
    Any thoughts or help would be greatly appreciated.
    Thanks,
    --Todd                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    The Oracle JDBC accepts TRANSACTION_READ_COMMITTED and TRANSACTION_SERIALIZABLE isolation levels.
    Example:
    connAttr.setProperty(“TRANSACTION_ISOLATION”, “TRANSACTION_SERIALIZABLE”);
    I'd check with the Apps server folks.
    Kuassi - blog http://db360.blogspot.com/
    ------ book http://www.amazon.com/gp/product/1555583296/

  • Error creating OC4J connection

    Hello,
    Could you please help me with the following problem. I get the error listed below when trying to create new OC4J connection by choosing application server node.
    java.lang.RuntimeException: Error getting OC4J Process for: opmn-home+oc4j-{server IP}-6003-default
         at oracle.oc4j.admin.jmx.shared.Oc4jOpmnRmiDomain.getOc4jProcs(Oc4jOpmnRmiDomain.java:616)
         at oracle.oc4j.admin.jmx.shared.Oc4jOpmnRmiDomain.getPort(Oc4jOpmnRmiDomain.java:335)
         at oracle.oc4j.admin.jmx.shared.Oc4jRmiDomain.getRmiPort(Oc4jRmiDomain.java:119)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:433)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
         at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
         at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
         at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
         at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
         at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
         at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: oracle.ias.opmn.optic.OpticBadConnectException: Timed out (15000 ms) connecting to OPMN
         at oracle.ias.opmn.optic.OpmnPhone.dialOpmn(OpmnPhone.java:447)
         at oracle.ias.opmn.optic.OpmnPhone.makePhoneCall(OpmnPhone.java:178)
         at oracle.ias.opmn.optic.OpmnPhone.request(OpmnPhone.java:130)
         at oracle.ias.opmn.optic.OpmnQuery.getBuf(OpmnQuery.java:347)
         at oracle.ias.opmn.optic.OpmnQuery.getDom(OpmnQuery.java:467)
         at oracle.ias.opmn.optic.OpmnQuery.getProc(OpmnQuery.java:615)
         at oracle.ias.opmn.optic.OpmnQuery.getProc(OpmnQuery.java:709)
         at oracle.oc4j.admin.jmx.shared.Oc4jOpmnRmiDomain.getOc4jProcs(Oc4jOpmnRmiDomain.java:592)
    Thank you for your help.

    Check out thread JDeveloper Application Server connectivity
    Probably OPMN is listening on a different IP-address, or the server name does not resolve to the same IP-address on your Jdev machine (opmn might send a redirect that Jdev cannot follow).
    Marc

  • Error creating a connection pool to DB2 with the weblogic 8.1 driver

    I am trying to create a new connection pool with using the weblogic 8.1 (non XA driver (weblogic.jdbc.db2.DB2Driver)). When I create the pool one of the steps is to test the driver configuration and it fails with this step.
    I get the following error:
    [BEA][DB2 JDBC Driver]The databaseName connection property is not valid when connecting to Host Operating Systems.
    We are going through IBM's DB2 connect gateway (version 8.x) to connect to a DB2 database running on Z/OS.
    Here are my connection parameters:
    Driver Classname: weblogic.jdbc.db2.DB2Driver
    url: jdbc:bea:db2://db2cont2.arrow.com:3700
    Database User Name: XXXXXX
    password xxxxx
    properties
    user=db2trce
    portNumber=3700
    databaseName=DB2T
    batchPerformanceWorkaround=true
    serverName=db2cont2.arrow.com
    Any ideas would be much appreciated.
    Thanks,
    Matt

    Matthew McHugh wrote:
    I am trying to create a new connection pool with using the weblogic 8.1 (non XA driver (weblogic.jdbc.db2.DB2Driver)). When I create the pool one of the steps is to test the driver configuration and it fails with this step.
    I get the following error:
    [BEA][DB2 JDBC Driver]The databaseName connection property is not valid when connecting to Host Operating Systems.
    We are going through IBM's DB2 connect gateway (version 8.x) to connect to a DB2 database running on Z/OS.
    Here are my connection parameters:
    Driver Classname: weblogic.jdbc.db2.DB2Driver
    url: jdbc:bea:db2://db2cont2.arrow.com:3700
    Database User Name: XXXXXX
    password xxxxx
    properties
    user=db2trce
    portNumber=3700
    databaseName=DB2T
    batchPerformanceWorkaround=true
    serverName=db2cont2.arrow.com
    Any ideas would be much appreciated.
    Thanks,
    MattHi Matt. Unfortunately DB2 is different on differnet OSes. For
    DB2 on OS/390, z/OS, iSeries, and AS/4001, the URL is like this:
    jdbc:bea:db2://db2_server_name:port;Location=db2_location;CollectionId=your_collectionname
    Try removing the serverName property and the databaseName, and
    change your URL to
    jdbc:bea:db2://db2cont2.arrow.com:3700;Location=db2_location;CollectionId=your_collectionname
    where you would change 'db2_location' and 'your_collectionname' as appropriate.
    Joe

  • Error saving connection factory

    I was trying to create a JCA connection factory so that I can use the user module to convert IDOCs to flat file. But I was encountering this problem when saving
    Saving JCA Connection Factory: CF_ID1_800 failed due to: Can not add connection factory
    I use NWA_SUPERADMIN role.. But seems like even that can't save it correctly.
    THanks

    Hi Brian,
    I am also facing the same issue in SAP PI NWA  for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file.            we are on SAP PI 7.11  sp06....
    error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
    The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
    could you share info, how your issue got solved..
    Regards
    ashutosh r

  • OJMS Connection Factory Error

    Hi,
    (Platforms: OC4J developer preview 4, JDev 10.1.3 EA, Database :Oracle 10.1.0 )
    I have tried to implement the JMS provider (OJMS) according to the following document :
    http://www.oracle.com/technology/sample_code/tech/java/codesnippet/jms/datasources/ResourceProvider.html
    In my client code while I try to get the queue by :
    queue = (Queue)jndiContext.lookup("java:comp/resource/TestRP/Queues/RPQueue");
    there is no problem. But when I try to get connection factory by :
    queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("java:comp/resource/TestRP/QueueConnectionFactories/RPTable");
    it fails and gives the following exception:
    05/11/28 11:40:19 javax.naming.NamingException: Lookup error: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910; nested exception is:
         java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910 [Root exception is java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910]
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:68)
    05/11/28 11:40:19      at javax.naming.InitialContext.lookup(InitialContext.java:351)
    05/11/28 11:40:19      at BServlet.insertToQueue(BServlet.java:224)
    05/11/28 11:40:19      at BServlet.doPost(BServlet.java:199)
    05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:846)
    05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:397)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:245)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:231)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.access$1000(ServerSocketAcceptHandler.java:33)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:820)
    05/11/28 11:40:19      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    05/11/28 11:40:19      at java.lang.Thread.run(Thread.java:595)
    05/11/28 11:40:19 Caused by: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910
    05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:100)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:83)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:341)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:158)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:235)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:55)
    05/11/28 11:40:19      ... 18 more
    Any idea?
    Thanks,

    Hi Brian,
    I am also facing the same issue in SAP PI NWA  for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file.            we are on SAP PI 7.11  sp06....
    error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
    The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
    could you share info, how your issue got solved..
    Regards
    ashutosh r

  • Creating socket connection error

    My problem is when I have router in local host, my client works fine, but when I move router to an other computer, then creating topic connection gives me error like: error creating socket connection to 127.0.0.1:14001, message: Connection refused: no further information
    (I use port 14001, in local host it works). Why does it dry to connect to localhost? If I put up router in localhost too, it starts sending messages to this one!?
    Anyway maybe this problem might have something to do with changeing the router version (swiftmq1.0 to 2.1.2)?
    Could anyone help me with this one, I'm in big hurry, router and client should work on monday :-(
    Thank You!

    Thanx 4 answer :) neville
    I have the answer allready - just I had to add 1 row in routers properties file, like:
    swiftlet.sys$jms.listeners.plainsocket.bindaddress=192.168.0.1
    It was in the SwiftMQ documentation, but I was to lazy to read all of it. My fault.
    But thanks again for trying to help! And I WILL read that jndi doc.

  • Problem in datasource and connection factory.

    I am using a connection factory to make connections to the database.
    First I create a connection pool then i created a datasource and finally i used the JNDI Location name which i used inside the BPEL to create a connection factory.
    Does this activity requires a restart of server. I am getting the following error.
    file:/software/product/10.1.3.3.0/bpel/domains/default/tmp/.bpel_IRobo_Workflow1_1.0_e580208857197172fe72bbfca5d9d8b6.tmp/fr_jumper_info.wsdl [ fr_jumper_info_ptt::fr_jumper_info(InputParameters) ] - WSIF JCA Execute of operation 'fr_jumper_info' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore. [Caused by: VDMT_IROBO_DATASOURCE not found]
    ; nested exception is:
         ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore. [Caused by: VDMT_IROBO_DATASOURCE not found]
    See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-7060] (Oracle TopLink - 10g Release 3 (10.1.3.3.0) (Build 070608)): oracle.toplink.exceptions.ValidationException
    Exception Description: Cannot acquire data source [VDMT_IROBO_DATASOURCE].
    Internal Exception: javax.naming.NameNotFoundException: VDMT_IROBO_DATASOURCE not found.
    </summary>
    </part>
    -<part name="detail">
    <detail>
    Exception Description: Cannot acquire data source [VDMT_IROBO_DATASOURCE].
    Internal Exception: javax.naming.NameNotFoundException: VDMT_IROBO_DATASOURCE not found
    </detailException Description: Cannot acquire data source [VDMT_IROBO_DATASOURCE].
    Internal Exception: javax.naming.NameNotFoundException: VDMT_IROBO_DATASOURCE not found
    </detail

    Hi James
    I have created the data source and i can find it in the path C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\data-sources.xml
    <managed-data-source connection-pool-name="IRoboConnectionPool" jndi-name="jdbc/VDMT_IROBO_DATASOURCE" name="VDMT_IROBO_DATASOURCE"/>
    And in C:\product\10.1.3.1\OracleAS_1\j2ee\home\application-deployments\default\DbAdapter\oc4j-ra.xml i can see
         <connector-factory location="eis/DB/VDMT_IROBO" connector-name="Database Adapter">
              <config-property name="xADataSourceName" value="jdbc/VDMT_IROBO_DATASOURCE"/>
              <config-property name="dataSourceName" value="VDMT_IROBO_DATASOURCE"/>
              <config-property name="platformClassName" value="oracle.toplink.platform.database.Oracle9Platform"/>
              <config-property name="usesNativeSequencing" value="true"/>
              <config-property name="sequencePreallocationSize" value="50"/>
              <config-property name="defaultNChar" value="false"/>
              <config-property name="usesBatchWriting" value="true"/>
              <connection-pooling use="none">
              </connection-pooling>
              <security-config use="none">
              </security-config>
         </connector-factory>
    You have said I have given the name for dataSourceName incorrectly , what value should we give I dont know that I thought it is a user defined value.

  • How does JMS Destination relates to a Connection Factory ?

    Hello,
    I am new to JMS but have experience since 1995 with IBM MQseries, I like to understand how Connection Factories and Destination related to each other. I have looked at JMS documentation and seen the graphical representation but in MQ world we create a Queue Manger and a Queue under it. I have looke all over but can not explain this to myself.
    In Sun�s Java Application Server version 9, I have created a Connection Factory called �jms/ConnectionFactory_abc� and then have created a Destination called �jms/destination_abc� and successfully sent and received messages, what I do not understand is that there is no menu option in Sun�s web based screen to related the 2 together!! How do they relate? Do they related becuase of my program logic?
    What if you like to have same Destination names under 2 different Factories?
    ---------Code fragment without TRY/CATCH
    queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("jms/ConnectionFactory_abc ");
    queue = (Queue) jndiContext.lookup(�jms/destination_abc �);
    queueConnection = queueConnectionFactory.createQueueConnection();
    queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    queueSender = queueSession.createSender(queue);
    message = queueSession.createTextMessage();
    message.setText(input);
    queueSender.send(message);
    queueConnection.close();
    Please advise
    Thank You.
    AA

    I'll have a stab at this one, but may not be 100% right. Hopefully someone will point out anything I've got wrong.
    A connection factory is used to obtain a connection to the JMS provider, which in the case of MQSeries is synonymous Queue Manager. The connection is used to initiate one or more conversations with the JMS provider / QM, which might include starting a new transactional session.
    The destinations (Queues or Topics) are objects hosted by the JMS provider, however your client can only access these objects after establishing a connection / session, since it is the connection / session which determines the protocols and parameters to be used.
    The JNDI lookups are just a way for your client to obtain a remote reference to the Connection Factory and Queue objects hosted by the JMS provider, without coupling your client with the underlying JMS implementation (i.e. MQSeries, JBossMQ, ActiveMQ etc). When these references are bound to the JNDI tree they are given names like "jms/ConnectionFactory_abc" and "jms/destination_abc", but are not related to each other. Attempting to bind two references with the same JNDI name (on the same JNDI server) will cause in an error. So while you can two identically named queues on separate queue managers, you would have to give them different JNDI names,
    Hope this helps,
    Steve

Maybe you are looking for