IWA integration with websphere or logic

Hi,
I was able to integrate and protect websphere sites with Basic Over LDAP Authentication Scheme. But i would like to achieve automatic logon using the IE automatic login authentication option. (Something similar to integrating IIS with IWA Scheme.) Therefore we tried authentication scheme to something similar to IIS IWA Authenciation Scheme using REMOTE_USER as challenge Parameter but it does not work.
Below is the authentication scheme we are using now and we are now facing a problem with the Challenge Parameter Field for the Authentication Scheme. Currently the WAS is using "username" and "password" to logon, so using REMOTE_USER as Challenge Parameter it will not work as i found out that REMOTE_USER is actually sending "domain/username". Is there any Challenge Parameter that i could use to pass "username" only without the domain? I believe that would solve the problem. Or is there any other alternative ways of doing it?
Details for Authentication Scheme_
Name Websphere Authenication Scheme
Description Websphere Authenication Scheme
Level 2
Challenge Method Basic
Challenge Parameter cred:REMOTE_USER
SSL Required No
Challenge Redirect
Enabled Yes
Plugins for Authentication Scheme
credential_mapping: obMappingBase=<"dc=test,dc=ovd">,obMappingFilter="(&(objectclass=inetorgperson)(uid=%REMOTE_USER%))"
Regards,
User

Hi,
thank you for confirming and i understand that. i will need to confirm when you say "Then pass the userid in the HTTP header back to the app just as you would with a normal webgate."
Does that means that upon authenication / authorization success using the ISA reverse-proxy, i will need to return a HTTP header to the webgate, something like this?
Authentication Rule has Action - On Success
Type: HeaderVar
Name: HTTP_REMOTE_USER
Return Attribute: uid
Authorization Rule has Action - On Success
Type: HeaderVar
Name: HTTP_REMOTE_USER
Return Attribute: uid
Thank you
User

Similar Messages

  • Integration with Websphere 5.0 (EJB 2.0) problems

    Hello all,
    Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
    Websphere 5.0 (using EJB 2.0).
    I have been basically binding a PersistenceManagerFactory into JNDI via
    start-up servlet, however got the exception bellow when I tried to create
    PersistenceManagerFactory (in setSessionContext of the EJB).
    <i>JDOFatalInternalException: Could not perform automatic lookup of EJB
    container's javax.transaction.TransactionManager implementation. Please ensure
    that you are running the application from within an <b>EJB 1.1</b> compliant
    EJB container, and then set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
    value to obtain the TransactionManager.</i>
    The reference to EJB 1.1 actually scared me a bit. Does this imply that
    Kodo (2.4) does not support J2EE 1.3?
    Would you know how to set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
    5.0?
    Thank you,
    Petr

    Petr-
    Is the integration with Websphere 5.0 application server officially
    supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
    Websphere. However, it should be noted that it is not as rigorously
    tested internally at SolarMetric as some other application servers (E.g.,
    JBoss and WebLogic). In short, integration is known to work, but it
    might be a little more rough around the edges than for other application
    servers (as shown in our misspelling of Websphere's TransactionManager
    implementation name).
    How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
    javax.jdo.option.ConnectionFactoryName property (see
    http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
    This is often more appropriate for applications server usage, since it
    allows you to configure pooling and other information from within the
    application server's centralized configuration.
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
    configuration we use for testing with IBM's drivers is:
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
    They shouldn't behave differently (I am guessing that the app driver is
    a type 2 driver or something), but it might be worth a shot to try using
    the net driver. If this fixes the problem, please let us know, because
    it will indicate that Kodo has a deficiency with one of IBM's drivers
    that we should look into resolving.
    Since I have been trying to integrate with App server, this is the
    initialization code that I use to bind PersistenceManagerFactory to JNDI.
    You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
    PM and start persistence operations. Note that you should also be able
    to deploy Kodo as a Resource Adapter (which allows Kodo configuration
    through the centralized Websphere configuration interface). However, I
    doubt this is part of the issue.
    So, in short, I recommend trying the following things:
    1. Using the ConnectionFactoryName to use the DataSource defined for the
    appserver, on the off chance this will fix it.
    2. Using the net driver instead of the app driver.
    3. Seeing if it will work with javax.jdo.option.Optimistic set to false
    If none of these work, please let us know, and we will continue to
    investigate other possible solutions.
    In article <[email protected]>, Petr Bulanek wrote:
    Hello Marc,
    Very good guess. Pretty much the same code worked well without App server.
    In that case, there obviously was no magic related to
    TransactionManagerFactory initialization (see bellow).
    Is the integration with Websphere 5.0 application server officially
    supported? Has anobody (that you know of) done it successfully yet?
    How do I tell Kodo to use existing Datasource managed by app server?
    Here is the basic configuration (URL, class, etc):
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2:snet
    javax.jdo.option.Optimistic=true
    javax.jdo.option.RetainValues=true
    javax.jdo.option.NontransactionalRead=true
    We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
    Since I have been trying to integrate with App server, this is the
    initialization code that I use to bind PersistenceManagerFactory to JNDI.
    You may find some funny stuff there.
    The new EESimpleConfiguration(true) construct seems to (by default) read
    the kodo.properties file that is part of the project.
    EEConfiguration conf = new EESimpleConfiguration(true);
    conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
    conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
    EEPersistenceManagerFactory pmf =
                        new EEPersistenceManagerFactory(conf);
    InitialContext ic = new InitialContext();
    ic.rebind(\"KodoPMF\", pmf);
    Thank you,
    Petr
    Marc Prud\'hommeaux wrote:
    Petr-
    It looks like DB2 doesn\'t like our attempt to close the connection
    without a rollback or commit. This is odd, since we have never
    seen this happen in our stand-alone DB2 tests. Can you let us know
    the connection details (driver, connectionURL, etc)?
    In the meantime, one possible workaround may be to turn off
    optimistic transactions (since this will cause the PM to
    only use a single Connection); can you try to specify:
    javax.jdo.option.Optimistic=false
    Also, have you tried to run this code in a non-managed environment
    (e.g., outside the application server)? I would be interested
    to know if it is related to running within an appserver.
    In article <[email protected]>, Petr Bulanek wrote:
    Hi Abe,
    Thank you for a speedo reply. You guys really are on the ball!!!
    As you suggested, the
    \\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
    did the job (for others, please note that the proper package name should
    contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
    Unfortunately, I got another problem. When running a method containing
    query (code bellow),
    I get SQLException complaining about \\\'Invalid transaction state\\\'.
    The method that executes the query is a stateless transactional Session
    bean.
    Thank you for your help,
    Petr
    --------------------------- DB2 - transaction state description
    CLI0116E Invalid transaction state.
    Explanation: There was a transaction in progress when SQLDisconnect was
    called.
    User Response: Call SQLTransact before calling SQLDisconnect.
    --------------------------- Exception ------------------------------------
    [2/01/03 16:34:19:050 EST] 563ddb8a SQL I
    com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
    D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
    PARENTX.JDOCLASSX FROM PARENTX
    [2/01/03 16:34:19:050 EST] 563ddb8a SQL I
    com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
    D:118283149 ] executing statement <369367952>: [reused=1;params={}]
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
    D:118283149 ] close:
    com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
    D:118283149 ] close connection
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
    exception when closing connection
    [2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
    com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
    was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
    Invalid transaction state. SQLSTATE=25000
    atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
    atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
    atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
    atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
    at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
    atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
    at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
    atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
    at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
    at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
    --------------------------- Failing code sample
    try {
                   PersistenceManager pm = factory.getPersistenceManager();
                   Extent ex = pm.getExtent(Parent.class, false);
                   Query q = pm.newQuery(ex, \\\"name==parName\\\");
                   q.declareParameters(\\\"String parName\\\");
                   Collection col = (Collection) q.execute(\\\"James\\\");
                   Iterator iter = col.iterator();
                   Parent pp;
                   Collection ch;
                   while (iter.hasNext()) {
                        pp = (Parent) iter.next();
                        System.out.println(pp);
                        ch = pp.getChildren();
                        Iterator it= ch.iterator();
                        while (it.hasNext()) {
                             System.out.println(it.next());
                   q.closeAll();
                   pm.close();
              } catch (Exception e) {
                   System.out.println(e);
                   throw new EJBException(e);
    Abe White wrote:
    The reference to EJB 1.1 actually scared me a bit. Does this imply that
    Kodo (2.4) does not support J2EE 1.3?
    EJB 2.0 is also supported. Sorry for the confusing error message.
    Would you know how to set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
    WSAD
    5.0?
    Try these settings:
    com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
         com.solarmetric.kodo.ee.InvocationManagedRuntime
    com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
         TransactionManagerMethod=\\\\
         com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
    Marc Prud\'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • Weblogic 9.2 ESB integration with Websphere MQ 6.0 throws MQJMS1016

    Hi
              We have setup a Websphere MQ integration where we have a weblogic server as the client.
              The MQ setup is a clean MQ installation no WAS is installed.
              Here are the MQ information
              OS: Windows 2003 R2 Entreprise Edition SP1
              MQ:
              Name: WebSphere MQ
              Version: 6.0.2.1
              CMVC level: p600-201-070323
              BuildType: IKAP - (Production)
              Here are the Weblogic server information
              OS: Windows 2003 R2 Entreprise Edition SP1
              weblogic:
              Name: Weblogic ESB
              VERSION: 9.2
              JDK: jdk150_06
              We have experience that the integration works fine. Until it becomes weekend and there are no activity between the weblogic server and the MQ.
              That is when we get the message:
              ####<2007-07-09 07:53:45 CEST> <Notice> <StdErr> <b00011100938> <esbserver> <asyncDelivery30> <<WLS Kernel>> <> <> <1183960425832> <000000> <2007.07.09 07:53:45 MQJMS1016E an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException>
              ####<2007-07-09 07:53:45 CEST> <Error> <ALSB Kernel> <b00011100938> <esbserver> <asyncDelivery30> <<anonymous>> <> <> <1183960425832> <BEA-380001> <Exception on TransportManagerImpl.sendMessageToService, com.bea.wli.sb.transports.TransportException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException
              com.bea.wli.sb.transports.TransportException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException
              at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:146)
              at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:845)
              at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:514)
              at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:620)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:585)
              at com.bea.wli.sb.transports.Util$1.invoke(Util.java:65)
              at $Proxy45.sendMessageAsync(Unknown Source)
              at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:137)
              at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:487)
              at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:354)
              at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:559)
              at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:488)
              at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:127)
              at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:319)
              at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:108)
              at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:6
              at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:834)
              at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:194)
              at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
              at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:669)
              at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:668)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:666)
              at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:304)
              at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
              at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
              at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
              at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
              at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2804)
              at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
              at java.lang.Thread.run(Thread.java:595)
              At the time we get this error we also do a thread dump to find the asyncDelivery30 and we can see what happens:
              "asyncDelivery30" RUNNABLE native
              java.net.SocketInputStream.socketRead0(Native Method)
              java.net.SocketInputStream.read(SocketInputStream.java:129)
              java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
              java.io.BufferedInputStream.read(BufferedInputStream.java:235)
              java.io.DataInputStream.readInt(DataInputStream.java:353)
              com.ibm.mq.MQInternalCommunications.timedReadInt(MQInternalCommunications.java:2698)
              com.ibm.mq.MQInternalCommunications.receiveBytesFaster(MQInternalCommunications.java:2796)
              com.ibm.mq.MQInternalCommunications.receive(MQInternalCommunications.java:1149)
              com.ibm.mq.MQSESSIONClient.lowLevelComms(MQSESSIONClient.java:2802)
              com.ibm.mq.MQSESSIONClient.MQGET(MQSESSIONClient.java:1833)
              com.ibm.mq.MQQueue.getMsg2Int(MQQueue.java:1209)
              com.ibm.mq.MQQueue.getMsg2(MQQueue.java:1066)
              com.ibm.mq.jms.MQMessageConsumer.getMessage(MQMessageConsumer.java:3194)
              com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2773)
              com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
              java.lang.Thread.run(Thread.java:595)
              The message we get from the MQ is this :
              09-07-2007 07:54:05 - Process(7772.406) User(LETMQTESTUser) Program(amqrmppa.exe)
              AMQ9208: Error on receive from host b00011100938 (10.11.64.5).
              EXPLANATION:
              An error occurred receiving data from b00011100938 (10.11.64.5) over TCP/IP.
              This may be due to a communications failure.
              ACTION:
              The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these
              values and tell the systems administrator.
              If anyone have some input/help concerning this problem. That would really be great

    - The NullPointerException looks like its being generated due to some sort of bug in MQ, so you might have some luck by contacting IBM and/or ensuring your MQ version has all the latest patches.
              - The error is being reported by WLI, which has its own newsgroup - so you might try posting there. I'm guessing that WLI tries to recover from the MQ error by closing down and re-establishing its connections to MQ.
              Tom

  • IBM websphere 6.1 integration with OAM

    Hi,
    1) Is the "interceptorClassName" Clases Name important? can i name it as other thing rather than what is stated in the documentation?
    example:
    According to the WAS integtraion guide the Interceptor classname is as: com.oblix.tai.was5.WebGate2TrustAssociationInterceptor
    Can i change it to com.oblix.tai.was5.WebGateTrustAssociationInterceptor
    2) Is there anywhere to verify that TAI is loaded properly and how do i test it?
    ================================================================================
    Interceptor classname is under WAS, Secure administration -> applications, and infrastructure -> Trust association -> Interceptors
    Thanks and Regards,
    Grey

    Thanks! i got the figure out. but i encouter something else while integrating with WAS
    im trying to integrate OAM with WAS without reverse proxy and i followed the documentation religiously. in the documentation
    Defining an Oracle Access Manager Policy Domain for WebSphere without Reverse Proxy_
    Without reverse proxy, disabling SSO in WAS is required. I will need to protect the WebSphere Administrative Console SSL URL. Otherwise, I will not be able to access the console after disabling SSO in WAS. I have create the policy domain as the documentation.
    ■ Resource Type: http
    ■ Host Identifier: xxx
    ■ URL Prefix: _/ibm/console; and /admin_
    ■ Description: Used by NetPointWASRegistry TAI component.
    Authorization Rules: Click the Authorization Rules tab, click Add, and then create and save an authorization rule to allow access to WebSphere Administrative
    Console resources. For example:
    a. Click General, then enter and save:
    * Name: Allow Administrator.
    * Description: Allow access to WebSphere Administrative Console resources.
    * Enabled: Yes
    * Allow takes Precedence: Yes
    Without Reverse Proxy: Click Actions, then enter and save the following WebSphere Administrative Console SSL URL for Authentication Success. For example:
    Redirect to: https://hostname:port/ibm/console *<- i found out that once I had this implemented. I will be going in an authentication cycle (keep getting authenticated and redirected back to the same page) because it is part of the resources I had it declare previously to be protected.*
    Is there a work around or is it due to documentation error?

  • I/PM ERP Integration with Oracle Application Server instead of Websphere

    I'm just starting an integration between IPM 7.7.1 and JDE EnterpriseOne v8.12.
    In the EIS documentation for 7.7.1 has some specific assumptions regarding integrations with JDE EnterpriseOne (8.12), specifically using IBM Websphere. We opted to go with the Oracle Portal and Oracle Application Server. Just curious if the integration approach/instructions would require some adjustments because of the non-Websphere selection my JDE team chose. Or if it just plan won't work.
    Jim

    Hi Jim,
    The reason that the documentation specifically spells out IBM Websphere is most likely because it was the application server that we developed and tested with at the time. The important requirement for this type of integration is that this server be an Intel based server running a Microsoft OS. The reason for this is because there are dlls with the Oracle IPM product that enable communication between the IPM functions and the JDE Business functions. If the Enterprise server for JDE is intel based then a JAS can exist on the same server, the dlls can be on that machine and the extra server is not required. This server is only required if the Enterprise server is not intel based. As far as your choice to use Oracle Application Server goes, I really have no basis to say if this works or not. My thought is that it shouldn't matter as long as the JAS server is an intel based, 32 bit server running a Microsoft OS. There are many other variables and lots of experience implementing this type of integration with JDE within the Oracle IPM consulting team. Give us a call if we can help.
    Hope this helps,
    Matt

  • Error integrating OBIEE portlet with WebSphere Portal

    Hi
    I am trying to integrate OBIEE 10.1.3.4.1 with Websphere Portal.
    I perform following steps :
    1. Installed OBIEE and created a report at url "http://punitp63969d:9704/analytics/saw.dll?Dashboard"
    2. Modified portlet.xml of sawjsr168portlets.war as follows
    <preference>
    <name>oracle.bi.presentation.sawserver.URL</name>
    <value>http://punitp63969d:9704/analytics/saw.dll?Dashboard</value>
    <read-only>false</read-only>
    </preference>
    <preference>
    <name>oracle.bi.presentation.portlets.jsr168.reportui.AdminUserName</name>
    <value>Administrator</value>
    <read-only>false</read-only>
    </preference>
    <preference>
    <name>oracle.bi.presentation.portlets.jsr168.reportui.AdminPwd</name>
    <value>Administrator</value>
    <read-only>false</read-only>
    </preference>
    <preference>
    <name>oracle.bi.presentation.portlets.websphere.SuperuserSlotId</name>
    <value>sawseveradmin</value>
    <read-only>false</read-only>
    </preference>
    where Administrator/Administrator is user-id/password for OBIEE and
    sawseveradmin is name of credential vault in WebSphere-Portal.
    3. Deployed the war on WebSphere Portal and got portlet disable with following error in log :
    WSVR0200I: Starting application: PA_SAWReport
    9/4/09 18:42:52:067 IST 000001ff ApplicationMg A WSVR0204I: Application: PA_SAWReport Application build level: Unknown
    9/4/09 18:42:52:708 IST 000001ff WebGroup A SRVE0169I: Loading Web Module: SAWReport.
    9/4/09 18:42:52:973 IST 000001ff VirtualHost I SRVE0250I: Web Module SAWReport has been bound to default_host:10000,:80,:10002,:10015,:10016,:443,:10023,:10026,:10040,:10035.
    9/4/09 18:42:53:130 IST 000001ff ApplicationMg A WSVR0221I: Application started: PA_SAWReport
    9/4/09 18:42:59:692 IST 00000037 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /searchfeed/myserver/scopes has not been defined.
    9/4/09 18:43:26:458 IST 00000037 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /searchfeed/myserver/scopes has not been defined.
    9/4/09 18:43:50:318 IST 000000a5 ServletWrappe I SRVE0242I: PA_SAWReport [wps/PA_SAWReport] Oracle_Business_Intelligence_Report_View_Portlet: Initialization successful.
    9/4/09 18:43:50:521 IST 000000a5 MimeResponseI E com.ibm.ws.portletcontainer.core.impl.MimeResponseImpl getWriter EJPPC0176W: Invalid content type
    9/4/09 18:43:50:661 IST 000000a5 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Oracle_Business_Intelligence_Report_View_Portlet. Exception thrown : javax.servlet.ServletException: java.lang.IllegalStateException: No content type set.
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:369)
    Caused by: java.lang.IllegalStateException: No content type set.
    at com.ibm.ws.portletcontainer.core.impl.MimeResponseImpl.getWriter(MimeResponseImpl.java:114)
    at com.siebel.analytics.web.portlets.jsr168.ReportUI.checkUser(ReportUI.java:852)
    at com.siebel.analytics.web.portlets.jsr168.ReportUI.doView(ReportUI.java:167)
    at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
    at com.siebel.analytics.web.portlets.jsr168.ReportUI.doDispatch(ReportUI.java:1058)
    at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletFilterChainImpl.doFilter(PortletFilterChainImpl.java:128)
    at com.ibm.wps.propertybroker.standard.filter.C2APortletFilter.doFilter(C2APortletFilter.java:185)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletFilterChainImpl.doFilter(PortletFilterChainImpl.java:120)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:573)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:114)
    at com.ibm.isclite.container.collaborator.PortletServletCollaborator.doRender(PortletServletCollaborator.java:68)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
    at com.ibm.ws.portletcontainer.rrd.RRDServerPortletServletCollaborator.doRender(RRDServerPortletServletCollaborator.java:123)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
    at com.ibm.ws.portletcontainer.cache.CacheCollaborator.doRender(CacheCollaborator.java:92)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
    at com.ibm.wps.pe.pc.waspc.core.impl.PortletServletCollaboratorImpl.doRender(PortletServletCollaboratorImpl.java:156)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
    at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:273)
    ... 219 more
    Please help me resolve this issue.Thanks in advance.

    I'm getting the same error on WebSphere 6.1.5. Is there any solution for this?

  • Integration with MQ 6.0

    We have a requirement to integrate Oracle BPM with MQ version 6.0. The trigger point for instance creation would be the messages subscibed from MQ. Please let me know if there is any example showing the integration or any helpful documentation. Thanks in advance.

    Hi,
    I don't know of any documentation, but here are the steps a friend documented a couple years ago:
    The MQ installer makes some changes to the environment variables, so restart Windows to ensure current settings are used.
    1) Start the MQ Queue Manager
    To start the queue manager, launch the WebSphere MQ Explorer (Start->Programs->IBM WebSphere MQ->WebShere MQ Explorer). Right-click on the queue manager and select Start:
    2) Enable WebSphere MQ Publish/Subscribe (i.e. JMS Topic) Functionality
    WebSphere MQ does not support JMS Topics out-of-the box. To enable this functionality, you'll need to do the following (QM_beaee06 is the name of my queue manager, be sure to use the correct queue manager name for your installation):
    REM -- This assumes you've installed in the default MQ directory 
    PROMPT> cd C:\Program Files\IBM\WebSphere MQ\bin
    REM -- This will check the broker status.  After installation it should be inactive
    REM -- IF YOU GET A DIFFERENT MESSAGE, BE SURE THE QUEUE MANAGER IS RUNNING
    PROMPT> dspmqbrk -m QM_beaee06 
    WebSphere MQ Publish/Subscribe broker for queue manager QM_beaee06 not active.
    REM -- Start the broker 
    PROMPT> strmqbrk -m QM_beaee06 
    WebSphere MQ Publish/Subscribe broker started for queue manager QM_beaee06.
    REM -- Now we can verify the broker is running 
    PROMPT> dspmqbrk -m QM_beaee06 
    WebSphere MQ Publish/Subscribe broker for queue manager QM_beaee06 running
    REM -- Last, we need to run a WebSphere MQ script to enable publish/subscribe 
    PROMPT> runmqsc QM_beaee06 < ..\Java\bin\MQJMS_PSQ.mqsc 
    8 MQSC commands read. 
    No commands have a syntax error. 
    All valid MQSC commands were processed. 3) Create a Sample Queue and Topic
    While you can use WebSphere MQ Explorer to add destinations using a GUI, it's quite easy to do it from the command line:
    REM -- This assumes you've installed in the default MQ directory 
    PROMPT> cd C:\Program Files\IBM\WebSphere MQ\bin
    REM -- This will launch an interactive shell where you'll enter the subsequent commands
    REM -- Note that the runmqsc shell does NOT provide any prompts
    PROMPT> runmqsc 
      define qlocal (ALBPM.SAMPLE.QUEUE) 
      define qlocal (ALBPM.SAMPLE.TOPIC) 
      end4) Configure the JMS Administered Objects in JNDI
    WebSphere MQ makes it very easy to use Sun's File System JNDI repository, so that's what you'll use here (if your client already has a JNDI repository in place, it can be substituted here). Before configuring JNDI, create this directory: C:\JNDI-Directory
    You'll also need to edit the JMSAdmin.config configuration file to specify your JNDI connection parameters – you can find this file in the C:\Program Files\IBM\WebSphere MQ\Java\bin directory. To use the file-based repository, ensure the following values are used:
    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory 
    PROVIDER_URL=file:/C:/JNDI-DirectoryOnce the JNDI parameters are set, you're ready to launch the MQ's JMS Administration command line interface:
    REM -- This assumes you've installed in the default MQ directory 
    PROMPT> cd C:\Program Files\IBM\WebSphere MQ\Java\bin
    REM -- This will launch an interactive shell where you'll enter the subsequent commands
    REM -- Note that the 'hostname' will default to 'localhost' and could have been omitted
    PROMPT> JMSAdmin 
    InitCtx> define q(albpmQueue) queue(ALBPM.SAMPLE.QUEUE) 
    InitCtx> define qcf(albpmQCF) transport(client) hostname(localhost)
    InitCtx> define t(albpmTopic) topic(ALBPM.SAMPLE.TOPIC) 
    InitCtx> define tcf(albpmTCF) transport(client) hostname(localhost)
    InitCtx> end 5) Test WebSphere MQ with a Stand-Alone JMS Client
    Use a generic JMS client to test. This enables you to quickly test connectivity to WebSphere MQ (or any other JMS broker). Always test integration with back-end services (whether it's a JMS broker or some other type of integration) from outside Oracle BPM before attempting it with the tool -- once it's working ouside Oracle BPM, it's typically trivial to get things working inside Oracle BPM.
    6) Configure Oracle BPM to Use WebSphere MQ
    Once you have successfully tested WebSphere MQ (or another JMS provider) using the stand-alone client, you can use the same configuration with Oracle BPM.
    a. Verify the following Java libraries have been added as an external resource:
    com.ibm.mq.jar
    connector.jar
    com.ibm.mqjms.jar
    dhbcore.jar
    fscontext.jar
    providerutil.jar
    The Java External Resource should not be marked versionable.
    b. Verify the JNDI Provider is configured with the same configuration as the stand-alone client. The resource type is (somewhat confusingly) a J2EE Application Server and the security principal and credential are both left blank.
    c. Verify the JMS Message Service external resource is correctly configured for the queue. It will lookup the Queue Connection Factory as well as the Queue itself using the JNDI resource previously defined.
    d. Similarly verify another JMS Message Service resource has been configured for the topic. It too will use the same JNDI resource.
    7) Execute the Oracle BPM Process
    a. Add Global Automatic activities (one for the queue and another for the topic) that each create a new work item each time a message is received. The runtime properties settings for these should be respectively:
    Global automatic type: "Executes when an event occurs"
    Listener class: "Fuego.Msg.MessageQueueListener"
    Component event types: "anyMsg: Java.Lang.Object"
    and
    Global automatic type: "Executes when an event occurs"
    Listener class: "Fuego.Msg.TopicListener"
    Component event types: "anyMsg: Java.Lang.Object"
    The logic in the Global Automatic has:
    componentArguments as Any[String]
    componentArguments = [
    "contextFactory" : "com.sun.jndi.ldap.LdapCtxFactory",
    "providerURL" : "ldap://fgdal-test1:389/dc=fuegotech,dc=us",
    "securityPrincipal"  : "cn=root",
    "securityCredentials": "password",
    "factoryName"        : "cn=qcf1",
    "queueName"          : "cn=q1"
    logMessage "MQLIstener:: MQListener initialized with this arguments:\n" + componentArguments
        using severity = DEBUG
    logMessage "MQ Message Received is " + arg.anyMsg using severity = DEBUG
    processargs as String[String]
    processargs["mqData"]=String(arg.anyMsg)
    // this creates the instance in the process passing the message into the input argument "mqData"
    result2 = ProcessInstance.create(arguments : processargs,argumentsSetName:"BeginIn")b. Deploy the process and start the server. Login to the Oracle BPM WorkSpace. Add a message to the queue and/or topic and the work item instance should show up in the Inbox immediately.
    Hope this helps,
    Dan

  • Brief discussion on SAP XI and its' Integration with SAP MDM.

    Hi,
    I have never worked on SAP XI.
    I am discussing it on brief, please give your valuable replies.
    SAP XI consists of System Landascape Directory(SLD).
    SLD Consists of Business System and Techinical System.
    Technical System contains all information about the software
    component. The Business System consists of Inbound and Outbound Business
    System which are used as logical names for data transfer.
    There is communication Channel for Receiver and Sender Business System and n agreement
    is signed between Sender and Receiver.
    Outbound Interface defined for Business System Outbound and Techical System associated
    with the Business System,
    Inbound Interface defined for Business System Inbound and Techical System associated
    with the Business System.
    In SAP NetWeaver XI Integration Directory, we have defined the Integration Scenarios,
    Actions, Interface Objects, Mapping Objects, Adapters Objects.
    Mapping Object defines the Structure and Value Mapping.
    Adapter Objects defines the Adapter program which implements RFC Adapter, FTP Adapter logic.
    FTP Adapter is used for XI-MDM Communication.
    RFC Adapter is used for XI-ECC Communication.
    Integration Repository: Both Outbound and Inbound Interfaces are Mapped with Value mapping and
    Structure Mapping inside Integration Repository.
    The File Adapter takes the File from the Outbound port of MDM System
    and sends it as IDOC to Receiver Business System.
    Value Mapping must be done between Sender and Receiver interfaces.
    Value Mapping is done by XSLT or Java based program.
    SAP NetWeaver XI Integration Server at runtime:
    Message Split, Interface Determination, Receiver Identifaction, Mapping, Techincal Routing
    and Call Adapter Proccess are done.
    In SAP XI 3.0 and MDM 5.5:
    Step 1: Create busines system as service.
    Step 2: Create communication channel for each business service. If the system can communicate
    through different channels, then create all possible channel types if necessary.
    Step 3: Create receiver agreement between the systems.
    Step 4: Interface determination:
    - Here you see for the first time the software component mentioned;
    there are some special requirements regarding this software component in relation to the customizing ID mapping.
    - To modify this software component, the customer needs to copy the SAP standard delivered software component
    into its own namespace. The customer is able to modify to create archives
    for the customized ID mapping.
    Receiver determination.
    Configure an FTP Server on the MDS.
    Create a send folder for outbound messages using outbound port(s) for
    remote systems(s).
    Create receive folder inbound messages using inbound port(s) for remote systems.
    This ia all about concept of SAP XI Infractsture and its' Integration with SAP MDM 5.5.
    Regards
    Kaushik Banerjee

    Hi Kaushik,
    You must be aware of File types that MDM Import Manager can Import i.e. we have XML, Excel etc. Now there are two transactions to extract data from R3
    1. MDMGX -
             - For lookup table extraction
             - Output in XML format which MDM can import without using XI.
              - FTP can be configured to put the file in the desired folder which will be then picked by Import Server.
    2. MDM_CLNT_EXTR -
              - For Main table records.
              - Output is in Idoc format which MDM doesn't understand hence we need XI in between which converts Idoc file received from R3 into XML which can then be imported using Import Manager or Import Server. For this we need to implement XI Scenario that consists of Source System, Receiver System, Type of Data etc.
    Just a basic understanding...
    Regards,
    Jitesh Talreja

  • OBIEE 11.1.1.5  Integration with HFM 11.1.1.3

    Hi,
    We are in the process of integrating OBIEE 11.1.1.5 with HFM 11.1.1.3. We have client installed and we require Hyperion Application Builder(HAB) which is compatible with BEA web logic server 10.3.5. If possible Please share the link.
    we found HAB(7.2.0) which is compatible with BEA weblogic server 8.1, but it is not compatible with weblogic server 10.3.5.
    Please help if someone find related information ASAP.
    Thanks.

    Hi,
    Any suggestions please.
    Regards,

  • Can JMS work with websphere (3.5 or +)

    Hi ,
    I am aware that JMS is designed to work with J2EE architecture but can I use it with websphere?
    Regards,
    Dukkar Lee

    Hi again. Saw your post on Web Shere. We use the pre built adaptor for Web Logic and Web Sphere from SpiritSoft - I dont think any one else has this?

  • Query on eRec integration with ECC (HCM)

    Hello All,
    We are using standalone eRec server on ehp4. Now my scenario is
    1) While raising the requisition request i need the Org unit to be pulled from the HR system. Currently i maintained the following switched with RFC's
    in HCM system i mainateined a witch
    1)RECFA DTCBA     ED1_200     (RFC Connection in E-Recruiting System) - RFC is created in the HR System
    (RFC type 3)
    Switches mainteined in Erec system
    2)RECFA HRRFC     CSD_130     Logical System of Connected HR System - Here i maintained RFC which is created in erec system
    Now when i create a requition in erec when i choose the Org Unit drop down I am unable to see the org units which are mainained in the HR system
    AM i missing any config or any functionality or any troubleshooting required.
    Pls guide me with you inputs
    2) Also i would like to know the data transfer of the applicant data from erec system to hr system while i do the data transfer.
    What all i need to configure for this and any prerequsitive is needed from my end.
    Plss help me on this
    Thanks & Regards
    Vijay Mohan G

    Hello Deepak,
    Thanks for sharing the Note
    When i am looking into the Note for I2 A scenario it is saying that i should maintain switches in T77SO table i.,e
    In which system should i maintain the folwwing switches i.,e in eRec system or HCM System. Pls let me know
    HRALX HRAC X Activates HR integration
    HRALX OBPON ON Activates O-BP integration
    HRALX PBPHR ON Distributes employees from
    connected HR system
    HRALX USRAC X Creates relationship to user
    RECFA HRRCF Logical system, not
    required when using XI
    technology for the data
    transfer but definitely
    required for integration in
    Organizational
    Management
    Logical system of the coupled
    HR system
    RECFA RECCE Specifies whether
    Concurrent Employment
    (CE) is active in the SAP ERecruiting
    system.
    Concurrent Employment is
    active in the SAP E-Recruiting
    system (parameter is relevant
    as of Release 604)
    RECFA DTCBA Logical system (required on
    the HR system side) , not
    required when using XI
    technology for the data
    transfer
    RFC connection to the SAP ERecruiting
    system

  • Siebel 8.1 integration with BI Publisher 11g

    Hello,
    I'm currently trying to integrate BI Publisher reporting with Siebel 8.1 at work. We've followed the guide named " [BI Publisher for Siebel Applications Guide|http://download.oracle.com/docs/cd/E14004_01/books/Reports/ReportsTOC.html] ", which you can find in the Oracle BI Publisher documentation website: [http://www.oracle.com/technetwork/middleware/bi-publisher/documentation/index.html].
    The problem is that this guide is meant to be used with the Oracle 10g version and we are using BI Publisher 11.1.1.5.0 (client's request).
    We installed the new version without problems and reached the step "[Copying JAR Files to the Oracle BI Publisher Server|http://download.oracle.com/docs/cd/E14004_01/books/Reports/ReportsIntegrate11.html#wp551748]".
    But since BI Publisher 11g runs on a Web Logic Server, instead of an Oracle Application Server (correct me if I'm wrong, I'm kind of new to the whole Oracle world), the file structures have changed and we cannot find the directory where we're supposed to copy those JAR files.
    I kept reading the guide, in case we could skip this step and maybe find where those files are supposed to be later... but then again I found myself in a similar problem, since I need to place a Siebel WSDL file in a BI Publisher directory for importing, which I cannot find either.
    Does anybody know how to accomplish this task or if it is even possible to use these software versions together? Could anyone at least point us to the right direction on where to look for this information?
    Thank you in advance.

    We actually ran into a similar problem where I work. I created a support web ticket for our issue and the response is that BIP 11G is not supported for integration with Siebel 8.1, or any other version for that matter. Oracle is currently working on a fix to integrated the latest version of Siebel with BIP.
    There advice to me was to downgrade to BIP 10G for the time being.

  • WebLogic with WebSphere MQ as an XA resource

    I have been using WebLogic MDBs with WebSphere MQ as an external JMS provider. We just bought MQ Extended Client that would let external transaction managers do XA management with MQ. I have looked at IBM's document @
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf. This document indicates that Weblogic cannot be used to do XA with MQ; only three txn managers are mentioned - CICS, Encina, and Tuxedo.
              I don't believe that to be true because it says that it can be used with any XA compliant transaction manager. Is anyone aware of documents showing how to configure a WebLogic server (expecially MDBs) to use MQ extended client to do XA?

    WL is an XA compliant TM, and many customers use it with MQ. For more information, you can start with this FAQ:
              http://e-docs.bea.com/wls/docs81/faq/interop.html#268632
              Also see the notes I've appended below.
              Finally, you can search this newsgroup - you will see that your question comes up quite a bit.
              Tom, BEA
              JMS Integration of Foreign Vendors with BEA WebLogic Server
              The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
              For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
              JMS Integration Overview
              - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
              - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
              - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
              - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
              - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
              - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
              - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Integration with 8.1 Details
              A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              This document refers to helpful new 8.1 features, which simplify integration. These include:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              And are also summarized here (under interoperability):
              http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Also read the MDB documentation, which extensively covers integrating foreign vendors:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
              Integration with 6.1 and 7.0 Details
              Read the "Using Foreign JMS Providers With WLS" white-paper:
              http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              Note that this white-paper does not take into account 8.1 features.
              For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              Notes on MQ Remote Capable XA Clients
              Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
              - Required on WLS where MQ objects are bound into JNDI:
              com.ibm.mq.jar, com.ibm.mqjms.jar
              - Required only if MQ objects are bound into JNDI on a different server:
              com.ibm.mq.jar
              If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
              Notes on Oracle AQ Integration
              If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
              http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
              Caveats:
              The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
              Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
              The solution doesn't seem to support transactions, it may be possible to extend it to do so.
              MDB Thread Pool Notes
              WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
              http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
              (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
              MDB Concurrency Notes
              Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
              Design Guide-Lines and Performance Tuning Notes
              The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

  • BI Publisher Performance integrated with OBIEE 11g

    Has anyone seen issues around the performance of rendering the BI Publisher frame when it is integrated with an OBIEE dashboard (11g)?
    If I create a simple BI Publisher off a simple data model (Select 1 from dual). I open the BIP report within the BI Publisher environment (XmlpServer) and it opens in seconds.
    When I open this same report within the OBIEE Web Catalog or place it on a dashboard page I have seen it take upwards of 40-50 seconds to render the frame then the report. The time seems to me more around rendering the frame.
    Usually when you initiate your first session you see the longest rendering time, subsequent runs of the report are lower but still higher then the few seconds it takes in the BIP environment.
    Has anyone else seen this issue, we opened a ticket with Oracle and it seems they are leaning toward creating a BUG around this. Just wanted to see what others were experiencing and if they identified the source of the issue. Thanks.

    Hi Dustin,
    The FMW security model in BI Publisher means it is integrated into OBIEE - I believe it's the default. If you're using authenticating and authorising via weblogic then I can't think of a good reason to use BI Server authentication in publisher, you should be using FMW security.
    In answer to your question tThere was no bug raised. The work around for us was using document 1338007.1. In your case that doesn't seem necessary since you're using OVD already.
    Edit - should just add that if your OVD authentication is set up in the repository then you need to shift that to the weblogic server security model and remove any authentication logic from the repository. After that the FMW security model for publisher should work.
    http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10543/privileges.htm
    Regards,
    Robert
    Edited by: Robert Tooker on Nov 3, 2011 2:07 AM

  • HR Integration with CRM doesn't create employee in CRM

    Hello all;
    We are using SAP CRM 5.0 SP08 and SAP ECC 6.0. I am trying to setup the HR-CRM integration and did everything that must be done in my opinion. The IDOC is created succesfully from the ERP side via PFAL and BD87 in CRM shows "green" status records for the IDOC but no business partner is created. I read the blog /people/vikash.krishna/blog/2006/10/15/replicating-hr-master-data-part-1 , examined the SAP notes 934372, 312090, 550055 but there is no result. May you please help me in solving the problem?
    Best Regards,
    Erkan

    Hi Erkan
    Did you follow all the following steps
    Setting up Transfer of Employee (HR Master) from R/3 to CRM
    1. Logical system XXX assigned to R/3 client XXX. Logical system YYY assigned to CRM client YYY – view through SCC4
    2. Create RFC Destination YYY  for CRM client YYY in R/3 and
    Server ID  with user details and client YYY.
    3. Transaction code SALE :  Application Link Enabling (ALE) &#61664; Modelling and Implementing Business Processes &#61664; Maintain Distribution Model and Distribute Views. (Direct transaction code : BD64)
    Go to change mode and select ‘Create Model view’.
    You get a popup. Fill in the details – Technical name, short text and validity
    Select ‘Add message type’ from the application tool bar.
    Fill in the following details
    Model view : HRCRM
    Sender logical system : XXX
    Receiver logical system : YYY
    Message type : HRMD_ABA
    Note : Only this message type works for employee transfer.
    4.Save the model. From the same screen select the distribution model and from the menu Environment &#61664; Generate partner profiles
    Don’t change anything in the next screen. Simply Execute.
    4.Distribute the distribution model HRCRM
    Select the distribution model. From the menu bar, Edit &#61664; Model View &#61664; Distribute
    You get a dialog showing the receiver logical system. Execute.
    You get a log ‘Model view HRCRM has been created in target system YYY
    5.Go to the CRM system and check up whether this model has been created.
    Transaction code BD64
    The model has got copied. No changes can be made in CRM
    6. Generate partner profiles for the distribution model in CRM by selecting
    Environment &#61664; Generate partner profiles.
    In the next screen, do not make any changes and Execute.
    Partner profiles can be seen in transaction WE20
    <b>Delta Download Settings</b>
    7. So far, the above settings will ensure the initial download. However for any changes / new employees to be transferred, i.e delta changes, changes pointers need to be activated.
    In R/3, Transaction code SALE, Application Link Enabling (ALE) &#61664; Modelling and Implementing Business Processes &#61664; Master Data Distribution &#61664; Replication of Modified Data &#61664; Activate Change Pointers – Generally (BD61)
    This  activates change pointers globally for all message types.
    8. In R/3, Transaction code SALE, Application Link Enabling (ALE) &#61664; Modelling and Implementing Business Processes &#61664; Master Data Distribution &#61664; Replication of Modified Data &#61664; Activate Change Pointers for Message Types
    Activate change pointer for message type HRMD_ABA
    9. CRM : Number Assignments. Generally, there are 3 types of number assignments (also called switches) when business partners are created.
    1 – The system uses the number from the general internal interval of the number
          range object BU_PARTNER
    2 – The system uses the number from a specific internal interval of the object
    3 – The number is transferred from HR and a prefix is added. In this case, a specific external interval, which must be defined as XX00000000 (upto
    XX99999999), is used (where XX denotes any two letters).
    The number range object for all switch positions is BU_PARTNER, with the interval depending on the switch value.
    For switch value 1, the system uses the internal standard interval, otherwise for switch values 2 and 3 you must also create a grouping (transaction BUC2) for these intervals. For the system to be able to connect the grouping and the number range interval, the name of the grouping must be exactly the same as the name of the corresponding number range interval (the name of the grouping is contained in the first column of the table). If you select 3 (HRALX/PNUMB = 3) for the number assignment of busienss partners of the employee role, create HRALX/PSUBG switch manually in table T77S0.
    In table T77S0, HRALX/ONUMB is used to set the number assignment for organizational units and HRALX/PNUMB is used to set the number assignment for employees.
    Create a number range ZZ
    Transaction code BUC2. Create a grouping of the same ID as that of the number range. Eg. Number range ID : ZZ and grouping ID should also be ZZ
    In table T77S0, maintain the following combinations
    HRALX-PNUMB = 2
    HRALX-PSUBG = ZZ
    10. Make the following customizing changes in CRM
    Transaction code SM30 : Table T77S0
    Group     Sem Abbr     Value Abbr     
    HRALX     HRAC     X     Activate HR Integration with CRM
    HRALX     OBPON     ON     Activate integration between Business partners and Org Units
    HRALX     PBPON     ON     Integration between business partners and employees
    HRALX     OPROL     BUP004     Role definition for org unit – Business partner
    HRALX     PPROL     BUP003     Role definition for Employee – Business partner
    HRALX     ONUMB     1     Number range assignment for org units
    HRALX     PNUMB     2     Number range assignment for Employees
    HRALX     PSUBG     ZZ     Number range grouping only if PNUMB is not 1.
    11. Create Employee Master in R/3.  Employee master consists of Infotypes. The mandatory infotypes are Actions, Address, Personal data and Organizational Assignment.
    Transaction code : PA30
    12. In R/3 Initial Download : SE38 – RHALEINI
    Plan version : 01
    Object type : P – Person (always)
    Object ID : Employee ID eg. 1
    Receiver Partner no. : YYY
    Select further details
    You get all the data transfer details
    13. In CRM, transaction code PP01 – View HR Master objects
    You see that the employee 1 has got transferred. To see the corresponding business partner go to the infotype Relationships (the first row)
    Screen 2 gives you the business partner ID in CRM
    14. Now change the employee master in R/3.  Execute program RBDMIDOC in R/3 to send the changes over to CRM
    Put message type ‘HRMD_ABA’ and Execute
    15. All subsequent changes in R/3, i.e changing an existing Master or creating a new one goes through directly by program RBDMIDOC.
    16. After all employees are transferred to CRM from R/3 only then its safe to execute initial download CUSTOMER_REL
    If an Employee responsible 2 is replaced by 3 in the customer master in R/3, then in CRM, the same is not replaced. Only difference that the sales area assignment is no longer there for the replaced employee in transaction BP relationships.
    Hope this would help.
    Regards,
    Rekha Dadwal
    <b>You gain a point for every point that you reward. So reward helpful answers generously</b>

Maybe you are looking for