SALESFORCE - SOA INTEGRATION

Hi ,
I am currently working on SALESFORCE - SOA Integration.
Followed the link +
http://www.oracle.com/ocom/groups/public/@ocom/documents/webcontent/337439.pdf
Can any one tell me the way to simply create an Account in SALESFORCE through BPEL PROCESS.
Thanks
Surya

Hello,
Users connecting to salesforce using weblogic will have to do one of the
following:
1. Disable Host Name Checking.
2. Upgrade to Weblogic 10.3.6+ and use the "Wildcarded Host Name Verifier"
http://docs.oracle.com/cd/E23943_01/web.1111/e13707/ssl.htm#CHDIEIEE
3. Configure a custom host name verifier:
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/security/ConfigureACustomHostNameVerifier.html
Hope this helps.
cheers,
Praveen

Similar Messages

  • SalesForce XI Integration...

    Hi,
       We are trying SalesForce-XI Integration using WSDLs. We are facing the following issues:
      a. The SalesForce SOAP Calls require a session id string to be passed as part of the SOAP header. This soap header is not visible as part of the message type(only the soap body is seen). How do we pass data as part of SOAP headers using XI?
      b. The Target URL for the SOAP calls is dynamic, while in XI, in the SOAP communication channels, this is Hardcoded. Can this be parameterised in anyway?
      Any help regarding these is welcome.
    Thanks,
    Harsh
    PS: Anyone who's worked on SalesForce XI Integration before?

    Harsh,
    Take a look at this document,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
    Part 4 ADVANCED FEATURES :
    <i>4.1 SOAP Header Fields
    The SOAP adapter creates the SOAP envelope. You cannot influence this procedure. If
    you need to apply special tags inside the SOAP header, the only option is to create the
    whole SOAP envelope during mapping, and in the case of a synchronous call, to remove
    the SOAP envelope in the mapping.
    In the SOAP adapter channel, select Do Not Use SOAP Envelope.
    By using this parameter, you can use the SOAP adapter to send or receive non-
    SOAP messages. In this case the sender SOAP adapter requires an additional
    parameter nosoap=true in the URL. For example:
    http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
    channel=<party>:<service>:<channel>&nosoap=true</i>
    Should address a few issues..hopefully
    Regards,
    Bhavesh

  • OIM-SOA integration

    Hi all,
    please provide me the document to know how the integration of OIM and SOA is done.
    thank you.

    OIM-SOA integration ????
    SOA is a required component before you install OIM 11g. Are you looking for how to install SOA before OIM install ?
    Thanks
    GK

  • Oracle salesforce Adapter integration in SOA 11.7

    I have implemented a scenario given in Chapter-5 of this pdf
    http://www.oracle.com/technetwork/middleware/adapters/documentation/ug-sfdcadapter-ps6-2104970.pdf
    I am facing an issue while invoking Salesforce Adapter. My composite has a bpel process which invokes sales force adapter.
    I have configured the adapter by following the pdf. I am trying to create an Account.
    <bindingFault>
    <part  name="summary">
    <summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'create' failed due to: Error sending bytes: Unknown exception while transforming request message. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
    </part>
    <part  name="detail">
    <detail>Unknown exception while transforming request message.</detail>
    </part>
    <part  name="code">
    <code>null</code>
    </part>
    </bindingFault>

    Hello,
    Users connecting to salesforce using weblogic will have to do one of the
    following:
    1. Disable Host Name Checking.
    2. Upgrade to Weblogic 10.3.6+ and use the "Wildcarded Host Name Verifier"
    http://docs.oracle.com/cd/E23943_01/web.1111/e13707/ssl.htm#CHDIEIEE
    3. Configure a custom host name verifier:
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/security/ConfigureACustomHostNameVerifier.html
    Hope this helps.
    cheers,
    Praveen

  • Oracle SOA Integration with Siebel 8.0 Call Center Application

    Hi Experts,
    I am trying to Integrate Oracle Fusion SOA and Siebel 8.0 and I have been following http://download.oracle.com/docs/cd/E17904_01/doc.1111/e17056/bpel_pm.htm as a reference.
    Here is what I have done so far:
    Created an Inbound Web service (Account Web Service) by login into Siebel Call Center Application. I was able to generate the WSDL file successfully. This WSDL has following operations :
    (a) AccountInsert
    (b) AccountQueryByExample
    (c) AccountQueryById
    If I understand it correctly, this is like any other wsdl file which can be consumed and operations can be invokved by consumers (web service clients)
    I have couple of doubts/questions :
    (1) Once WSDL is generated by the Siebel Client, it can be used in my BPEL process/composite apps to perform the integration. If this statement is true, why and where do we need Siebel Adapter?
    (2) While I was following the online tutorial @ http://download.oracle.com/docs/cd/E17904_01/doc.1111/e17056/bpel_pm.htm , I can see, WSDL was generated by using the Application Explorer (a swing based tool provided by Oracle as a part of Adapter framework). But I have used Siebel Call Center to generate the WSDL file. Which is the standard way of generating the WSDL file?
    (3) In the tutorial mentioned above, I can see request and response xsd files (i.e queryWithView_invoke_request.xsd queryWithView_invoke_response.xsd) . No where in the tutorial has mentioned, how these files were created. Are these hand written files by the developer, or it is something that can be created out of the wsdl itself?
    (4) Also, there is a .jca file (queryWithView_invoke.jca) which is also being used while configuring the Third Party Adapter. Where does queryWithView_invoke.jca come from? Is it something that is created from Application Explorer?
    Would really appreciate if someone can throw lights on these gray areas....
    Waiting for an eagerly reply...
    Thanks in Advance !
    Jameel

    Hi,
    If you are talking about configuring the outbound WS , then you need to go to Siebel > Administration-Webservices> Outbound Webservices
    Query for webservices there and give the <HOST>:<SOA PORT> in the URL.

  • SOA integration repository in R12.1

    I am gettting the error
    Warning
    SOA Provider Access is not available. You may not be able to see complete information about the service. Please contact your System Administrator
    When I am trying to access the SOA repository from Oracle !2.1. I have added the Integrated SOA Gateway responsibility for myself.
    All inputs are welcome.

    Hi Deepak,
    I am facing the same issue. I am new to EBS. I ahve the access to SYSADMIN user. I am seeing this error in this account itself, so what do i need to do to fix this issue?
    Please reply me if you got any solution for this? Also i am looking for an example to interact with any SOA Gateway web service. I want to know how the authentication is done, and what are the settings to be done in the ESB to authenticate a service. I did the all the steps as per documents, but still not able to get success. So i am looking a complete example where I can do the same steps and check it fro my side.
    --Khaleel                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • ADF-SOA integration getting class cast exception when creating a BPEL task

    Hi,
    We are creating a BPEL task programmatically using below code snippet
    IInitiateTaskResponse tResponse = iTask.initiateTask(task);
    when initiateTask() is called i keep getting below exception.
    oracle.bpel.services.workflow.task.ejb.TaskServiceBean_399vcw_HomeImpl_1036_WLStub cannot be cast to oracle.bpel.services.workflow.task.ejb.TaskServiceRemoteHome.
    Sometime restarting the servers(soa and wls) solves the issue but most of the time i get above exception. I have a integrated WLS server and a remote SOA server. i have done necessary JNDI configuration in my integrated server and global trust is created betwen both the servers.
    Any pointers will help us in our development which is stuck because of this issue.

    Mozakkir,
    My name is Phil DeLaine and I work for one of Oracle's Gold Partners, TechDemocracy.
    I saw your post about the SOA/BPEL integration issue.
    Given the potential complexity of your situation, would it make sense to use one of our SOA experts to solve the problem and deliver your project?
    Please let me know how we can help. You can reach out to me anytime.
    Regards,
    Phil
    Phil DeLaine
    Sales Director
    TechDemocracy
    (978) 758-3156 (Cell)
    [email protected]
    http://www.techdemocracy.com/
    Our Successes:
    1) We won the 2011 Oracle Titan Award for the Best Middleware Implementation. Our award winning solutions included SOA, IAM and BI.
    2) We have been awarded with the highly prestigious Oracle ACE Director status for outstanding industry achievement and track record.
    3) We sit on several Advisory Boards for Oracle Product Management (for Fusion Middleware Products).
    4) We are an Oracle Center of Excellence Partner for SOA and IAM.
    5) We are frequently invited to speak at a number of Oracle Customer Success forums such as Oracle's "OpenWorld".
    6) We have been rated by Inc. Magazine as one of the top 10 fastest growing companies for 3 consecutive years.
    7) We have won and successfully deliveried several projects at Fortune 100, 500 and 1,000 companies. (References Available)

  • Error Occured While Creating Grant From SOA Integration Repository

    Hi All,
    I have created the Custom SOA Object using the Iparser.
    Now i am trying to provide the grant through the SOA repository.
    When I click create,the its failing
    I am getting the following error when I click a CREATE GRANT button for a web service that has been deployed.
    Exception Details.
    oracle.apps.fnd.framework.OAException: oracle.jbo.NoDefException: JBO-25058: Definition isOverloaded of type Attribute not found in AdminMethodsVO
         at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1247)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(OAPageBean.java:3136)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(OAPageBean.java:2931)
         at OA.jspService(_OA.java:228)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
         at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
         at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
         at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395)
         at OA.jspService(_OA.java:221)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
         at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:619)
    ## Detail 0 ##
    oracle.apps.fnd.framework.OAException: oracle.jbo.NoDefException: JBO-25058: Definition isOverloaded of type Attribute not found in AdminMethodsVO
         at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:896)
         at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1169)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(OAPageBean.java:3136)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(OAPageBean.java:2931)
         at OA.jspService(_OA.java:228)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
         at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
         at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
         at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395)
         at OA.jspService(_OA.java:221)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
         at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:619)
    oracle.apps.fnd.framework.OAException: oracle.jbo.NoDefException: JBO-25058: Definition isOverloaded of type Attribute not found in AdminMethodsVO
         at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:896)
         at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1169)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(OAPageBean.java:3136)
         at oracle.apps.fnd.framework.webui.OAPageBean.renderDocument(OAPageBean.java:2931)
         at OA.jspService(_OA.java:228)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
         at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
         at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
         at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395)
         at OA.jspService(_OA.java:221)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
         at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:619)

    Yeah abd BTW you might get another error once the WSDL is deployed.
    The error is
    Property setIRepOverloadSeq is not defined for oracle.tip.adapter.apps.AppsStoredProcedureInteractionSpec
    Please verify the spelling of the property. Please verify the spelling of the property.
    ; nested exception is: ; Nested exception is:
    ORABPEL-12532 ORABPEL-12532
    Error while setting JCA WSDL Property. Error while setting JCA WSDL Property.
    The soulution
    You can see the WSDL file Web service method / d02/inst/apps/VIS02_ebs006/soa/PLSQL/4690/ANYWSDLYOUAREUSING.wsdl a problem, view the contents of this file
    <Jca: operation
    PackageName=”ORACLESEEKER_DEPT_PKG” PackageName = "ORACLESEEKER_DEPT_PKG"
    ProcedureName=”ADD_DEPARTMENT” ProcedureName = "ADD_DEPARTMENT"
    IRepInternalName=”PLSQL:ORACLESEEKER_DEPT_PKG:ADD_DEPARTMENT” IRepInternalName = "PLSQL: ORACLESEEKER_DEPT_PKG: ADD_DEPARTMENT"
    IRepOverloadSeq=”1″ IRepOverloadSeq = "1"
    InteractionSpec=”oracle.tip.adapter.apps.AppsStoredProcedureInteractionSpec” > InteractionSpec = "oracle.tip.adapter.apps.AppsStoredProcedureInteractionSpec">
    </jca:operation>
    This tag contains an attribute IRepOverloadSeq, see the above error should be in Java, Oracle does not implement handling of this property seems to be a bug, since the procedure does not deal with it, that any case to back up this file, and then remove the tag to fix it.
    Thanks

  • Coherence, OSB and SOA integration

    Hi,
    I have a WL domain, that consists on a SOA cluster and a OSB cluster. I want to have external cache servers, as it is the preferred option provided by Oracle, so I have external processes which starts a cache, loads data from database, and create a Coherence cluster.
    I have tried different options for deployment and havinfg issues with all of them.
    In my domain (FMW 11.1.1.6), I have not deployed the coherence libs, as they are included in the server modules. I start the external process, which points to the coherence lib in FMW_MODULES, and load everything. So far so good. When I start the managed servers for OSB cluster and SOA clusters I get a lot of errors, like:
    java.lang.IllegalArgumentException: No scheme for cache: "/soa-infra/deployment/members/mydomain_development_soa_cluster"
    I don't know if I should create different coherence clusters, one for my apps, and one for built in OSB+SOA functionality, or I could use the same. If I use the same, where should I put cache configurations, and where can I see built in cache definitions.
    If I should create a new cluster for my functionality, how could I do it, knowing that I will not be bundling only J2EE apps, but also global libraries, and security providers using these coherence infrastructure.
    Do I need activecache for anything?
    Documentation is not very clear.
    Thanks for your support.

    jorgemoralespou wrote:
    Hi,
    I have a WL domain, that consists on a SOA cluster and a OSB cluster. I want to have external cache servers, as it is the preferred option provided by Oracle, so I have external processes which starts a cache, loads data from database, and create a Coherence cluster.
    I have tried different options for deployment and havinfg issues with all of them.
    In my domain (FMW 11.1.1.6), I have not deployed the coherence libs, as they are included in the server modules. I start the external process, which points to the coherence lib in FMW_MODULES, and load everything. So far so good. When I start the managed servers for OSB cluster and SOA clusters I get a lot of errors, like:
    java.lang.IllegalArgumentException: No scheme for cache: "/soa-infra/deployment/members/mydomain_development_soa_cluster"
    I don't know if I should create different coherence clusters, one for my apps, and one for built in OSB+SOA functionality, or I could use the same. If I use the same, where should I put cache configurations, and where can I see built in cache definitions.
    If I should create a new cluster for my functionality, how could I do it, knowing that I will not be bundling only J2EE apps, but also global libraries, and security providers using these coherence infrastructure.
    Do I need activecache for anything?
    Documentation is not very clear.
    Thanks for your support.Hi,
    Oracle SOA Suite 11g leverages an embedded Coherence cache to coordinate several cluster-wide activities including composite deployment. Coherence cache-config is pre-defined for SOA Cluster, and all SOA composite application will inherit this. This cache-config is zipped in fabric-runtime.jar with the name of soa-coherence-cache-config.xml and tangosol-coherence-override.xml is also included in fabric-runtime.jar that enforces SOA server to use soa-coherence-cache-config.xml. Now you have 2 options to make it work,
    1) Make managed servers join the external Coherence cluster as storage-disabled nodes: In order to accomplish it, you need to ensure that the configuration (soa-coherence-cache-config.xml and tangosol-coherence-override.xml) used by cache servers are same as used by SOA Suite(except, storage flag). Also, note that you need to merge your cache server configuration into soa-coherence-cache-config.xml because SOA Suite requires all the caches that are predefined in soa-coherence-cache-config.xml and reference this merged configuration file in you cache server and also in SOA cluster by modifying tangosol-coherence-override.xml
    2) Managed Servers access the Coherence cluster as extend clients: In order to accomplish it, modify soa-coherence-cache-config.xml and add remote-scheme to access the external Coherence cluster. You need to ensure that you provide a tangosol-coherence-override.xml to your cache servers so that they form a seperate cluster and not try joining the SOA Suite cluster.
    You are getting the error:
    java.lang.IllegalArgumentException: No scheme for cache: "/soa-infra/deployment/members/mydomain_development_soa_cluster"Your coherence cluster is using the same multicast ip/port for this cluster as used by the SOA Coherence cluster on startup but a different configuration file is used by your Coherence cluster than soa-coherence-cache-config.xml.
    Try following option1 and it should help solve your problem.
    Please note, modifying fabric-runtime.jar is not recommended by Product Management and is just a work around. Also, I would suggest you to understand licensing from Oracle Sales Rep.
    Hope this helps!
    Cheers,
    NJ
    Edited by: user738616 on Feb 27, 2012 11:02 AM

  • PSFT - SOA Integration

    How to create a JMS Connection Factory in PSFT and deploy it so that we can use same JMS queue to write inbound messages from BPEL Process?
    We want to use different JMS Queues from sending and recieving JMS messages?
    We have below solutions identified in this context:
    Solution 1 - Reading the JMS Queues generated from the PSFT IB through a JMS Adapter and process it through Async One way flow and pass it to the 3rd Party Application & vice versa.
    Solution 2 - Using AIA to create the framework for the inbound and outbound process flows.
    Can you suggest which is better for scalability & reusability?
    Cheers,
    Sid

    Yes There are certain chnages in R12.
    In R12 SOA has to communicate with EBS through Internet SOA Gateway.Business event, Concurrent prog etc are exposed from EBS as thorugh internet soa gateway

  • OBIEE SOA Integration Bridge session

    Hi,
    I am trying to show OBIEE reports in .NET using OBIEE Web Services. So far I am able to successfully display and perform drill down and export operations on the report without using Bridge.
    I have written my HTTPModule/HTTPHandler to process the OBIEE requests. I am able to successfully show the report but all of it is not loading properly and I am UNABLE to do any drill down or export to pdf etc.
    During one of the AJAX requests made from the browser, the response I get back is the IFrame with log in page I am not sure why this is happening.
    For example: GET request to http://localhost/Bridge?RedirectURL=saw.dll%2fuicomponents/common/common.xml?fmapId=KqIJCw always return me with login page
    Same is true for http://localhost/Bridge?RedirectURL=saw.dll%3fgetReportXmlFromSearchID
    I have checked the headers, parameters, cookies, etc. All is as it is suppose to be. I think request from the browser is missing something or something in my Bridge is not set correct.
    I am initializing code as:
    var htmlViewService = new HtmlViewServiceSoapClient();
    //Get sessionId
    var sessionId = sawSessionServiceSoapClient.logon("prodney", "Admin123");
    //Set bridge
    htmlViewService.setBridge("http://localhost/Bridge", sessionId);
    //Get pageId
    var pageId = htmlViewService.startPage(new StartPageParams() { dontUseHttpCookies = true }, sessionId);
    //Create report object
    var newreportRef = new ReportRef
    reportPath = reportPath,
    reportXml = reportXml
    Here is the code for my bridge:
    private void Application_BeginRequest(object sender, EventArgs e)
    var app = (HttpApplication)sender;
    HttpRequest request = app.Context.Request;
    var response = app.Response;
    var context = app.Context;
    if (!String.IsNullOrEmpty(request.Params["RedirectURL"]))
    response.Clear();
    response.ClearHeaders();
    response.ClearContent();
    var headers = context.Request.Headers;
    string requestUri = ObieeServerUrl + context.Request.Params["RedirectURL"];
    var httpWebRequest = (HttpWebRequest)WebRequest.Create(requestUri);
    string modifiedSince = headers.Get("If-Modified-Since");
    httpWebRequest.Method = context.Request.HttpMethod;
    httpWebRequest.Accept = headers.Get("Accept");
    httpWebRequest.Expect = headers.Get("Expect");
    httpWebRequest.ContentType = headers.Get("Content-Type");
    httpWebRequest.Referer = headers.Get("Referer");
    httpWebRequest.UserAgent = headers.Get("User-Agent");
    httpWebRequest.CookieContainer = new CookieContainer();
    if (!string.IsNullOrEmpty(modifiedSince))
    httpWebRequest.IfModifiedSince = DateTime.Parse(modifiedSince);
    if (!httpWebRequest.Method.Equals("GET"))
    CopyStreams(context.Request.InputStream, httpWebRequest.GetRequestStream());
    HttpWebResponse httpWebResponse = null;
    try
    httpWebResponse = (HttpWebResponse)httpWebRequest.GetResponse();
    catch (WebException ex)
    httpWebResponse = (HttpWebResponse)ex.Response;
    for (int i = 0; i < httpWebResponse.Cookies.Count; i++)
    Cookie c = httpWebResponse.Cookies;
    var httpCookie = new HttpCookie(c.Name, c.Value)
    Path = c.Path,
    Domain = ObieeServerUrl
    context.Response.Cookies.Add(httpCookie);
    context.Response.StatusCode = (int)httpWebResponse.StatusCode;
    context.Response.ContentType = httpWebResponse.ContentType;
    CopyStreams(httpWebResponse.GetResponseStream(), context.Response.OutputStream);
    response.End();
    return;
    private void CopyStreams(Stream inputStream, Stream outputStream)
    var buf = new byte[4096];
    try
    do
    int iRead = inputStream.Read(buf, 0, 4096);
    if (iRead == 0)
    break;
    var enc = new System.Text.UTF8Encoding();
    var dataString = enc.GetString(buf);
    outputStream.Write(buf, 0, iRead);
    while (true);
    finally
    outputStream.Close();
    Thanks
    Edited by: user1055840 on Nov 23, 2011 12:50 PM
    Edited by: user1055840 on Nov 23, 2011 12:52 PM

    May be a little bit late. But it's best later than never.
    It seems that OBIEE doesn't use cookie for the authentication.
    Most of the URL contain an _scid parameter (session id) to be able to authenticate.
    If you don't have it, you are redirected to the login page.
    Cheers
    Nico
    I forgot to say that i didn't work enough with the Web Service to do a bridge implementation.
    Edited by: gerardnico on Sep 10, 2012 2:50 PM - I forgot to say that i didn't work enough with the Web Service to do a bridge implementation.

  • SOA Integration between FS-Account Management and Bank Analyzer under BS 8.0

    Hello all, we have set up the soamanager i.o. to integrate account manager and FS-business partner with the Bank Analyzer under Release 8.0 For the business partner this works fine. For master data of the current accounts we encounter the following problem:
    We have configured the soamanager  on the consumer side installing the consumer: BankAccountContractProcessingCurrentAccountContractEventOut On this side we would like to use message type: CurrentAccountContractFSCreatedBulkInformation_V3.
    However the consumer (account management) provides CurrentAccountContractFSCreatedBulkInformation_V2 only, which is the xml-formate for Release BS 7.0.
    Can anybody tell me, how to configure AM (consumer side), such that it provides the correct xml-formate for Release 8.0. For more information please refer to the document:  IOA_technical_configuration_19. For further info on soamanager-config refer to the appendix.
    Thanks, Sebastian Sachse

    hi Sebastian
    please refer to Katja Bornschein ([email protected]) as the owner ot the IOA-Scenarios. She will give you the information needed. As far as I know '_V3' is used only in FSAPPL500 (Release 9.0, GA in November 2014)
    BR, Ernst

  • Salesforce CRM and SAP Integration

    Hello Experts,
    I am supposed to come up with salesforce integration with SAP. Can you please let me know how do I start? What is that I can pick up from SAP to integrate this with salesforce and what are the hardware details required?
    If somebody has worked on this please do let me know.
    Thank you in advance,
    Cheers,
    Deepak

    salesforce integration with SAP
    salesforce->XI->SAP
    1) send salesforce data through webservice to SAP XI. it will be done by using SOAP adapter.
    2) XI will send data to SAP by idoc/rfc/proxy,depending on scenario.
    this thread ll bring clarity on the same :
    Salesforce.com integration with XI

  • Integrating SOA and Peoplesoft: Configuring JMSTARGET Connector in IB.

    Hi All,
    I have created JMS queue/topic in oracle application server. Can anybody idea how can we configure JMS connector of peoplesoft integration broker.
    Let me first explain my requirement, I am working in peoplesoft outbound interface design with SOA integration.
    So my approach will be creating JMS queue in oracle application Server and then configuring this JMS to any node of peoplesoft IB.
    Then extracted information from peoplesoft need to send to the above node so that once the node receive the message it should
    populate the JMS queue inturn SOA BPEL will be triggered to write into third party file/database.
    Please give your inputs on this approach if you any other suggetion for peoples soft outbound integration with SOA.
    Thanks inadvance.

    Its published, but somehow you are unable to see it..issues with Meatlink for sure..
    Here is its content :
    Applies to:
    PeopleSoft Enterprise PT PeopleTools - Version: 8.4 - Release: 8.4
    Information in this document applies to any platform.
    This document was previously published as Customer Connection Solution 201077819
    Symptoms
    Please see below.
    Cause
    Not Applicable
    Solution
    <<Document:664816.1>> E-IB: Configuring Integration Broker with IBM MQ on AIX
    SPECIFIC TO: Enterprise, PeopleTools, Integration Broker Release 8.49
    ISSUE:
    How to setup Integration Broker to PUT messages to an IBM MQ Server on a remote machine?
    SOLUTION:
    <See attachment for documentation with screenshot examples.>
    Configuring Integration Broker with IBM MQ on AIX
    The following guide is intended to outline the setup between Peoplesoft Integration Broker and IBMs Websphere MQ version 6 client on AIX. Note: This is not a certification, but a working example, specifically using the MQ client to connect to a remote machine running the MQ server.
    Platform Information:
    PeopleSoft PeopleTools 8.49
    IBM Websphere MQ Release 6
    AIX
    Steps
    1) Install and IBM Websphere MQ (WMQ) client
    2) Configure WMQ connection
    3) Configure Peoplesoft
    4) TEST using PING and a Peoplesoft message to PUT data onto the WMQ server
    Steps
    1) Install and configure Websphere MQ client on AIX where Peoplesoft is located
    NOTE: This is one optional architecture. It is also possible to install Peoplesoft and MQ on the same server, which avoids the client software altogether.
    a. IBM deliveres an MQ client that is installed on the same box as the Peoplesoft with the following options.
    i. Installed to /usr/mqm, all objects owned by local user mqm
    ii. Ensure that the MQ Extended Transactional Client is installed
    1. This includes com.ibm.mqetclient.jar file
    iii. Mq specific environment variables
    1. $MQ_JAVA_DATA_PATH=/usr/mqm
    2. $MQ_JAVA_INSTALL_PATH=/usr/mqm/java
    3. $MQ_JAVA_LIB_PATH=/usr/mqm/java/lib
    4. jms.jar, fscontext.jar, jndi.jar, providerutil.jar, stcjms.jar
    iv. CLASSPATH
    1. Includes the following MQ jar files
    i. com.ibm.mqetclient.jar
    ii. providerutil.jar
    iii. com.ibm.mqjms.jar
    iv. ldap.jar
    v. jta.jar
    vi. jndi.jar
    vii. jms.jar
    viii. connector.jar
    ix. com.ibm.mq.jar
    2. Example
    a. > echo $CLASSPATH
    i. echo $CLASSPATH /usr/mqm/java/lib/com.ibm.mqetclient.jar:/usr/mqm/java/lib/providerutil.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/ldap.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/fscontext.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib:/usr/mqm/java/bin
    3. When setting up Peoplesoft, add these jar files to the classpath setting in the setenv.sh file and reboot PIA
    2) Configure WMQ
    a. Edit JMSAdmin.config (located in /usr/mqm/java/bin)
    ii. Set Initial Context Factory = com.sun.jndi.fscontext.RefFSContextFactory
    # The following line specifies which JNDI service provider is in use.
    # It currently indicates an LDAP service provider. If a different
    # service provider is used, this line should be commented out and the
    # appropriate one should be uncommented.
    #INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    #INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
    iii. Set PROVIDER_URL=file:/usr/mqm/java
    # The following line specifies the URL of the service provider's initial context. It currently refers to an LDAP root context. Examples of a file system URL and WebSphere's JNDI namespace are also shown, commented out.
    #PROVIDER_URL=ldap://polaris/o=ibm,c=us
    PROVIDER_URL=file:/usr/mqm/java
    #PROVIDER_URL=iiop://localhost/
    b. Run JMSAdmin to setup queue and qcf to the MQ server
    i. def qcf(PLAS160_QCF) HOSTNAME(GSPLVP006-VM2) PORT(1414) CHANNEL(SYSTEM.DEF.SVRCONN) QMANAGER(QM_gsplvp006_vm2) TRANSPORT(CLIENT)
    ii. NOTE: When connecting from a client to a remote server, it is important to specify the hostname, port and transport along with the other values.
    iii. def q(PLAS160_Q) queue(PLAS160_Q)
    1. Note: The q is a local naming alias, whereas the queue is the physical queue name on the MQ server
    iv. Screenshot:
    v. This creates a .bindings file
    vi. NOTE: It is also possible to use IVTSetup for this, but JMSAdmin is recommended.
    vii. NOTE: It is possible to gain a .bindings file from your MQ server administrator. Be sure that this format is correct, and the location on the client is referenced correctly.
    viii. JMSAdmin can also be used to determin what connections are available from this machine using command dis ctx as shown
    b. Optional: Test the connection to the MQ server using IBM software.
    NOTE: Testing the ivtQ and ivt QCF can be accomplished using the IVTRun program, provided that the ivtQ and ivtQCF have been setup in the .bindings file with the same available on the MQ server (some mq administrators do not enable this by default)
    i. Example IVTRun, see Appendix 1
    ii. Example .bindings file see Appendix 2
    3) Configure PeopleSoft
    a. Create an external NODE representing the target JMS queue
    i. Example node, see appendix 3
    b. Setup the connectors properties for the new node
    i. Use the connector ID= JMSTARGET
    ii. Example properties screenshot, see Appendix 4
    1. Notes
    a. JMSProvider is MQSeries
    b. JMSFactory, JMSQueue are those specified in the .bindings file representing that on the JMS server. In this case, PLAS160_QCF and PLAS160_Q are used for this example.
    c. JMSUrl is the location of the working .bindings file on the web server (in this case file:/D:/apps/IBM/WebSphereMQ/Java )
    c. Setup Gateway Properties
    i. Access the Gateway Properties using PIA and add the JMS information for MQSeries to the integrationgateway.properties file as shown:
    ## JMS configuration Section
    # <the following line is required>
    ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
    ii. Queue information here is only needed if going to GET message using the JMSListeningConnector. Not needed for the target PUT (or ping)
    iii. Example integrationgateway.properties, See appendix 5
    4) Test PUT connection from Peoplesoft to WMQ
    1. Ping the JMS node from the node definition
    b. Setup routings to PUT messages to the MQ node
    i. Example using USER_PROFILE
    ii. Submit the message and check the Operations Monitor
    iii. Verify that the message made it to MQ (this is viewed by browsing the queue on the Websphere MQ Explorer, message browser. A better utility is rfhutil which is included in the MQ windows client development kit)
    NOTE: This document is intended for 1 way communication TO Mq from Peoplesoft. Setup for GET using the JMSListeningConnector is a separate topic for documentation.
    Appendix 1 IVTRun
    Appendix 2 .bindings file.
    NOTE: The PLAS160_QCF and PLAS160_Q references are applicable to this example.
    #This file is used by the JNDI FSContext.
    #Wed Sep 17 11:43:13 PDT 2008
    PLAS160_QCF/RefAddr/9/Type=SRC
    PLAS160_Q/RefAddr/5/Encoding=String
    PLAS160_QCF/RefAddr/13/Content=5000
    PLAS160_QCF/RefAddr/3/Content=GSPLVP006-VM2
    PLAS160_Q/RefAddr/8/Content=PLAS160_Q
    PLAS160_QCF/RefAddr/13/Type=PINT
    PLAS160_QCF/RefAddr/1/Type=TRAN
    MYPUT/RefAddr/2/Content=-2
    PLAS160_QCF/RefAddr/6/Encoding=String
    PLAS160_QCF/RefAddr/17/Type=RINT
    PLAS160_QCF/RefAddr/5/Type=CHAN
    PLAS160_QCF/RefAddr/18/Encoding=String
    PLAS160_Q/RefAddr/2/Content=-2
    PLAS160_PUT/RefAddr/1/Encoding=String
    PLAS160_QCF/RefAddr/20/Content=SYSTEM.DEFAULT.MODEL.QUEUE
    PLAS160_PUT/RefAddr/3/Type=PER
    MYPUT/RefAddr/6/Encoding=String
    PLAS160_Q/RefAddr/5/Content=0
    PLAS160_PUT/RefAddr/8/Content=PLAS160_PUT
    PLAS160_Q/RefAddr/6/Encoding=String
    MYPUT/RefAddr/0/Type=VER
    PLAS160_PUT/RefAddr/7/Type=FIQ
    PLAS160_QCF/RefAddr/7/Encoding=String
    MYPUT/RefAddr/4/Type=CCS
    PLAS160_PUT/RefAddr/2/Content=-2
    PLAS160_QCF/RefAddr/19/Encoding=String
    PLAS160_PUT/RefAddr/5/Content=0
    PLAS160_PUT/RefAddr/2/Encoding=String
    PLAS160_Q/RefAddr/3/Type=PER
    MYPUT/RefAddr/8/Type=QU
    MYPUT/RefAddr/7/Encoding=String
    PLAS160_Q/RefAddr/7/Encoding=String
    MYPUT/ClassName=com.ibm.mq.jms.MQQueue
    PLAS160_Q/RefAddr/7/Type=FIQ
    PLAS160_QCF/RefAddr/8/Encoding=String
    PLAS160_QCF/RefAddr/6/Type=CCS
    MYPUT/RefAddr/9/Content=
    PLAS160_QCF/RefAddr/10/Type=SFIPS
    PLAS160_QCF/RefAddr/10/Encoding=String
    PLAS160_PUT/RefAddr/3/Encoding=String
    PLAS160_QCF/RefAddr/20/Type=TM
    MYPUT/RefAddr/8/Encoding=String
    PLAS160_Q/RefAddr/8/Encoding=String
    PLAS160_QCF/RefAddr/14/Type=MBS
    PLAS160_QCF/RefAddr/17/Content=5000
    PLAS160_QCF/RefAddr/2/Type=QMGR
    PLAS160_PUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
    PLAS160_QCF/RefAddr/7/Content=\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
    MYPUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
    MYPUT/RefAddr/3/Content=-2
    PLAS160_PUT/RefAddr/0/Type=VER
    MYPUT/RefAddr/6/Content=273
    PLAS160_QCF/RefAddr/18/Type=TCM
    PLAS160_QCF/RefAddr/9/Encoding=String
    PLAS160_QCF/RefAddr/11/Content=false
    PLAS160_QCF/RefAddr/1/Content=1
    PLAS160_Q/RefAddr/6/Content=273
    PLAS160_QCF/RefAddr/11/Encoding=String
    PLAS160_QCF/RefAddr/20/Encoding=String
    PLAS160_PUT/RefAddr/4/Type=CCS
    PLAS160_PUT/RefAddr/4/Encoding=String
    PLAS160_QCF/RefAddr/14/Content=10
    PLAS160_QCF/RefAddr/4/Content=1414
    PLAS160_Q/RefAddr/9/Content=
    MYPUT/RefAddr/9/Encoding=String
    MYPUT/RefAddr/0/Content=6
    MYPUT/RefAddr/1/Type=EXP
    PLAS160_Q/RefAddr/9/Encoding=String
    PLAS160_PUT/RefAddr/8/Type=QU
    PLAS160_Q/RefAddr/0/Content=6
    PLAS160_Q/RefAddr/0/Type=VER
    MYPUT/RefAddr/5/Type=TC
    PLAS160_Q/RefAddr/3/Content=-2
    PLAS160_QCF/RefAddr/0/Encoding=String
    PLAS160_PUT/RefAddr/6/Content=273
    PLAS160_QCF/RefAddr/21/Content=
    PLAS160_Q/RefAddr/4/Type=CCS
    MYPUT/RefAddr/9/Type=QMGR
    PLAS160_QCF/RefAddr/21/Encoding=String
    PLAS160_PUT/RefAddr/9/Content=
    PLAS160_QCF/RefAddr/12/Encoding=String
    PLAS160_PUT/RefAddr/5/Encoding=String
    MYPUT/RefAddr/0/Encoding=String
    PLAS160_Q/RefAddr/8/Type=QU
    PLAS160_Q/RefAddr/0/Encoding=String
    PLAS160_PUT/RefAddr/0/Content=6
    PLAS160_Q/FactoryName=com.ibm.mq.jms.MQQueueFactory
    PLAS160_PUT/RefAddr/3/Content=-2
    PLAS160_QCF/RefAddr/7/Type=CT
    PLAS160_QCF/RefAddr/1/Encoding=String
    PLAS160_QCF/RefAddr/11/Type=SPAG
    PLAS160_QCF/RefAddr/21/Type=TQPFX
    PLAS160_QCF/RefAddr/13/Encoding=String
    PLAS160_QCF/RefAddr/22/Encoding=String
    PLAS160_PUT/RefAddr/6/Encoding=String
    PLAS160_QCF/RefAddr/15/Type=FIQ
    PLAS160_QCF/RefAddr/3/Type=HOST
    MYPUT/RefAddr/1/Encoding=String
    PLAS160_PUT/RefAddr/1/Type=EXP
    PLAS160_QCF/RefAddr/19/Type=MNST
    PLAS160_QCF/RefAddr/2/Encoding=String
    PLAS160_PUT/RefAddr/5/Type=TC
    PLAS160_QCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
    PLAS160_QCF/RefAddr/14/Encoding=String
    PLAS160_QCF/RefAddr/18/Content=true
    MYPUT/RefAddr/2/Type=PRI
    PLAS160_QCF/RefAddr/8/Content=0
    MYPUT/RefAddr/4/Content=1208
    MYPUT/RefAddr/2/Encoding=String
    PLAS160_PUT/RefAddr/9/Type=QMGR
    PLAS160_Q/ClassName=com.ibm.mq.jms.MQQueue
    PLAS160_Q/RefAddr/1/Encoding=String
    MYPUT/RefAddr/7/Content=1
    PLAS160_Q/RefAddr/1/Type=EXP
    MYPUT/RefAddr/6/Type=ENC
    PLAS160_QCF/RefAddr/12/Content=true
    PLAS160_QCF/RefAddr/2/Content=QM_gsplvp006_vm2
    PLAS160_Q/RefAddr/7/Content=1
    PLAS160_QCF/RefAddr/3/Encoding=String
    PLAS160_Q/RefAddr/5/Type=TC
    PLAS160_QCF/RefAddr/15/Content=1
    PLAS160_QCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
    MYPUT/RefAddr/1/Content=-2
    PLAS160_PUT/RefAddr/7/Encoding=String
    PLAS160_QCF/RefAddr/15/Encoding=String
    PLAS160_Q/RefAddr/9/Type=QMGR
    MYPUT/RefAddr/3/Encoding=String
    PLAS160_Q/RefAddr/1/Content=-2
    PLAS160_Q/RefAddr/2/Encoding=String
    PLAS160_Q/RefAddr/4/Content=1208
    PLAS160_QCF/RefAddr/8/Type=CTO
    PLAS160_PUT/RefAddr/7/Content=1
    PLAS160_QCF/RefAddr/22/Content=1
    PLAS160_QCF/RefAddr/12/Type=UCP
    PLAS160_QCF/RefAddr/0/Type=VER
    PLAS160_QCF/RefAddr/4/Encoding=String
    PLAS160_QCF/RefAddr/22/Type=MRET
    PLAS160_QCF/RefAddr/16/Type=LA
    PLAS160_PUT/ClassName=com.ibm.mq.jms.MQQueue
    PLAS160_QCF/RefAddr/4/Type=PORT
    PLAS160_PUT/RefAddr/8/Encoding=String
    PLAS160_QCF/RefAddr/16/Encoding=String
    PLAS160_PUT/RefAddr/1/Content=-2
    PLAS160_PUT/RefAddr/4/Content=1208
    PLAS160_Q/RefAddr/3/Encoding=String
    PLAS160_PUT/RefAddr/2/Type=PRI
    PLAS160_PUT/RefAddr/6/Type=ENC
    PLAS160_QCF/RefAddr/5/Encoding=String
    MYPUT/RefAddr/3/Type=PER
    PLAS160_PUT/RefAddr/9/Encoding=String
    PLAS160_QCF/RefAddr/17/Encoding=String
    MYPUT/RefAddr/4/Encoding=String
    PLAS160_Q/RefAddr/2/Type=PRI
    MYPUT/RefAddr/7/Type=FIQ
    PLAS160_Q/RefAddr/4/Encoding=String
    PLAS160_QCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
    PLAS160_QCF/RefAddr/16/Content=
    PLAS160_Q/RefAddr/6/Type=ENC
    PLAS160_QCF/RefAddr/6/Content=819
    PLAS160_QCF/RefAddr/19/Content=true
    PLAS160_QCF/RefAddr/9/Content=0
    MYPUT/RefAddr/5/Content=0
    PLAS160_PUT/RefAddr/0/Encoding=String
    MYPUT/RefAddr/8/Content=PLAS160_PUT
    PLAS160_QCF/RefAddr/10/Content=false
    MYPUT/RefAddr/5/Encoding=String
    PLAS160_QCF/RefAddr/0/Content=6
    Appendix 3 Node definition
    Appendix 4 - Node JMSTarget Connectors Properties
    Appendix 5 integrationgateway.properties JMS configuration section
    ## JMS configuration Section
    #The JNDIFactory Classnames for Weblogic, IPlanet, MQSeries.
    #ig.jms.JMSProvider.JNDIFactory.Weblogic=weblogic.jndi.WLInitialContextFactory
    #ig.jms.JMSProvider.JNDIFactory.IPlanet=com.sun.jndi.fscontext.RefFSContextFactory
    ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
    #ig.jms.JMSProvider.JNDIFactory.OracleApplicationServer=com.evermind.server.rmi.RMIInitialContextFactory
    # Enter the number of Queue listners to instantiate
    #ig.jms.Queues=1
    # For each queue specify the following properties
    # Name
    # Provider
    # JMSFactory name (which is binded to the JNDI)
    # MessageSelector (optional Message Filter)
    # JNDI System File URL
    # JMS User
    # JMS Password
    # Example :
    #ig.jms.Queue1=QUEUE_VAS
    #ig.jms.Queue1.Provider=MQSeries
    #ig.jms.Queue1.JMSFactory=QCF
    # ig.jms.Queue1.MessageSelector=
    #ig.jms.Queue1.Url=file:/D:/apps/IBM/WebSphereMQ/Java
    # ig.jms.Queue1.User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.Password=EncryptedPassword
    # ig.jms.Queue1.SecurityPrincipal=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.SecurityCredentials=EncryptedPassword
    #IBInfoHeaders
    #ig.jms.Queue1.MessageName=QE_F18_ASYNC
    #ig.jms.Queue1.MessageVersion=VERSION_1
    #ig.jms.Queue1.RequestingNode=FromNode
    #ig.jms.Queue1.DestinationNode=ToNode
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    #ig.jms.Queue1.NodePassword=EncryptedRequestingNodePassword
    #ig.jms.Queue1.SubChannel=SubChannel
    # Enter the number of Topic Subscribers to instantiate
    # ig.jms.Topics=1
    # For each Topic specify the following properties
    # Name
    # Provider
    # JMSFactory name (which is binded to the JNDI)
    # MessageSelector (optional Message Filter)
    # JNDI System File Url
    # JMS User
    # JMS Password
    # Example :
    # ig.jms.Topic1=ExampleTopic
    # ig.jms.Topic1.Provider=MQSeries
    # ig.jms.Topic1.JMSFactory=TopicConnectionFactory
    # ig.jms.Topic1.MessageSelector=
    # ig.jms.Topic1.Url=file:c:/
    # ig.jms.Topic1.User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Topic1.Password=EncryptedPassword
    # ig.jms.Queue1.SecurityPrincipal=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.SecurityCredentials=EncryptedPassword
    #IBInfo Headers
    #ig.jms.Topic1.MessageName=QE_F18_ASYNC
    #ig.jms.Topic1.MessageVersion=VERSION_1
    #ig.jms.Topic1.RequestingNode=FromNode
    #ig.jms.Topic1.DestinationNode=ToNode
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    #ig.jms.Topic1.NodePassword=EncryptedRequestingNodePassword
    #ig.jms.Topic1.SubChannel=SubChannel
    #For sending error either ErrorQueue or ErrorTopic must be configured
    #If both exists, errors are only sent to ErrorQueues.
    #Configure the Error-Queue configuration
    # ig.jms.ErrorQueue=ErrorQ
    # ig.jms.ErrorQueue-Provider=Weblogic
    # ig.jms.ErrorQueue-User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.ErrorQueue-Password=sam
    # ig.jms.Queue1.SecurityPrincipal=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.Queue1.SecurityCredentials=EncryptedPassword
    # ig.jms.ErrorQueue-JMSFactory=TopicConnectionFactory
    # ig.jms.ErrorQueue-Url=file:c:/
    #Configure the Error-Topic configuration
    # ig.jms.ErrorTopic=Error
    # ig.jms.ErrorTopic-Provider=IPlanet
    # ig.jms.ErrorTopic-User=sam
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    # ig.jms.ErrorTopic-Password=sam
    # ig.jms.ErrorTopic-JMSFactory=TopicConnectionFactory
    # ig.jms.ErrorTopic-Url=file:c:/
    ## End of JMS configuration Section
    # Profile Information
    # Set it to either TRUE or FALSE
    ig.ProfileInformation=FALSE
    #End-Of Profile Information
    ##EIPTestTool Properties
    #Class name of the Gateway Manager to use during processing
    #ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.EIPTestToolGatewayManager
    #Contains a true or false value.
    #True for LoopBack
    #ig.EIPLoopBack=TRUE
    #Contains the directory path that will be used
    #to store request/response files during recording.
    #ig.EIPOutputDirectory=c:/temp/output
    # Number of ig.EIPMsgProp.N.propFile's
    #ig.EIPMsgProp.count=0
    #Certification root directory
    #ig.EIPInputDirectory=c:/temp/input
    #MessageProperty file names with locations.
    #ig.EIPMsgProp.1.propFile=c:/temp/input/properties/pro1.xml
    #ig.EIPMsgProp.2.propFile=c:/temp/input/properties/pro2.xml
    #Overrides input directory for an EIP
    #ig.EIPMsgProp.1.inputDirectory=c:/temp/input/properties1/
    #EIPNodemapFileName
    #ig.EIPNodeMap=c:/temp/nodemap.xml
    ##End of EIPTestToolProperties
    #File connector password.
    # Use the supplied encryption utility to provide an encrypted password for the entry below
    ig.fileconnector.password=EncryptedPassword
    #End of file connector properties.
    ## Query Access Services (QAS) Configuration Section.
    # QAS Repository Home Directory. This is the directory where Query result blocks will be
    # temporarily persisted.
    # Example:
    #ig.qas.repositoryHomeDir=C:/QASRepository
    # Uncomment the following line and replace the value with the actual QAS Repository Home Directory.
    #ig.qas.repositoryHomeDir=<Full-Path-For-Directory>
    ## END of QAS Configuration.
    ## AS2 Connector Properties.
    # These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
    # REQUIRED:
    # AS2 KeyStore Properties
    # Uncomment the following two lines to specify your key keystore path and password.
    # Use the PSCipher.bat utility to encrypt the keystore password.
    # example:
    # ig.AS2.KeyStorePath=C://pt846//webserv//peoplesoft//keystore//pskey
    # ig.AS2.KeyStorePassword=GD9klUFw8760HVaqeT4pkg==
    # OPTIONAL:
    # AS2 Log Directory, logs all incoming and outgoing AS2 requests and responses.
    # Uncomment and specify the correct directory name to enable logging.
    # example:
    # ig.AS2.LogDirectory = c://temp//as2//logs
    ## End of AS2 Connector Properties
    ## AS2ListeningConnector Only Properties.
    # OPTIONAL:
    # AS2From and AS2To http header parameters are required on all incoming AS2 messages. These parameters must
    # map to PeopleSoft node definitions either directly or indirectly via AS2 From & To map specifications.
    # AS2 From & To Map
    # This map translates incoming AS2From and AS2To http header parameters into PeopleSoft node names.
    # This property is not required if your incoming messages use AS2From and AS2To parameters that match
    # existing PeopleSoft node definitions.
    # ig.AS2.AS2ListenerMap.From.<AS2From>= Specify the PSFT Source Node Name.
    # ig.AS2.AS2ListenerMap.To.<AS2To>= Specify the PSFT Target Node Name.
    # This example translate AS2From from AS2SENDER to PSFT_SRC_NODE, and AS2To from AS2RECEIVER to PSFT_TGT_NODE.
    # example:
    # ig.AS2.AS2ListenerMap.From.AS2SENDER=PSFT_SRC_NODE
    # ig.AS2.AS2ListenerMap.To.AS2RECEIVER=PSFT_TGT_NODE
    # AS2 Message name
    # Message name used to publish AS2 transactions.
    # Use this property if the incoming AS2 Message Name is not in the HTTP Header or the URL.
    # Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters .
    # when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
    # AS2 From & To map above.
    # ig.AS2.<source>.<target>.MessageName= Specify the Message Name
    # example:
    # ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.MessageName=AS2_ORDER_REQUEST
    # These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
    # REQUIRED:
    # AS2 Certificates
    # CertificateAlias is the certificate of the AS2 Listening Node used to decrypt incoming messages.
    # SignerCertificateAlias is the certificate of the AS2From trading partner of Listening Node used to verify
    # the incoming signature.
    # Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters
    # when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
    # AS2 From & To map above.
    # ig.AS2.<source>.<target>.CertificateAlias = Specify the target AS2 Listening Node certificate alias.
    # ig.AS2.<source>.<target>.SignerCertificateAlias = Specify the source AS2From trading partner certificate alias.
    # example:
    # ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.CertificateAlias=<GeneratedAS2certificatealias>
    # ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.SignerCertificateAlias=<GeneratedAS2certificatealias>
    ## End of AS2ListeningConnector Only Properties
    ## AS2 Target Connector Properties
    # These Properties need to be set to use the AS2TargetConnector
    # AS2 Original Request Information Log Directory
    # This is required for Async MDN only. The Async MDN receiver uses this directory
    # to find original request information.
    # example:
    # ig.AS2.AS2Directory=c://temp//as2
    ## END of AS2 Target Connector Properties.
    #XML dtd lookup flag
    # true - enable dtd reference lookup dtd on gateway. this is also the default value.
    # false - disable dtd reference lookup on gateway.
    ig.dtdLookup=true
    # Maximum active connections to be cached on gateway
    # These are connections from gateway to peoplesoft application server
    # Caching connections will improve integration broker throughput
    ig.connection=10
    #####################

  • SOA-Siebel Integration

    Hi
    I am currently working on Siebel(Call Center)-SOA Integration. In the Siebel , I have exposed the Siebel Inbound service "PRODUCT IMPORT" and using the wsdl of "PRODUCT IMPORT " which contains the inbuilt schema I created a SOA Composite thus by invoking (Insert operation ) Siebel Service from the composite.
    I am facing issue while passing the Input : - the service is able to create workspace items in the Siebel "Administration Product" but its not able to create Siebel Product Information
    [ Product Info like "product Type ..etc ]
    Can any one send me a valid input or a sample request to craete a product info in Siebel .
    Thanks

    Hi ,
    Following are the steps to Create a product in siebel :-
    1. Get the Siebel Product Inbound Service (.wsdl file )
    2. Above service contains the inline schema.
    3. Create a BPEL Process based on the Inline schema.
    4. Invoke product Import Service ( create opearation ) to create the product in siebel.
    5. Build and deploy the composite
    6. Please make use of below mentioned SOAP request :-
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
         <soap:Body>
              <ns1:ListOfProductImport xmlns:ns1="http://www.siebel.com/xml/ProductImport">
                   <ns1:ProductImport>
                        <ns1:Id>1-DVE2F</ns1:Id>
                        <ns1:Created>19-MAY-13</ns1:Created>
                        <ns1:Updated></ns1:Updated>
                        <ns1:ConflictId>0</ns1:ConflictId>
                        <ns1:ModId>4</ns1:ModId>
                        <ns1:OverrideLockedFlag>Y</ns1:OverrideLockedFlag>
                        <ns1:WorkspaceId></ns1:WorkspaceId>
                        <ns1:WorkspaceName>Test16</ns1:WorkspaceName>
                        <ns1:WorkspaceReleaseFlag>Y</ns1:WorkspaceReleaseFlag>
                        <ns1:WorkspaceReuseFlag>Y</ns1:WorkspaceReuseFlag>
                        <ns1:ListOfProductDefinition>
                             <ns1:ProductDefinition>
                                  <ns1:Id>1-DVE2F</ns1:Id>
                                  <ns1:Created>19-MAY-13</ns1:Created>
                                  <ns1:Updated></ns1:Updated>
                                  <ns1:ConflictId>0</ns1:ConflictId>
                                  <ns1:ModId>4</ns1:ModId>
                                  <ns1:AutoExplodeFlag>Y</ns1:AutoExplodeFlag>
                                  <ns1:BillableFlag>Y</ns1:BillableFlag>
                                  <ns1:BillingServiceType></ns1:BillingServiceType>
                                  <ns1:BillingType></ns1:BillingType>
                                  <ns1:BusinessUnitId>0-ACWP</ns1:BusinessUnitId>
                                  <ns1:CheckEligibilityFlag>Y</ns1:CheckEligibilityFlag>
                                  <ns1:CommonId></ns1:CommonId>
                                  <ns1:Description>NewProd</ns1:Description>
                                  <ns1:EffectiveEndTime></ns1:EffectiveEndTime>
                                  <ns1:EffectiveStartTime></ns1:EffectiveStartTime>
                                  <ns1:InclusiveEligibilityFlag>Y</ns1:InclusiveEligibilityFlag>
                                  <ns1:IntegrationId>1-DUYH</ns1:IntegrationId>
                                  <ns1:OrderableFlag>Y</ns1:OrderableFlag>
                                  <ns1:PriceType>One-Time</ns1:PriceType>
                                  <ns1:ProductId>1-GHI2</ns1:ProductId>
                                  <ns1:ProductName>LatestProduct20</ns1:ProductName>
                                  <ns1:ProductType></ns1:ProductType>
                                  <ns1:SalesProductFlag>Y</ns1:SalesProductFlag>
                                  <ns1:ServiceInstanceFlag>Y</ns1:ServiceInstanceFlag>
                                  <ns1:ServiceProductFlag>Y</ns1:ServiceProductFlag>
                                  <ns1:StructureType>None</ns1:StructureType>
                                  <ns1:TrackAsAssetFlag>Y</ns1:TrackAsAssetFlag>
                                  <ns1:Type>Insurance</ns1:Type>
                                  <ns1:UnitofMeasure>Dollar</ns1:UnitofMeasure>
                                  <ns1:VendorId></ns1:VendorId>
    </ns1:ProductDefinition>
    </ns1:ListOfProductDefinition>
                        <ns1:ListOfProductStructure>
                             <ns1:ProductStructure>
                                  <ns1:Id>1-DVE2F</ns1:Id>
                                  <ns1:Created>19-MAY-13</ns1:Created>
                                  <ns1:Updated></ns1:Updated>
                                  <ns1:ConflictId>0</ns1:ConflictId>
                                  <ns1:ModId>4</ns1:ModId>
                                  <ns1:ComponentProductBusinessUnitId></ns1:ComponentProductBusinessUnitId>
                                  <ns1:ComponentProductId></ns1:ComponentProductId>
                                  <ns1:ComponentProductName></ns1:ComponentProductName>
                                  <ns1:ComponentProductVendorId></ns1:ComponentProductVendorId>
                                  <ns1:IntegrationId>1-DUYH</ns1:IntegrationId>
                                  <ns1:ProductBusinessUnitId></ns1:ProductBusinessUnitId>
                                  <ns1:ProductId></ns1:ProductId>
                                  <ns1:ProductName></ns1:ProductName>
                                  <ns1:ProductVendorId></ns1:ProductVendorId>
    </ns1:ProductStructure>
    </ns1:ListOfProductStructure>
    </ns1:ProductImport>
    </ns1:ListOfProductImport>
    </soap:Body>
    </soap:Envelope>
    7. After successful testing , have a look at the Invoke_output variable which contains the primary Id of the created product.
    8. Use the primary ID of the product to query product details.
    9. Also you can find the same in database ( if you have access to ..
    select from S_PROD_INT where ROW_ID like 'PRIMARY_ROW_ID';*
    Edited by: Surya on May 21, 2013 9:13 AM

Maybe you are looking for