SSO in resource adapter : Subject=NULL

Error while trying to use SingleSignOn in resource adapter deployed in WebLogic server 8.1
Hi,
To support SSO in Resource Adaptor all steps were produced as described in WebLogic site:
http://e-docs.bea.com/wls/docs81/secmanage/credential_maps.html#1100282
I've created a user in default security realm mapped to some credentials, after deploying of Resource Adaptor I'm trying to send username/password from third party app to deployed adapter throw WebLogic and ManagedConnectionFactoryImpl::createManagedConnection called but with Subject=NULL, is there need some additional steps to configure credentials mapping beside described on BEA site ?

Hi Udo,
I hope Post configuration is completed.
Have you imported the BASIS component. If not import the BASIS component which is specified in the installation guide.
hope it will solve your problem
Regards,
Ramesh P

Similar Messages

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

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; }

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.

Adapter Engine null

Hi,
I have an error with the adapter engine (PI 7.0):
under Runtime Workbench / Component Monitoring / Integration Server
Adapter Engine is shown with red light: "Adapter Engine null".
Details are saying: "No correct URL exists for the RuntimeCheck. Enter a correct URL in the System Landscape Directory"
If i go to SLD / Administration / Content Maintenance and choose (left side) subject "Landscape Description" and (right side) "XI Adapter Framework" and choose Adapter Engine, there is an empty field "ISMsgURL", which is described with "The URL that points to the integration server. The URL is used to transfer messages from the adapter framework to the integration server".
I can fill it with the URL to IE, but unfortunately it is again empty, if i restart the Java Stack.
Does anybody have had that error or does anybody have an idea how to solve it?
Best regards,
Udo

Hi Udo,
I hope Post configuration is completed.
Have you imported the BASIS component. If not import the BASIS component which is specified in the installation guide.
hope it will solve your problem
Regards,
Ramesh P

ClassCastException by using deployed resource adapter

Dear community team,
I try to create an connection for my web application (war file) running on SAP Web Application Server to access an enterprise information system (Apache JackRabbit) by using JCA and deployed resource adapter. The resource adapter "jackrabbit-jca-1.3.3.rar " is provided Apache Jackrabbit.
http://jackrabbit.apache.org/downloads.cgi
I changed some deployment descriptor configuration and deployed it successfully by using Deployment Tools. With the Visual Administrator I also could check the JNDI object and finded an entry in connector container.
The JNDI lookup worked fine and it returned a object type "JCARepositoryHandle" (I could analyse its type and attributes in debugging modus).If I tried to cast the object "JCARepositoryHandle", I got an ClassCastException.
Do you have any adoption why I only saw the returned object "JCARepositoryHandle" in debugging modus but it wasnt possible cast and to use it.
If you need any more information, please let me know.
Thanks for your support.
PS: Please have also a look in the attached source an configuration files:
Java servlet class
===================================================================
Connection connection = null;
 Context initctx = null;
 try {
 //get the initial JNDI context
 Hashtable env = null;
 initctx = new InitialContext();
 // perform JNDI lookup to get the connection factory
 JCARepositoryHandle rep = (JCARepositoryHandle)initctx.lookup("deployedAdapters/jcr/Repository/shareable/jcr/Repository");
connector-j2ee-engine.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector-j2ee-engine SYSTEM 'connector-j2ee-engine.dtd'>
<connector-j2ee-engine>
 <jndi-name>jcr/Repository</jndi-name>
 <pool-params>
 <max-connections-number>10</max-connections-number>
 <max-time-to-wait-connection>120</max-time-to-wait-connection>
 <expiration-control>
 <connection-lifetime>900</connection-lifetime>
 <run-cleanup-thread>300</run-cleanup-thread>
 </expiration-control>
 </pool-params>
</connector-j2ee-engine>
ra.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE connector PUBLIC
 '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN'
 'http://java.sun.com/dtd/connector_1_0.dtd'>
 <connector>
 <display-name>Jackrabbit JCR Adapter</display-name>
 <vendor-name>Apache.org</vendor-name>
 <spec-version>1.0</spec-version>
 <eis-type>JCR Adapter</eis-type>
 <version>1.6</version>
 <license>
 <description>Not required</description>
 <license-required>false</license-required>
 </license>
 <resourceadapter>
 <managedconnectionfactory-class>org.apache.jackrabbit.jca.JCAManagedConnectionFactory</managedconnectionfactory-class>
 <connectionfactory-interface>javax.jcr.Repository</connectionfactory-interface>
 <connectionfactory-impl-class>org.apache.jackrabbit.jca.JCARepositoryHandle</connectionfactory-impl-class>
 <connection-interface>javax.jcr.Session</connection-interface>
 <connection-impl-class>org.apache.jackrabbit.jca.JCASessionHandle</connection-impl-class>
 <transaction-support>XATransaction</transaction-support>
 <config-property>
 <config-property-name>HomeDir</config-property-name>
 <config-property-type>java.lang.String</config-property-type>
 <config-property-value>C:/temp/repository</config-property-value>
 </config-property>
 <config-property>
 <config-property-name>ConfigFile</config-property-name>
 <config-property-type>java.lang.String</config-property-type>
 <config-property-value>C:/temp/repository/repository.xml</config-property-value>
 </config-property>
 <reauthentication-support>false</reauthentication-support>
 </resourceadapter>
 </connector>

The reason for the ClassCastException was the class loader issue.

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.

Java.lang.ClassCastException: org.jboss.resource.adapter.jdbc.WrappedConnec

Hi,
I am using Connection pooling in Jboss 4.0 GA. In my application we are using Oracle object like ARRAY,TAB type etc for transactions.
My problem is that I have getting following error:
java.lang.ClassCastException: org.jboss.resource.adapter.jdbc.WrappedConnection
Can u tell me how to resolve this issue.
Regards,
Sanket Akre

i was facing the same issue .
try this one :
java.sql.Connection conn = null;
      javax.naming.InitialContext ic = new javax.naming.InitialContext();
      // for Jboss JNDI_NAME = java:OracleDS
      javax.sql.DataSource ds = (javax.sql.DataSource)ic.lookup(projsp.UtilityFunctions.getProperty("JNDI_NAME"));
      org.jboss.resource.adapter.jdbc.WrappedConnection wc=(org.jboss.resource.adapter.jdbc.WrappedConnection)ds.getConnection();
      conn = (oracle.jdbc.driver.OracleConnection)wc.getUnderlyingConnection();

Access BAPIs Using the SAP Java Resource Adapter

Hi experts,
Can someone tell me how to Access BAPIs Using the SAP Java Resource Adapter?

hi Shweta,
Please refer the step by step procedure:
1. Start the deploy tool of the SAP J2EE Application Server with the DeployTool.bat in the directory //<SAP J2EE Engine Installation Directory/.../j2ee/deploying.
2. Choose Project → New Project and enter a name for the new project.
3. Click on the Deployer tab.
4. From the menu path, choose Deploy → EAR → Load Module and select the sapjra.rar file.
5. For the newly created node sapjra.rar, choose Server Settings → Identity Subjects and select Caller Impersonation as authentication type, so that the J2EE user data is used to log on to the ABAP system.
6. Make sure that the J2EE Application Server is running. Connect to the J2EE Application Server with Deploy → Connect.
7. Deploy the sapjra.rar using the menu Deploy → Deployment → Deploy Module.
8. Enter SAPJRADemo as application name and start the application.
9. Close the deploy tool.
10. Start the Visual Administrator again.
11. Select the Cluster tab and switch to <Server Node> → Services → Connector Container.
12. Click on the Runtime tab and choose sap.com/SAPJRADemo → eis/SAPJRADemoFactory.
13. Choose Managed Connection Factory → Properties. On this page, you need to specify the logon data for the ABAP system. There is already some dummy data visible in the property list if no real system data has been specified so far.
14. To change the value of a property, select the property in the list, change the value underneath it, and add the changes using the Add button. At the end, do not forget to save all changes by pressing the button Save Changes. The user configured for the SAP JRA must be the user authorized to read metadata of function modules.

Ear access standalone Resource Adapter problem

I deployed a standalone resource adapter. Then I deployed a ear.
In the ear, I try to look up the resource adapter, I got an exception:
javax.naming.NameNotFoundException: No Object found: MyRA|null
In weblogic-ra.xml, I added:
<enable-global-access-to-classes>true</enable-global-access-to-classes>
but still have the problem.
However, when I embeded the RA in the ear and deploy the ear, I can get the RA by lookup()
Is there anyway I can get successfully look up the standalone RA?
P.S.
My problem seems to be similar with an earlier post "Access Resource Adaptar outside the EAR".
Access Resource Adaptar outside the EAR
My problem is different.
I lookup the RA in an ear deployed in the server.
However, I'm not using EJB to lookup the RA.
server version: weblogic server 11g r1
Thanks a lot

My RA runs correctly after deployment, I can see my RA in the JNDI tree.
I just did some more tests.
I use the following way to look up:
InitialContext ctx = new InitialContext();
ConnectionFactory cf = (ConnectionFactory) ctx.lookup("MyConnectionFactory");
If I look up it in an EJB, I can get the object.
But when I look up in a servlet, no object can be found.
The servlet is in a war embeded in the ear.

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

JCA 1.5 Resource Adapter integration

Hi,
I'm trying to create a custom JCA 1.5 Resource Adapter that has to be integrated with the BPEL PM. I already have the JCA Resource Adapter done,
and I want to integrate it with BPEL. I'm following the document http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter%20Development%20cookbook.pdf, but I'm not able to make it work. Is there more documentation? any tutorial, example...
Thanks,
Miquel

Hi Manfred,
This is the error page that I'm getting. Seems an internal BPEL PM error. I can't make the Audit Trail because I'm getting an error page, not the result page.
Yes, I have the CCI ManagedConnectionFactory deployed as eis/imEIS
What do you mean with the records must be of type XMLRecord? This is what the XMLRecordConverter has to do, no?
To convert javax.resource.cci.Record <-> oracle.tip.adapter.api.record.XMLRecord
Thanks for your help,
Miquel
Oracle BPEL Process Manager Full Cycle
An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
Attachments:
Build Information:
Oracle BPEL Server version 10.1.2.0.2
Build: 2196
Build time: Tue Jan 10 12:31:53 UTC 2006
Build type: release
Source tag: BPEL_10.1.2.0.2_GENERIC_060110.1200
Exception Message:
[javax.servlet.ServletException]
null
Exception Trace:
javax.servlet.ServletException
at com.evermind.server.http.EvermindPageContext.handlePageThrowable(EvermindPageContext.java:595)
at com.evermind.server.http.EvermindPageContext.handlePageException(EvermindPageContext.java:537)
at ngDoInitiate.jspService(_ngDoInitiate.java:438)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
at displayProcess.jspService(_displayProcess.java:792)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Also, before I submit the form I see this on the log:
<2006-12-12 14:51:14,750> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process BPELIntegration, revision 1.0 needs to be reloaded
<2006-12-12 14:51:14,812> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT CONNECTION 4 Autocommit = false
<2006-12-12 14:51:14,843> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::closeConnection> CLOSE CONNECTION 3
<2006-12-12 14:51:14,875> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::getConnection> GOT CONNECTION 4 Autocommit = false
<2006-12-12 14:51:14,921> <DEBUG> <default.collaxa.cube.engine.data> <ConnectionFactory::closeConnection> CLOSE CONNECTION 3
<2006-12-12 14:51:14,921> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "presentation manager":
java.lang.NullPointerException
at com.collaxa.cube.xml.xsd.WSDLUtil.getInputParameters(WSDLUtil.java:33)
at com.collaxa.cube.xml.xsd.xerces.WSDLFormHandler.writeForm(WSDLFormHandler.java:82)
at com.collaxa.cube.xml.xsd.xerces.WSDLFormHandler.write(WSDLFormHandler.java:76)
at com.collaxa.cube.ejb.impl.PresentationManagerBean.getInitiateFormContent(PresentationManagerBean.java:66)
at IPresentationManagerBean_StatelessSessionBeanWrapper62.getInitiateFormContent(IPresentationManagerBean_StatelessSessionBeanWrapper62.java:81)
at com.oracle.bpel.client.BPELProcessHandle.getInitiateFormContent(BPELProcessHandle.java:383)
at ngInitiateForm.jspService(_ngInitiateForm.java:243)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
at displayProcess.jspService(_displayProcess.java:806)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)

Modify a global attribute from a Resource Adapter

I need to modify a global attribute (e.g.: firstname) from a Resource Adapter (e.g.: realCreate method).
When I try to get the context (this.getContext()) it is always null.
Any ideas please?
Thx

I get the context:
LighthouseContext lighthouseContext = SessionFactory.getServerInternalContext();and modify a other user:
WSUser wsUser = (WSUser)lighthouseContext.checkoutObject(Type.USER, "otherUser", null);
wsUser.setAttribute("globalAttribute","myValue");
lighthouseContext.checkinObject(wsUser, null);but I need to modify the current user, and he is locked by 'Configurator'.
Any ideas?
Thx

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>
 <jndi-name>BPELConnectionFactory</jndi-name>
 <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,

I need Fusion help creating a demo of BRM JCA Resource Adapter

I need Fusion help creating a demo of BRM JCA Resource Adapter.
I know BRM well but am clueless with Fusion.
I am trying to figure out what Fusion products to download and install and how I manipulate the Fusion side to manipulate BRM.
My BRM docs say:
Installing the BRM JCA Resource Adapter ->
Software requirements
(yada yada install a bunch of BRM stuff I know how to do)
The adapter must be deployed on a J2EE 1.4-compliant application server that has implemented the JCA 1.5 specification. The adapter runs only in a managed environment. (Does this imply some particular Fusion package?)
(more yada yada about installing more BRM packages I know how to do)
Deploying and configuring the BRM JCA Resource Adapter ->
Overview of the BRM JCA Resource Adapter configuration procedure
The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:
Installing the adapter on your BRM system, if you have not already done so. See Installing the BRM JCA Resource Adapter.
Generating the schema files for the adapter. See Generating the schema files for your system. (links to some BRM commands np)
Specifying how to construct XML tags. See Specifying the XML tags for extended fields. (links to an oob file included with directions on how to address BRM customizations np)
Generating the WSDL files for the adapter. See Generating the WSDL files for your system. (links to an oob file with directions to configure. I could use some help if/when I get this far)
The last two look pretty important but I haven't a clue. I pasted the text from the docs below.
Deploying the adapter on your application server. See Deploying the BRM JCA Resource Adapter on an Oracle application server.
Connecting the adapter to the BRM software. See Connecting the adapter to BRM in Oracle AS.
Deploying the BRM JCA Resource Adapter on an Oracle application server
The adapter is dependent on Java Archive (JAR) files to deploy properly. The following table lists the JAR files that the adapter requires from each application in your system.
Application
JAR files
J2EE application server
classes12.jar, connector15.jar, and jta.jar
Oracle BPEL process
bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
BRM J2EE Resource Adapter
pcm.jar and pcmext.jar
Apache
xercesImpl.jar
If you are deploying the adapter in a standalone Oracle Containers for Java EE (OC4J) instance, make sure these JAR files are available to the class loader that is loading the adapter.
If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:
Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:
<imported-shared-libraries>
<import-shared-library name="adf.oracle.domain"/>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
Save and close the file.
Restart the application server or the J2EE instance.
After you make the JAR files available, deploy the adapter on the Oracle application server by using either the Oracle Application Server (Oracle AS) Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server.
After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:
Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
Remove the following oracle.bpel.common entry (shown in bold below):
<imported-shared-libraries>
<import-shared-library name="adf.oracle.domain"/>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
Save and close the file.
Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapterDeploymentName directory.
Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:
<oc4j-connector-factories...>
<imported-shared-libraries>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
<oc4j-connector-factories>
Save and close the file.
Restart the application server or the J2EE instance.
For more information about deploying the adapter, see your application server’s documentation.
Connecting the adapter to BRM in Oracle AS
You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates oc4j-ra.xml from the packaged ra.xml. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.
Use the resource adapter home page from the Oracle AS ASC page to create connection pools and connection factories.
Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide. See download.oracle.com/docs/cd/B31017_01/web.1013/b28956/conncont.htm.
Make sure you set the pool’s Maximum Connections parameter (maxConnections XML entity) equal to or greater than the Oracle BPEL process manager’s dspMaxThreads parameter. For more information, see Oracle BPEL Process Manager Performance Tuning in Oracle Application Server Performance Guide for 10g Release 3 (10.1.3.1.0) at download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm.
Note To set up JCA Resource Adapter transaction management in BPEL, you must create a private connection pool and set its Inactive Connection Timeout property (inactivity-timeout XML entity) to 0. See About JCA Resource Adapter transaction management in BPEL for more information.
Create as many connection factories as your system needs. For each connection factory, specify the following:
The JNDI location for the connection factory.
The connection pool to use.
How to connect to BRM by using these entries:
Entry
Description
ConnectionString
Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip Server1 12006.
DBNumber
Specify the database number for the BRM database. For example, enter 1 or 0.0.0.1 for database 0.0.0.1.
InputValidation
Specifies whether to validate the input XMLRecord:
True — The adapter validates the input XMLRecord against the opcode schema.
False — The adapter does not validate the input XMLRecord.
The default is False.
This overrides any other validation parameter specified in the WSDL file.
OutputValidation
Specifies whether to validate the output XMLRecord:
True — The adapter validates the output XMLRecord against the opcode schema.
False — The adapter does not validate the output XMLRecord.
The default is False.
This overrides any other validation parameter specified in the WSDL file.
LoginType
Specifies the authentication method:
1 — The adapter logs in to BRM by using the specified login name and password.
0 — The adapter logs in to BRM by using the specified service type and POID ID.
The default is 1.
UserName
Specifies the login name the adapter uses for logging in to the BRM software.
Note This entry is required only if LoginType is set to 1.
Password
Specify the password the adapter uses for logging in to the BRM software.
Note This entry is required only if LoginType is set to 1.
PoidID
Specifies the POID ID. This entry should be set to 1.
ServiceType
Specifies the service the adapter uses to log in to the BRM software.
The default is /service/pcm_client.
You have successfully configured the adapter to connect to BRM.

I need Fusion help creating a demo of BRM JCA Resource Adapter.
I know BRM well but am clueless with Fusion.
I am trying to figure out what Fusion products to download and install and how I manipulate the Fusion side to manipulate BRM.
My BRM docs say:
Installing the BRM JCA Resource Adapter ->
Software requirements
(yada yada install a bunch of BRM stuff I know how to do)
The adapter must be deployed on a J2EE 1.4-compliant application server that has implemented the JCA 1.5 specification. The adapter runs only in a managed environment. (Does this imply some particular Fusion package?)
(more yada yada about installing more BRM packages I know how to do)
Deploying and configuring the BRM JCA Resource Adapter ->
Overview of the BRM JCA Resource Adapter configuration procedure
The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:
Installing the adapter on your BRM system, if you have not already done so. See Installing the BRM JCA Resource Adapter.
Generating the schema files for the adapter. See Generating the schema files for your system. (links to some BRM commands np)
Specifying how to construct XML tags. See Specifying the XML tags for extended fields. (links to an oob file included with directions on how to address BRM customizations np)
Generating the WSDL files for the adapter. See Generating the WSDL files for your system. (links to an oob file with directions to configure. I could use some help if/when I get this far)
The last two look pretty important but I haven't a clue. I pasted the text from the docs below.
Deploying the adapter on your application server. See Deploying the BRM JCA Resource Adapter on an Oracle application server.
Connecting the adapter to the BRM software. See Connecting the adapter to BRM in Oracle AS.
Deploying the BRM JCA Resource Adapter on an Oracle application server
The adapter is dependent on Java Archive (JAR) files to deploy properly. The following table lists the JAR files that the adapter requires from each application in your system.
Application
JAR files
J2EE application server
classes12.jar, connector15.jar, and jta.jar
Oracle BPEL process
bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
BRM J2EE Resource Adapter
pcm.jar and pcmext.jar
Apache
xercesImpl.jar
If you are deploying the adapter in a standalone Oracle Containers for Java EE (OC4J) instance, make sure these JAR files are available to the class loader that is loading the adapter.
If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:
Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:
<imported-shared-libraries>
<import-shared-library name="adf.oracle.domain"/>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
Save and close the file.
Restart the application server or the J2EE instance.
After you make the JAR files available, deploy the adapter on the Oracle application server by using either the Oracle Application Server (Oracle AS) Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server.
After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:
Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
Remove the following oracle.bpel.common entry (shown in bold below):
<imported-shared-libraries>
<import-shared-library name="adf.oracle.domain"/>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
Save and close the file.
Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapterDeploymentName directory.
Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:
<oc4j-connector-factories...>
<imported-shared-libraries>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
<oc4j-connector-factories>
Save and close the file.
Restart the application server or the J2EE instance.
For more information about deploying the adapter, see your application server’s documentation.
Connecting the adapter to BRM in Oracle AS
You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates oc4j-ra.xml from the packaged ra.xml. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.
Use the resource adapter home page from the Oracle AS ASC page to create connection pools and connection factories.
Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide. See download.oracle.com/docs/cd/B31017_01/web.1013/b28956/conncont.htm.
Make sure you set the pool’s Maximum Connections parameter (maxConnections XML entity) equal to or greater than the Oracle BPEL process manager’s dspMaxThreads parameter. For more information, see Oracle BPEL Process Manager Performance Tuning in Oracle Application Server Performance Guide for 10g Release 3 (10.1.3.1.0) at download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm.
Note To set up JCA Resource Adapter transaction management in BPEL, you must create a private connection pool and set its Inactive Connection Timeout property (inactivity-timeout XML entity) to 0. See About JCA Resource Adapter transaction management in BPEL for more information.
Create as many connection factories as your system needs. For each connection factory, specify the following:
The JNDI location for the connection factory.
The connection pool to use.
How to connect to BRM by using these entries:
Entry
Description
ConnectionString
Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip Server1 12006.
DBNumber
Specify the database number for the BRM database. For example, enter 1 or 0.0.0.1 for database 0.0.0.1.
InputValidation
Specifies whether to validate the input XMLRecord:
True — The adapter validates the input XMLRecord against the opcode schema.
False — The adapter does not validate the input XMLRecord.
The default is False.
This overrides any other validation parameter specified in the WSDL file.
OutputValidation
Specifies whether to validate the output XMLRecord:
True — The adapter validates the output XMLRecord against the opcode schema.
False — The adapter does not validate the output XMLRecord.
The default is False.
This overrides any other validation parameter specified in the WSDL file.
LoginType
Specifies the authentication method:
1 — The adapter logs in to BRM by using the specified login name and password.
0 — The adapter logs in to BRM by using the specified service type and POID ID.
The default is 1.
UserName
Specifies the login name the adapter uses for logging in to the BRM software.
Note This entry is required only if LoginType is set to 1.
Password
Specify the password the adapter uses for logging in to the BRM software.
Note This entry is required only if LoginType is set to 1.
PoidID
Specifies the POID ID. This entry should be set to 1.
ServiceType
Specifies the service the adapter uses to log in to the BRM software.
The default is /service/pcm_client.
You have successfully configured the adapter to connect to BRM.

SSO in resource adapter : Subject=NULL

Similar Messages

Maybe you are looking for