Cci resource adapter in weblogic

          Hi,
          I am trying to install the cciblackbox-tx resource adapter that comes with
          sun reference implementation. I successfully deployed the resource adapter and
          created the stored procedures in cloudscape. I get a null pointer exception when
          I call the execute method on the interaction. I did check that the connection,
          interaction are not null. I have a feeling that the java class (Procs.class) that
          you create for the stored procedures need to be in the classpath of the cloudscape
          server when it starts. I would appreciate if anyone can provide insight into this.
          thanks,
          babu
          

          Weblogic 6.1 ships cloudscape 3.5.1. Sun's RI ships cloudscape 3.6. cloudscape
          3.5.1 does not fetch the metadata of the stored procedures properly. I upgraded
          to cloudscape 3.6 and evrything works fine. I did try the example on suns RI and
          it works fine.
          babu
          prasen <[email protected]> wrote:
          >
          >yes you are right, you need to put Procs.class in your classpath.
          >
          >Also I am not sure, but there may be some problems with their
          >implementation. Did you try out teh example on SUN's RI ?
          >
          >prasen
          >
          >babu siddabathuni wrote:
          >>
          >> Hi,
          >> I am trying to install the cciblackbox-tx resource adapter that
          >comes with
          >> sun reference implementation. I successfully deployed the resource
          >adapter and
          >> created the stored procedures in cloudscape. I get a null pointer exception
          >when
          >> I call the execute method on the interaction. I did check that the
          >connection,
          >> interaction are not null. I have a feeling that the java class (Procs.class)
          >that
          >> you create for the stored procedures need to be in the classpath of
          >the cloudscape
          >> server when it starts. I would appreciate if anyone can provide insight
          >into this.
          >>
          >> thanks,
          >> babu
          

Similar Messages

  • WebSphere MQ resource adapter  and Weblogic - how?

    Hi,
    has anybody managed to get the WebSphere MQ resource adapter to run with Weblogic 10.3 ?
    (http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzaw.doc/uj40010_.htm)
    I got it deployed, but it never triggers. I only made changes to the ra.xml, do I also need a weblogic-ra.xml?
    Has anybody a sample for the WebSphere MQ resource adapter?
    Thanks very much,
    Juergen

    Here's an example resource adapter configuration you can use
    * weblogic-ra.xml - http://pastie.org/294590
    * note: you have to edit ra.xml manually to change transaction type from Local to XA, etc.
    This configures:
    * the resource adapter (needed for MDBs) to the jndi name wmq/Connector
    * a queue for outbound messages to the jndi name wmq/Queue1
    a connection factory for outbound messages to the jndi name wmq/ConnectionFactory
    Here's an example MDB that uses the above adapter
    * ejb-jar.xml - http://pastie.org/294594
    * weblogic-ejb-jar.xml - http://pastie.org/294597
    * note: useJNDI doesn't seem to work on WLS. Otherwise, you could setup the queue in your weblogic-ra.xml and then reference the jndi name in the ejb-jar.xml. This limitation clutters the ejb-jar.xml with implementation details of websphere, which are tricky to inject (deployment plan, xslt, etc.). That said, this does work.
    * note: If you want consistent control of the amount of consumers you have on a queue, set the ejb-jar.xml activation-config maxPoolDepth == weblogic-ejb-jar.xml max-beans-in-free-pool
    This configures:
    * an mdb instance listening on a specific WMQ destination
    I hope this helps. It is the result of may months of effort between Bea and IBM, and with me in the middle! ;)
    Cheers,
    -Adrian
    Edited by: ferncam1 on Oct 17, 2008 5:31 AM

  • Resource Adapter errors in WebLogic 10.3

    Hi,
    I'm getting ClassCastException from coherence 3.5.3 resource adapter in WebLogic 10.3.
    I've already tried to install resource adapter as a separate deploy and inside ear file, but get same errors.
    Has anybody already managed to use this adapter along with weblogic 10.3 ? The error occurs when I try to get a NamedCache object. The distributed cache named "cache" is up and running since I manage to get and put objects into cache by using NamedCache from CacheFactory (CacheFactory.getCache("cache")).
                   ctx = new InitialContext();
                   // the transaction manager from container
                   tx = (UserTransaction) ctx.lookup("java:comp/UserTransaction");
                   tx.begin();
                   adapter = new CacheAdapter(ctx, "tangosol.coherenceTx", CacheAdapter.CONCUR_PESSIMISTIC ,CacheAdapter.TRANSACTION_REPEATABLE_GET, 300);
                   NamedCache cache = adapter.getNamedCache("cache", getClass().getClassLoader());
                   cache.put(1, 11);
                   Integer estoqueGet = (Integer)cache.get(1);
    2010-06-05 20:24:02.859/96.703 Oracle Coherence GE 3.5.3/465 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/
    a
    2010-06-05 20:24:02.969/96.813 Oracle Coherence GE 3.5.3/465 <Info> (thread=Cluster, member=n/a): Failed to satisfy the variance: allowed=16, actual=47
    2010-06-05 20:24:02.969/96.813 Oracle Coherence GE 3.5.3/465 <Info> (thread=Cluster, member=n/a): Increasing allowable variance to 19
    2010-06-05 20:24:03.344/97.188 Oracle Coherence GE 3.5.3/465 <Info> (thread=Cluster, member=n/a): This Member(Id=2, Timestamp=2010-06-05 20:24:03.078, Address=1
    0.10.10.10:8089, MachineId=2570, Location=machine:ACCENTUR-1FAF0A,process:8036, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1) joined cluste
    r "cluster:0xDDEB" with senior Member(Id=1, Timestamp=2010-06-05 20:23:06.562, Address=10.10.10.10:8088, MachineId=2570, Location=machine:ACCENTUR-1FAF0A,proces
    s:6300, Role=CoherenceServer, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1)
    2010-06-05 20:24:03.438/97.282 Oracle Coherence GE 3.5.3/465 <D5> (thread=Cluster, member=n/a): Member 1 joined Service Management with senior member 1
    2010-06-05 20:24:03.438/97.282 Oracle Coherence GE 3.5.3/465 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistributedCache with senior member 1
    2010-06-05 20:24:03.656/97.500 Oracle Coherence GE 3.5.3/465 <D5> (thread=Invocation:Management, member=2): Service Management joined the cluster with senior se
    rvice member 1
    2010-06-05 20:24:04.125/97.985 Oracle Coherence GE 3.5.3/465 <D5> (thread=TcpRingListener, member=2): TcpRing: connecting to member 1 using TcpSocket{State=STAT
    E_OPEN, Socket=Socket[addr=/10.10.10.10,port=3748,localport=8089]}
    2010-06-05 20:24:04.141/97.985 Oracle Coherence GE 3.5.3/465 <Info> (thread=[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)', memb
    er=2): Loaded cache configuration from "zip:D:/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/coherenceapp/v3byxq/war/WEB-
    INF/lib/coherence.jar!/coherence-cache-config.xml"
    2010-06-05 20:24:04.438/98.282 Oracle Coherence GE 3.5.3/465 <D5> (thread=DistributedCache, member=2): Service DistributedCache joined the cluster with senior s
    ervice member 1
    2010-06-05 20:24:04.453/98.297 Oracle Coherence GE 3.5.3/465 <D5> (thread=DistributedCache, member=2): Service DistributedCache: received ServiceConfigSync cont
    aining 258 entries
    2010-06-05 20:24:04.547/98.391 Oracle Coherence GE 3.5.3/465 <D4> (thread=DistributedCache, member=2): Asking member 1 for 128 primary partitions
    2010-06-05 20:24:04.828/98.672 Oracle Coherence GE 3.5.3/465 <Error> (thread=DistributedCache, member=2): An exception (java.io.IOException) occurred reading Me
    ssage Response Type=21 for Service=DistributedCache{Name=DistributedCache, State=(SERVICE_STARTED), LocalStorage=enabled, PartitionCount=257, BackupCount=1, Ass
    ignedPartitions=0, BackupPartitions=0}
    2010-06-05 20:24:04.828/98.672 Oracle Coherence GE 3.5.3/465 <Error> (thread=DistributedCache, member=2): Terminating DistributedCache due to unhandled exceptio
    n: java.io.IOException
    2010-06-05 20:24:04.828/98.672 Oracle Coherence GE 3.5.3/465 <Error> (thread=DistributedCache, member=2):
    java.io.IOException: Class initialization failed: java.lang.ClassCastException: com.tangosol.run.xml.SimpleElement
    at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:1946)
    at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2273)
    at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2219)
    at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:60)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
    at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
    at com.tangosol.coherence.component.net.message.DistributedCacheResponse.read(DistributedCacheResponse.CDB:2)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:123)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    at java.lang.Thread.run(Thread.java:619)
    Class: com.tangosol.run.xml.SimpleElement
    ClassLoader: weblogic.utils.classloaders.ChangeAwareClassLoader@15fe77a finder: weblogic.utils.classloaders.CodeGenClassFinder@2a865b8 annotation: coherenceapp@
    WebAppCoherence
    ContextClassLoader: weblogic.utils.classloaders.ChangeAwareClassLoader@15fe77a finder: weblogic.utils.classloaders.CodeGenClassFinder@2a865b8 annotation: cohere
    nceapp@WebAppCoherence
    at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:1961)
    at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2273)
    at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2219)
    at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:60)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
    at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
    at com.tangosol.coherence.component.net.message.DistributedCacheResponse.read(DistributedCacheResponse.CDB:2)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:123)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    at java.lang.Thread.run(Thread.java:619)
    2010-06-05 20:24:04.844/98.688 Oracle Coherence GE 3.5.3/465 <D5> (thread=DistributedCache, member=2): Service DistributedCache left the cluster
    java.lang.RuntimeException: Failed to start Service "DistributedCache" (ServiceState=SERVICE_STOPPED)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:8)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:29)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:39)
    at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache$Router(SafeCacheService.CDB:1)
    at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache(SafeCacheService.CDB:46)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:878)
    at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1088)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:304)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
    at com.tangosol.coherence.ra.component.connector.resourceAdapter.cciAdapter.CacheAdapter$ManagedConnection$Connection$Interaction.execute(CacheAdapter.C
    DB:35)
    at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:329)
    at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:271)
    at ServletCoherence.doGet(ServletCoherence.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Exception: java.lang.RuntimeException: Failed to start Service "DistributedCache" (ServiceState=SERVICE_STOPPED)
    java.lang.RuntimeException: Failed to start Service "DistributedCache" (ServiceState=SERVICE_STOPPED)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:8)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:29)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:39)
    at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache$Router(SafeCacheService.CDB:1)
    at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache(SafeCacheService.CDB:46)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:878)
    at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1088)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:304)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
    at com.tangosol.coherence.ra.component.connector.resourceAdapter.cciAdapter.CacheAdapter$ManagedConnection$Connection$Interaction.execute(CacheAdapter.C
    DB:35)
    at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:329)
    at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:271)
    at ServletCoherence.doGet(ServletCoherence.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    The problem may be related to having more than one coherence.jar and tangosol.jar in the classpath. Can you verify that you only have one of those in the classpath?
    /Christer

  • WebLogic Server 10.0 MP1: Error in resource adapter deployment

    When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
    An error occurred during activation of changes, please see the log for details.
    weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
    java.util.logging.LoggingPermission.(java.lang.String)
    The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
    In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
    permission javax.management.MBeanTrustPermission "register";
    permission java.util.logging.LoggingPermission "control";
    When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
    For me this seems to be a bug in WebLogic 10.0MP1.
    Best,
    Manfred

    Re: Installation error: Weblogic Server 10.0 MP2

  • Weblogic-ra.xml for resource adapter

    Hi
    We are trying to deploy Oracle Centraloffice on weblogic 10.3
    But after configuring resource adapter which resides inside Central office application's EAR file, are application stops working.
    It give us No classdef found error, basically it stops finding the JAR files which resides inside the application.
    Resource adapter is configured to read file system for incoming JAR files and then process them, but if it starts working then are application stops working.
    We are configuring the resource adapter's weblogic-ra.xml with the weblogic 9.10 schema in which everything is bundled inside <outbound-resource-adapter> tag

    What is the correct way of looking up a resource adapter from another resource adpater? The JNDI name of my resource adapter is "StorageFactory" and I am doing a lookup like:
              Context ctx = new InitialContext();
              ctx.lookup("StorageFactory")
              Is this a correct way to lookup?

  • JCA Resource adapter deployment in Weblogic server

    Hi,
    I have deployed a resource adapter successfully in Weblogic server and works fine.My resource adapter has weblogic-ra.xml and ra.xml available under meta-inf folder.I have provided some properties in weblogic-ra.xml and ra.xml but unable to see the same properties when i open the resource adapter settings page in the the weblogic administration console
    I want to change resource adapter properties from weblogic adminstration console but dont see the properties which i used during deployment.
    Can someone help with identifying the issue or if i have to do something different.
    Appreciate any help.
    Thanks
    S

    Not sure what might be causing this behavior. Property values in ra/weblogic-ra.xml should be displayed on the console (http://machine:port/console). I think I have experienced similar issue only to realize that console only displays 10 properties and other properties are displayed after pressing Next link on the page.
    How many proprieties you have? What are getting displayed and what properties are not getting displayed?
    Manoj

  • JNDI lookup() for a Resource Adapter fails

    Hi guys,
    I've deployed a Resource Adapter on Weblogic (v10.3.4). It's JNDI name is: jca/HelloAdapter
    Moreover, in the Outbound Connection Pools tag, I've created a javax.resource.cci.ConnectionFactory entry with JNDI name: eis/HelloAdapter.
    I want to write a simple Java test to lookup my Resource adapter. The code I am using is the following:
          Hashtable<String, String> properties = new Hashtable<String, String>();
          properties.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
          properties.put(Context.PROVIDER_URL, "t3://localhost:8001");
          properties.put(Context.SECURITY_PRINCIPAL, "weblogic");
          properties.put(Context.SECURITY_CREDENTIALS, "weblogic1");
          Context ctx = null;
          try {
              ctx = new InitialContext(properties);
              javax.resource.cci.ConnectionFactory cf =
                (javax.resource.cci.ConnectionFactory) ctx.lookup("jca/HelloAdapter");
          } catch (NamingException e) {
              e.printStackTrace();
          }I get the following exception:
    javax.naming.NameNotFoundException: No Object found:  jca/HelloAdapter|null
         at weblogic.connector.deploy.JNDIHandler.lookupObject(JNDIHandler.java:881)
         at weblogic.connector.deploy.JNDIHandler.getObjectInstance(JNDIHandler.java:843)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:424)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)Any ideas please ? Thank you for your time
    Regards,
    George

    Sorry guys,
    I suppose my thread subject is out of the scope of the specific list.
    Sorry for the inconvenience

  • Send message to WebSphere MQ resource adapter - how?

    Hi,
    has anybody a working sample how an Weblogic EJB can write to an MQ queue via the WebSphere MQ resource adapter?
    http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj40010_.htm
    I took Adrian Cole's sample from
    WebSphere MQ resource adapter  and Weblogic - how?
    the message driven bean works, but for outbound I couldn't get it to work.
    I used
         @Resource(name = "wmq/ConnectionFactory")
         private javax.jms.ConnectionFactory queueConnectionFactory;
         Connection connection = null;
         connection = queueConnectionFactory.createConnection();
         Session sess = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
         MessageProducer messageProducer = sess.createProducer(queue);
         messageProducer.send(msg);
         connection.close();
    But then I get
    javax.jms.JMSException: [JMSPool:169819]There was an error with a resource pool used to pool JMS sessions: weblogic.common.ResourceException: 0:javax.jms.JMSException: MQJCA1018:Only one session per connection allowed.
    Can't I use the Resource Adapter to trigger an MDB and write in the same application to the same Resource Adapter?
    Thanks,
    Juergen

    By using @Resource you activate Session pooling [http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jms/j2ee.htm]. Although you constantly create and close the connection, you end up with one connection and multiple Sessions created out of it when there is sufficient concurrency. In JCA, ManagedConnection represents a single Resource (because it also deals with JDBC). In JMS, a Session is a resource. Session pooling violates the requirement "one resource per managed connection" which is what MQ Resource Adapter is telling [http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj40030_.htm].
    Some possible solutions:
    * Set max-beans-in-free-pool 1 in weblogic-ejb-jar.xml
    * disable wls Session pooling by simply looking up using InitialContext.lookup. WLS session pool is redundant because resource adapters usually pool connections [http://download.oracle.com/docs/cd/E12840_01/wls/docs103/resadapter/connect.html]. Define outbound resource adapter use its connection factory.

  • Multiple EARs packaging the same resource adapter -- Weblogic Application S

    Hello,
    I had a question regarding JNDI and deploying multiple applications (EAR's) which package the same resource adapter running on Webloigc Application Server 9.1. I have an EAR file, ear1, which contains a resource adapter with connection factory with JNDI name say 'xyz' specified in the weblogic-ra.xml file. I have another EAR file, ear2, which again packages the same resource adapter with the same connection factory with JNDI name 'xyz'. Upon activating the 2nd EAR file, I get an exception 'javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.', as seen below:
    <May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'JMS2JMS_eInsightweblogic2'.>
    <May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:217)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
    Truncated. see log file for complete stacktrace
    javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
    at weblogic.connector.outbound.RAOutboundManager.getConnectionFactory(RAOutboundManager.java:721)
    at weblogic.connector.deploy.JNDIHandler.getConnectionFactory(JNDIHandler.java:1017)
    at weblogic.connector.deploy.JNDIHandler.lookupObject(JNDIHandler.java:871)
    at weblogic.connector.deploy.JNDIHandler.getObjectInstance(JNDIHandler.java:845)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    Truncated. see log file for complete stacktrace
    It seems like the 2nd EAR is trying to go across and lookup the connection factory from the 1st EAR. Does weblogic bind the RA's connection factory jndi name in the global jndi and is not specific to each EAR? Is there some flag or switch I can turn on to make the JNDI specific to each EAR?
    My weblogic deployment descriptor for the ra looks like the following:
    <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
    http://www.bea.com/ns/weblogic/90/weblogic-ra.xsd">
    <jndi-name>JMS2JMS_eInsightDeployment4_stcbpelra</jndi-name>
    <enable-access-outside-app>false</enable-access-outside-app>
    <enable-global-access-to-classes>false</enable-global-access-to-classes>
    <outbound-resource-adapter>
    <connection-definition-group>
    <connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
    <connection-instance>
              <b><jndi-name>BPELConnectionFactory</jndi-name></b>
              <connection-properties>
              <pool-params>
              <initial-capacity>0</initial-capacity>
              <max-capacity>10000</max-capacity>
              <capacity-increment>1</capacity-increment>
              <shrinking-enabled>true</shrinking-enabled>
              <shrink-frequency-seconds>60</shrink-frequency-seconds>
              <match-connections-supported>false</match-connections-supported>
              </pool-params>
              <properties>
                   <property>
                        <name>BPELConnectionFactory</name>
                        <value>BPELConnectionFactory</value>
                   </property>
              </properties>
              </connection-properties>
         </connection-instance>
    </connection-definition-group>
    </outbound-resource-adapter>
    </weblogic-connector>

    Thanks for the reply... in my case this would be done by the active synch process so no GUI form is required. I will be getting a list of application ID for the user by LDAP AS. One i get it i will have to parse it and get the list of application user id. I am passing those ID;s to a workflow where I am forming the resource name as you mentioned
    for example:
    If i get user1#user2#user3 from AS i am separating them based on # using split and getting 3 different user id;s
    now i am forming a string with the resource name and passing it to the sub process in which i am checking out the user object, setting the user attributes and checking in the new view.
    user1#LDAP
    user2#LDAP|1
    user3#LDAP|2
    Problem ; When i run this user1 is getting created in LDAP but user2 and user3 are not. There entry is getting created in IDM.
    When I open the IDM object I get a yellow triangle (warning) and if I open the user object and hit save button IDM creates the user account on the LDAP.
    any help for further solving this problem would be appreciated.
    Regards,

  • Inqmy resource adapter for SAP with Bea Weblogic Server

              Hi everybody,
              Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic server
              It works well with INQMY server, but with BEA I'm getting a lot of problems creating
              the connections.
              Thanks in advance.
              Xavi.
              

    All,
              Here are the steps we (used for internal testing) had to perform to get
              IN-Q-MY adapter for SAP to work with WebLogic:
              The wli.adapter.inqmy.sapr3.spi package contains extensions to the
              In-Q-My J2EE Connector Architecture classes to overcome some limitations
              in the base implementation classes. To get around these issues, we had
              to extend their R3ManagedConnectionFactory, R3ConnectionManager, and
              R3ConnectionFactory classes.
              * The javax.resource.spi.ManagedConnectionFactory implementation
              does not over-ride the equals and hashCode methods correctly. This
              causes problems with WLS 6.1.
              * There is a bug in their javax.resource.spi.ConnectionManager
              implementation for non-managed uses of the adapter. Consequently, their
              adapter cannot be used in a non-managed scenario.
              * The javax.resource.cci.ConnectionFactory class does not support
              the getConnection() method that does not take any arguments (it throws a
              null pointer exception).
              I am attaching the classes discussed above.
              Cheers,
              Chris
              Torsten Friebe wrote:
              > Hi,
              >
              > does anybody know where to get a trail version - if one exists - of IN-Q-MY
              > application server or the resource adapter?
              >
              > Thanks, regards
              > Torsten
              >
              > "Xavi" <[email protected]> schrieb im Newsbeitrag
              > news:[email protected]...
              >
              >>Hi everybody,
              >>
              >>Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic
              >>
              > server
              >
              >>?
              >>
              >>It works well with INQMY server, but with BEA I'm getting a lot of
              >>
              > problems creating
              >
              >>the connections.
              >>
              >>Thanks in advance.
              >>Xavi.
              >>
              >>
              >
              >
              package wli.adapter.inqmy.sapr3.spi;
              import java.io.Serializable;
              import javax.resource.ResourceException;
              import javax.resource.cci.Connection;
              import javax.resource.cci.ConnectionSpec;
              import javax.resource.spi.ConnectionManager;
              import javax.resource.spi.ConnectionRequestInfo;
              import javax.resource.spi.ManagedConnection;
              import javax.resource.spi.ManagedConnectionFactory;
              import com.inqmy.r3adapter.R3ConnectionSpec;
              import com.inqmy.r3adapter.R3ManagedConnectionFactory;
              * Extends the In-Q-My implementation to allow for getConnection() with no
              * connection spec, i.e. use the default configured connection parameters.
              public class R3ConnectionFactory
              extends com.inqmy.r3adapter.R3ConnectionFactory
              implements com.bea.connector.IProxyMarker {
              private R3ConnectionSpec m_cspec;
              public R3ConnectionFactory(ConnectionManager cm, R3ManagedConnectionFactory mcf)
              throws ResourceException {
              super(cm, mcf);
              String strClientNumber = mcf.getClientNumber();
              if (strClientNumber == null) {
              throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+mcf);
              String strLanguage = mcf.getLanguage();
              if (strLanguage == null) {
              throw new javax.resource.spi.IllegalStateException("Language not set for "+mcf);
              String strUserName = mcf.getUserName();
              if (strUserName == null) {
              throw new javax.resource.spi.IllegalStateException("UserName not set for "+mcf);
              String strPassword = mcf.getPassword();
              if (strPassword == null) {
              throw new javax.resource.spi.IllegalStateException("Password not set for "+mcf);
              m_cspec = new R3ConnectionSpec(strClientNumber, strLanguage, strUserName, strPassword);
              public Connection getConnection(ConnectionSpec connectionSpec)
              throws ResourceException {
              if (connectionSpec == null) connectionSpec = m_cspec;
              return super.getConnection(connectionSpec);
              package wli.adapter.inqmy.sapr3.spi;
              import java.io.Serializable;
              import javax.resource.ResourceException;
              import javax.resource.spi.ConnectionManager;
              import javax.resource.spi.ConnectionRequestInfo;
              import javax.resource.spi.ManagedConnection;
              import javax.resource.spi.ManagedConnectionFactory;
              * Extends the In-Q-My implementation to over-ride the
              * allocateConnection method to return a CCI connection vs. a ManagedConnection
              public class R3DefaultConnectionManager
              implements ConnectionManager, Serializable {
              public R3DefaultConnectionManager() {}
              public Object
              allocateConnection(ManagedConnectionFactory mcf, ConnectionRequestInfo cri)
              throws ResourceException {
              ManagedConnection mc = mcf.createManagedConnection(null, cri);
              return mc.getConnection(null, cri);
              package wli.adapter.inqmy.sapr3.spi;
              import javax.resource.spi.ConnectionManager;
              import javax.resource.spi.ConnectionRequestInfo;
              import javax.resource.spi.ManagedConnection;
              import javax.security.auth.Subject;
              * Extends the In-Q-My implementation to get around some problems encountered
              * while running on WebLogic:
              * <ul>
              * <li>Must over-ride default implementation of equals and hashCode method</li>
              * <li>Needed to provide my version of the CCI ConnectionFactory</li>
              * <li>Needed to provide my version of the default ConnectionManager for the
              * non-managed scenario use case</li>
              * </ul>
              public class R3ManagedConnectionFactory
              extends com.inqmy.r3adapter.R3ManagedConnectionFactory {
              private int m_iHashCode;
              transient private com.inqmy.r3adapter.R3ConnectionRequestInfo t_cri = null;
              public R3ManagedConnectionFactory() {
              super();
              java.rmi.server.UID uid = new java.rmi.server.UID();
              m_iHashCode = uid.hashCode();
              public Object createConnectionFactory() {
              // need to install our own default connection manager because In-Q-My
              // version causes a ClassCastException in CCI ConnectionFactory
              // getConnection
              return createConnectionFactory(new R3DefaultConnectionManager());
              public ManagedConnection createManagedConnection(Subject subject, ConnectionRequestInfo cri)
              throws javax.resource.ResourceException {
              // need to check for null on the ConnectionRequestInfo object because the
              // In-Q-My R3ManagedConnection ctor does not check for null
              if (cri == null) cri = getDefaultConnectionRequestInfo();
              return new com.inqmy.r3adapter.R3ManagedConnection(this, subject, cri);
              public Object createConnectionFactory(ConnectionManager connectionManager) {
              // need to supply a connection factory that can deal with getConnection
              // that does not take a ConnectionSpec
              try {
              return new R3ConnectionFactory(connectionManager, this);      
              } catch (javax.resource.ResourceException re) {
              re.printStackTrace();
              throw new java.lang.IllegalStateException(re.getMessage());
              com.inqmy.r3adapter.R3ConnectionRequestInfo getDefaultConnectionRequestInfo()
              throws javax.resource.spi.IllegalStateException {
              if (t_cri == null) {
              String strClientNumber = this.getClientNumber();
              if (strClientNumber == null) {
              throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+this);
              String strLanguage = this.getLanguage();
              if (strLanguage == null) {
              throw new javax.resource.spi.IllegalStateException("Language not set for "+this);
              String strUserName = this.getUserName();
              if (strUserName == null) {
              throw new javax.resource.spi.IllegalStateException("UserName not set for "+this);
              String strPassword = this.getPassword();
              if (strPassword == null) {
              throw new javax.resource.spi.IllegalStateException("Password not set for "+this);
              t_cri = new com.inqmy.r3adapter.R3ConnectionRequestInfo(strClientNumber, strLanguage, strUserName, strPassword);
              return t_cri;
              public boolean equals(Object obj) {
              if (obj == null) return false;
              if (obj == this) return true;
              if (!this.getClass().isInstance(obj)) return false;
              R3ManagedConnectionFactory mcf = (R3ManagedConnectionFactory)obj;
              return compare(getClientNumber(), mcf.getClientNumber()) &&
              compare(getLanguage(), mcf.getLanguage()) &&
              compare(getUserName(), mcf.getUserName()) &&
              compare(getPassword(), mcf.getPassword()) &&
              compare(getServerName(), mcf.getServerName()) &&
              compare(getSystemNumber(), mcf.getSystemNumber());
              protected final boolean compare(final Object obj1, final Object obj2) {
              if (obj1 == obj2) return true;
              if (obj1 != null) {
              return obj1.equals(obj2);
              } else {
              if (obj2 == null) {
              return true;
              } else {
              return false;
              public int hashCode() { return m_iHashCode; }
              

  • Inbound Resource Adapter problem on WebLogic 9

    Hi,
              I have a problem with inbound resource adapter deployed on WebLogic 9 when it's Work instance in run() tries to create an endpoint configured to RA via endpointActivation() - a call to MessageEndpointFactory's createEndpoint() method blocks if casted to interface that a receiving MDB implements!
              Or, to look at the code:
              endpoint = (MyMessageListener)factory.createEndpoint(null);
              will block. If a cast is removed the call does not block anymore but (of course) it is no longer possible to call an MDB.
              Any hints?

    Turning on Debugging, found the problem:
              <[JCABindingManager] activationSpec=null>
              <[JCABindingManager] The activationSpec is null, deActivation is skipped>
              In the application.xml, I had
              1. ejb (mdb) module and then
              2. connector module
              Changed the application.xml to
              1. connector module and then
              2. ejb (mdb) module
              container then called endpointDeactivation on undeployment.

  • Call another WebLogic's EJBs from resource adapter?

              Is it possible to call another WebLogic's EJBs from a resource adapter?
              A call to the javax.naming.InitialContext(Hashtable environment) results in a
              VersioningError:
              weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPATH:
              (BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 , 6.1.4.0)
              not compatible with
              (BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
              at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
              at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
              at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
              at weblogic.kernel.Kernel.initialize(Kernel.java:122)
              at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
              at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
              at java.lang.Class.newInstance0(Native Method)
              at java.lang.Class.newInstance(Class.java:232)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at java.lang.reflect.Constructor.newInstance(Native Method)
              I'm not sure it will always be possible to match the version, although here upgrading
              the SP3 to SP4 will probably be done soon.
              Does anyone have experience with this?
              Or better: is there any documentation on this issue?
              

              Hi Hans,
              Here is the link for Weblogic SP3 / SP4 vulnerability and comparison for
              http://216.239.53.104/search?q=cache:RqqaQ3HZdwoJ:www.nipc.gov/cybernotes/2003/cyberissue2003-06.pdf+Versioning+Error+in+BEA+weblogic+6.1+SP3+and+SP4&hl=en&ie=UTF-8
              Hope this will help you.
              Let me know if u have any further problems.
              rgds
              KSK
              "Hans Bausewein" <[email protected]> wrote:
              >
              >
              >Is it possible to call another WebLogic's EJBs from a resource adapter?
              >
              >A call to the javax.naming.InitialContext(Hashtable environment) results
              >in a
              >VersioningError:
              >
              >weblogic.common.internal.VersioningError: Incompatible service packs
              >in CLASSPATH:
              >(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 ,
              >6.1.4.0)
              >not compatible with
              >(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
              > at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
              > at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
              > at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
              > at weblogic.kernel.Kernel.initialize(Kernel.java:122)
              > at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
              > at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
              > at java.lang.Class.newInstance0(Native Method)
              > at java.lang.Class.newInstance(Class.java:232)
              > at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
              > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > at javax.naming.InitialContext.init(InitialContext.java:217)
              > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > at java.lang.reflect.Constructor.newInstance(Native Method)
              >
              >
              >
              >I'm not sure it will always be possible to match the version, although
              >here upgrading
              >the SP3 to SP4 will probably be done soon.
              >
              >Does anyone have experience with this?
              >
              >Or better: is there any documentation on this issue?
              >
              

  • JCA Resource Adapter CCI

    Has anyone found a reference application that properly uses the JCA CCI specification? I would like to test a Resource Adapter against the standard rather than against my understanding of the standard.

    try:
    http://www.fawcette.com/javapro/2002_02/magazine/features/tmodi/

  • Connectivity from ejb to Resource Adapter at run time

              I am facing a problem regarding the look-up of the Resource Adapter from the Ejb.
              To explain :
              1.I have The <resource-ref> tag in ejb-jar.xml set at follows :
              <resource-ref>
              <description>The Resource Adapter</description>
              <res-ref-name>eis/RitResourceAdapter</res-ref-name>
              <res-type>javax.sql.DataSource</res-type>
              <res-auth>Container</res-auth>
              </resource-ref>
              and the <resource-description> tag in weblogic-ejb-jar.xml as follows:
              <resource-description>
              <res-ref-name>eis/RitResourceAdapter</res-ref-name>
              <jndi-name>eis/RitResourceAdapterConnectorJNDINAME</jndi-name>
              </resource-description>
              2.Even though I have mentioned the res-ref-type as javax.sql.Datasource , in my
              code I have done :
              rcf = (RitConnectionFactory) c.lookup ("java:comp/env/eis/RitResourceAdpapter");
              Where rcf is the my Resource Adapter specific Connection Factory (one which
              I have prepared and not
              the javax.resource.cci.ConnectionFactory). So this means the connection
              object which I get is casted to
              get my own application specific connection object.
              3.When I run my servlet (which looks up the Ejb and which in turn looks-up the
              Resource Adapter) it works fine to the point that it looks-up the bean successfully
              but fails when it tries to do so for Resource Adapter. The Server exception is
              as follows :
                        javax.ejb.EJBException
                        - with nested exception:
              [javax.naming.NameNotFoundException: Unable to resolve comp/env/eis/RitResourceAdpapter/
              Resolved: 'comp/env/eis' Unresolved:'RitResourceAdpapter' ; remaining name '']
              It will be great to hear about any solution from you people.
              For your information :
              I am using Weblogic 6.1, both the ejb jar and the RitResourceAdapter.rar has been
              deployed and the relevant portion of the weblogic-ra. xml is :
              <connection-factory-name>LogicalNameOfRitResourceAdapter</connection-factory-name>
              <jndi-name>eis/RitResourceAdapterConnectorJNDINAME</jndi-name>
              Regards,
              Ritwik
              

    > My question here is that is there any way where I do not put the queue name in the sender adapter at design time and based on the data availability in the queue let the sender adapter know the queue name to be processed at run time.
    Unfortunately for JMS Sender CC it is not possible, but other way around is possible. I.e. you can dynamically choose the receving queue names by using ASMA "JMSReplyTo" in JMS Sender CC.
    Regards,
    Sarvesh

  • BINDING.JCA-12510 JCA Resource Adapter location error in SOA 11g Suite

    Hi,
    I am just testing one simple SOA Application in SOA 11g Suite. Created a SOA Composite Application with one DB Adapter at designtime all worked fine with DB Adapter. But when I deploy the Application on the server I get the following error:
    The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/soademoDatabase'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/soademoDatabase. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ".Do I need to jndi-name in weblogic-ra.xml if so what is the exact location. Any help is appreciated.
    Thanks

    I did but still not able to connect now getting the following error. I went to the Weblogic Console, clicked on deployments, selected DBAdapter, clicked on configuration ,
    and then I don't see outbound configurations instead it shows Outbound Connection Pools, Under Outbound Connection Pools tab I clicked on New and it asked to select Outbound Connection Group I selected the one that was already there (with JNDI eis/DB/SOADemo) and then created my JNDI which was added to the default Outbound Connection Group and in the end it asked to save the Plan.xml which I saved it under a new directory created under soa directory. But still am not able to connect.
    How do I create my own Connection Group as don't want to use the defualt one out there.
    After creating the JNDI Name it asks for saving the Plan.xml file. Where exactly we save this file. Are there any standards.
    Why can't I update any properties when I click on the new JNDI name it takes to Settings for javax.resource.cci.ConnectionFactory --> Outbound Connection Properties but there I see a save buttn but I can't make any changes.
    BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception. Missing Property: [DBManagedConnectionFactory.userName]. You may have set a property (in _db.jca) which requires another property to be set also. Make sure the property is set in the interaction (activation) spec by editing its definition in _db.jca. . ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. Is there any documentation that lists all these steps as I couldn't find it anywhere. The guide only talks abou DBAdapter but how to configure etc can't find any info. Any help is appreciated.
    Thanks.

Maybe you are looking for

  • Mail not showing messages in Time Machine

    As per attached snapshot, I cannot restore any mail messages as I have no idea what they are, the subject lines, etc. are completely blank. Any ideas on how to fix this? JKB http://homepage.mac.com/dr.jkb/Sites/images/Picture.jpg

  • Images in Finder but not in iPhoto

    Just restored using Backup 3.1.2. Most pics & Events appear in iPhoto '08. However, most current pics (March to August) do not. I can see the pics using "Show Package Contents" of Picture/iPhoto Library/Data -OR- Picture/iPhoto Library/Originals If I

  • USB Superdrive will not burn my cd

    I have a macbook pro Retina display and the USB Superdrive.  For some reason the superdrive will not burn cd's. Help please...US

  • What are the SAP backup for SID (SAP DB), Master & MSDB?

    Dear Experts, I'm trying to do backup via tcode DB13 for full backup.  Somehow there are 3 database option for me to choose, which are Master, MSDB and SID (SAP DB). I just wonder what are they. My concern is which of the above options consists all t

  • Import problems - colour shift

    When I import photos, several of the HSL values change as the previews are created (the photos turn bright purple)! I have to go through them all individually pressing - Control / shift / R - to reset the settings.