Bpel-config.xml and soa-infra-config.xml file location in SOA 11g Pre-built

Hi frnds,
I have downloaded and started Oracle SOA 11g Pre-built from http://www.oracle.com/technetwork/middleware/soasuite/learnmore/vmsoa-172279.html and trying to configure it according to my requirements to upgrade from SOA 10g to 11g. But I can't find bpel-config.xml and soa-infra-config.xml files in BPEL domain home (i.e. /oracle/fmwhome/user_projects/domains/domain1).
Can you please help me?
BR, Lisan

None of those roles are intended to be granted to application users. Those are instead to limit various operational / support responsibilities. For instance, if you have "operators" for your production environment who are responsible for starting & stopping servers vs "Administrators" who are performing configuration changes, etc.
The SOA* versions can be used to separate even further - an "Operator" ( with rights in the WL console ) can be distinct from a "SOAOperator" ( with rights in the SOA /em ), etc.
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10226/appx_roles_privs.htm#insertedID2
also, here is a bit more on soa-infra roles:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10226/appx_users.htm#insertedID4

Similar Messages

  • Ejb-jar.xml and orion-ejb-jar.xml configuration issue

    Chris,
    We have an application that uses the Oracle 10g Application Server and WebSphere MQ v5.3 w/ fixpack 9.
    Our application is a J2EE messaging system which essentially consists of Message Driven Beans, the EJB
    realization of the J2EE Java Message Service (JMS) API. Our application has Message Driven Beans which
    listen to queues and send messages to queues -- a simple messaging system. Currently we can listen to queues, but
    cannot send messages to queues in the Oracle 10g Application Server environment.
    Any J2EE application server has its own implementation of Java Naming Directory Interface (JNDI) API that
    deployed J2EE applications utilize to lookup resources such as Data Sources, JMS Destinations (i.e. MQ Queue),
    JMS QueueConnectionFactories (i.e. MQ QManagers).
    Our application uses the 3rd party JMS Provider, WebSphere MQ.
    MQ ships with a JMSAdmin tool which allows one to create JMS administered objects (i.e. objects a java
    application searches for in some JNDI directory) that reside in some JNDI context. We create a JNDI context for
    MQ resources, queues and QManagers. We configure the MQ provided
    JMSAdmin tool with two property name/value pairs:
    PROVIDER_URL=file:/opt/mqm/JNDI-Directory
    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    A resultant .bindings file is created in /opt/mqm/JNDI-Directory which represents our JDNI context
    containing our JMS administered objects. A standalone java application that needs to directly access this
    JNDI context can simply conduct a JNDI lookup on the following context: "java:comp/resource/MQSeries/". An
    example of how a standalone application would lookup a JMS administered object named "qNumber1" would be to
    lookup "java:comp/resource/MQSeries/qNumber1". This lookup would result in the standalone java application
    having a JMS reference to an MQ Queue.
    There is a major difference in how an enterprise EJB application deployed into a J2EE Container (Oracle 10g App Server)
    conducts a JNDI lookup on a 3rd party resource such as MQ as a JMS Provider. A typical EJB application deployed
    into a J2EE container as an .ear (enterprise archive) file has implicit access to the application server's own
    JNDI context. This JNDI context is usually "java:comp/env/". Looking up the Application Server's own Data Source or
    it's own JMS Resources is easy. An application that needs references to these Application Server provided resources
    simply conducts a lookup for "java:comp/env/jms/someQ" or "java:comp/env/jdbc/myDataSource".
    The problem we face is mapping our MQ JNDI context to the Oracle App Server's own JNDI context. We believe this is
    accomplished through mappings defined in both the ejb-jar.xml (EJB Descriptor) and the application server specific
    counterpart, orion-ejb-jar.xml. Note that Oracle 10g Application Server uses the popular orion J2EE container for
    hosting J2EE enterpise applications.
    Our Message Driven Beans (MDBs)currently listen to the Queue at the JNDI location "prodQ". Our problem is that we cannot
    get our MDB to send messages to any queues. Note that the MQ implementation of the queues and Queue Managers work
    flawlessly with standalone java applications. It's safe to say that the MQ objects are working.
    We are looking for a solid example of how the ejb-jar.xml and the orion-ejb-jar.xml map 3rd party JMS provider
    JNDI locations to the App Server's JNDI context.
    Below is how we have attempted to configure our own ejb-jar.xml and orion-ejb-jar.xml:
    ejb-jar.xml begin >>>>>>>>>>>>>>><?xml version = '1.0' encoding = 'UTF-8'?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <display-name>Production Message Driven Bean</display-name>
    <enterprise-beans>
    <message-driven>
    <display-name>prodMdb</display-name>
    <ejb-name>prodMdb</ejb-name>
    <ejb-class>message.handler.AIDMSMessageConsumerBean</ejb-class>
    <transaction-type>Bean</transaction-type>
    <message-driven-destination>
    <destination-type>javax.jms.Queue</destination-type>
    </message-driven-destination>
         <resource-ref>
    <res-ref-name>prodQCF</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Application</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
         <resource-ref>
    <res-ref-name>prodQ</res-ref-name>
    <res-type>javax.jms.Queue</res-type>
    <res-auth>Application</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
                   <resource-ref>
    <res-ref-name>prodR</res-ref-name>
    <res-type>javax.jms.Queue</res-type>
    <res-auth>Application</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    </message-driven>
    </enterprise-beans>
    </ejb-jar>
    <<<<<<<< ejb-jar.xml end <<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    begin orion-ejb-jar.xml >>>>>>>>>>>>>>>>>>>>>>>>>>><orion-ejb-jar>
    <enterprise-beans>
    <message-driven-deployment name="prodMdb" connection-factory-location="java:comp/resource/MQSeries/prodQCF" destination-location="java:comp/resource/MQSeries/prodR">
              <resource-ref-mapping location="prodQ" name="prodQ">     
                   <lookup-context location="java:comp/resource/MQSeries/" >
                        <!-- <context-attribute name="java.naming.factory.initial"
                             value="com.sun.jndi.fscontext.RefFSContextFactory" /> -->
                   </lookup-context>
              </resource-ref-mapping>
              <resource-ref-mapping location="prodR" name="prodR">     
                   <lookup-context location="java:comp/resource/MQSeries/" >
                        <!-- <context-attribute name="java.naming.factory.initial"
                             value="com.sun.jndi.fscontext.RefFSContextFactory" /> -->
                   </lookup-context>
              </resource-ref-mapping>
         </message-driven-deployment>
    </enterprise-beans>
    </orion-ejb-jar>
    <<<<<<<<< end orion-ejb-jar.xml <<<<<<<<<<<<<<<<<<<<<<<<

    If you look at the contents of a deployment plan (Plan.xml) when you have it generated
    <deployment-plan ...>
      <module-override>
        <module-name>ejb.jar</module-name>
        <module-type>ejb</module-type>
        <module-descriptor external="true">
          <root-element>weblogic-ejb-jar</root-element>
          <uri>META-INF/weblogic-ejb-jar.xml</uri>
        </module-descriptor>
        <module-descriptor external="false">
          <root-element>ejb-jar</root-element>
          <uri>META-INF/ejb-jar.xml</uri>
        </module-descriptor>
        <module-descriptor external="true">
          <root-element>persistence-configuration</root-element>
          <uri>META-INF/persistence-configuration.xml</uri>
        </module-descriptor>
        <module-descriptor external="false">
          <root-element>persistence</root-element>
          <uri>META-INF/persistence.xml</uri>
        </module-descriptor>
      </module-override>
    </deployment-plan>You can see which files can be external and which can be not. The weblogic-ejb-jar.xml can be external
    but in this case you need a deployment plan to point weblogic to the file. The ejb-jar.xml cannot be
    external (see external=false)
    The benefit of storing the weblogic-ejb-jar.xml is that your administrator can fine tune certain
    configurations by using a deployment plan, instead of having to extract the contents from the jar file
    and then repackage it again.
    No need to worry about a clustered environment, you can place the jar and the deployment plan
    on the server where the admin server is located, when you deploy an application you deploy it to
    the cluster and everything is taken care off.
    More information on deployment plans can be found here: http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/config.html

  • Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml

    Hi  All,
    we are not able to connect to Live office to our server . URL is  not authenticated in Excel and  if we place same url in browser ,we are getting below error message.
    "Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml"
    we couldn't able to rest the same after changing settings in axis2 file also.
    Any solution where we can configure in CMC or any files
    Regards
    Mahesh

    Hi Mahesh,
    As mentioned by Abhilasha, this is the expected behavior.
    In order to validate you could place the following URL in the browser.
    http://servername:portno/dswsbobje. you would see Tomcats home page which will display the list of Services.
    As far as the Live office in Excel is concerned , If you are getting a yellow  exclamation mark stating (Web service not correct) next to Session URL, try changing the servername to IPaddress of the server.
    Eg: http://ipaddress:portno/dswsbobje/services/Session
    While inserting the Session URL in the Live Office settings confirm the URL as per above.
    If the issue still persists, you could configure the host file entry in you client machine.
    Let me know if the information is helpful.
    Regards,
    Noopur

  • Open and work on FCP project file located at xsan volume

    It is recommended by apple to *open and work on FCP project file located at xsan volume*
    or we should open , work and save our FCP project file from local drive only .
    Is there is risk of corrupting xsan volume if we open FCP project file placed in xsan volume .
    where should be the location of FCP project files ??????
    Mac pro 2.66 , FCP 6.01, xsan 1.4

    Opening a file twice is a indeed a problem. To prevent this, and for numerous other reasons, we use Open Directory. In OD you can configure that a user can login just once (concurrently).
    In old versions of xsan it was not recommended to put project files on xsan, but nowadays it works fine.
    Putting projectfiles on a san has the advantage that a user can work on any client. If this is not important in your environment these files can be stored locally.

  • Deploytool not deleting fields in ejb-jar.xml and sun-cmp-mappings.xml

    Java(TM) 2 Platform, Enterprise Edition 1.4 SDK Developer Release deploytool
    This situation was found on a simple, but original application using CMP EJB's. The database is MySQL using numeric id's and foreign keys.
    I changed some fields in the database and went through the usual 14 attempts at getting deploytool to recognize a new schema without success. The one thing that is noticed is that when I tried to open the CMP display in the Entity selection the tool would not show any data, also it appears to lockup; however, if you select EJB in the choice box of the upper left you can get the view to close.
    In desperation (mind you decoding machine generated XML is NOT my favorite activity) I looked at the descriptor viewer and notice fields existed in the descriptor that were deleted in the database. The tool had read the schema because the new fields were also present.
    In sun-cmp-mappings.xml the old <cmp-field-mapping> definitions were still present. and in ejb-jar.xml the <query> and <cmp-field> were still present.
    After deleting them out -- happy, happy, happy, joy, joy, joy. Deploytool accepted the new schema (keeping all the proper old stuff correctly. yea!!!) and a simple create mapping process brought the beans and database into sync.
    I didn't want to report a bug, since I am actually new to EJB's so if anybody wishes to comment please do. I just wanted to provide a heads up in case this was something not noticed.
    BTW I'm a recent expert at EJB's anybody got a job? :-)

    Have you tried to unmap your fields and relationships?
    Go through all your enterprise beans in the CMP Database window and click Unmap All until the Persistent Field Mappings table is empty of mappings. Then click Create Database Mappings, select the new schema, and verify the fields and relationships were mapped. This should clear out any old field mappings.
    -Ian Evans

  • Performance on  Schema based Xml and No Schema based XML

    Hai,
    We can insert two kind of xml like schema based xml document and non schema based xml document into XMLTYPE fields.I like to know which xml document will have good performance ( fast access ) compare to another.
    Even if we have any other approach than schema.It will be great.
    We do XPath query to get the values from xml document.Is there any way to get the fields faster than the XPath.I am using Oracle 10g R2.
    I need to access much fast the xml element from the table.Please help me!.
    Thanks,
    Saravanan.P

    HHave you read the FAQ or any of the XML DB whitepapers... If not I suggest that you do so before proceeding any further or asking any more questions. If you take the time to a do a little basic research you should be able to see that you have made the worst possible decision if performance is importantto you.
    If you invested a little bit of effort before posting you would soon understand that in 10gR2 you will need to use schema based storage to get high performance, and that it doesn't matter whether you use XPath or XQuery, what matters is whether or not the XPath or XQuery operations get re-written correctly so the database can optimize them.

  • BPEL assign count and node value from xml

    I have mapnames.xml in the project with nodes like this:
    <mapname>STATUS_DIMS_LOAD</mapname>
    <mapname>MOVEMENT_DIMS_LOAD</mapname>
    The xml of mapnames will be used for an input variable for a FlowN invoke.
    Trying to count the number of mapnames in the xml document and put in a variable.
    <assign name="getMapNamesN">
    <copy>
    <from expression= *"count(bpws:getVariableData('... ? " />*
    <to variable="FlowN_Dims_Count"/>
    </copy>
    </assign>
    Then use that in the FlowN
    <bpelx:flowN name="FlowN_Dims" N="bpws:getVariableData('Flow_Dims_Count')" indexVariable="Index">
    And then inside the FlowN, get the actual mapname using the index.
    <assign name="Assign_Dims">
    <copy>
    <from expression= *"bpws:getVariableData('... ? [',bwps:getVariableData('Index'),']') " />*
    <to variable="Invoke_Dims_InputVariable" part="InputParameters"
    query="/ns8:InputParameters/ns8:P_MAPNAME" />
    </copy>
    </assign>
    What is the syntax to
    1. Count the number of mapnames in the xml document?
    2. Use the FlowN index to assign the mapname to an input variable?

    That looked hopeful, but it did not show how to create the variables and I do not know the syntax for making an array variable.

  • Storing ejb-jar.xml and weblogic-ejb-jar.xml

    We are using Weblogic Integration 9.2 on a 2 cluster system sharing the same domain directory.
    1) I am wondering if I can store these files somewhere in the domains directory instead of the EJB's archive - call it MyEjb.jar?
    2) Are there any benefits to storing these files outside of the MyEjb.jar file? I am thinking to make it easier to update the configurations such as number of MDB consumers and such to avoid having to recreate the MyEjb.jar with the new config and redeploy the application. A simple text edit and bounce could be fine if the files can be stored outside.
    2b) Can another application in the same domain read these files to find out the connection factory and queue information?
    3) Are there any disadvantages to storing those files outside of the jar file? One issue I can think of here is how to deal with them on a cluster environment.
    4) Any other feedback apprecaited.

    If you look at the contents of a deployment plan (Plan.xml) when you have it generated
    <deployment-plan ...>
      <module-override>
        <module-name>ejb.jar</module-name>
        <module-type>ejb</module-type>
        <module-descriptor external="true">
          <root-element>weblogic-ejb-jar</root-element>
          <uri>META-INF/weblogic-ejb-jar.xml</uri>
        </module-descriptor>
        <module-descriptor external="false">
          <root-element>ejb-jar</root-element>
          <uri>META-INF/ejb-jar.xml</uri>
        </module-descriptor>
        <module-descriptor external="true">
          <root-element>persistence-configuration</root-element>
          <uri>META-INF/persistence-configuration.xml</uri>
        </module-descriptor>
        <module-descriptor external="false">
          <root-element>persistence</root-element>
          <uri>META-INF/persistence.xml</uri>
        </module-descriptor>
      </module-override>
    </deployment-plan>You can see which files can be external and which can be not. The weblogic-ejb-jar.xml can be external
    but in this case you need a deployment plan to point weblogic to the file. The ejb-jar.xml cannot be
    external (see external=false)
    The benefit of storing the weblogic-ejb-jar.xml is that your administrator can fine tune certain
    configurations by using a deployment plan, instead of having to extract the contents from the jar file
    and then repackage it again.
    No need to worry about a clustered environment, you can place the jar and the deployment plan
    on the server where the admin server is located, when you deploy an application you deploy it to
    the cluster and everything is taken care off.
    More information on deployment plans can be found here: http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/config.html

  • Does TopLink 10g generate toplink-ejb-jar.xml and weblogic-ejb-jar.xml?

    Also, does it have the ability to deploy an EJB JAR to an app server of choice?
    Thanks in advance.

    TopLink's Mapping Workbench will generate the toplink-ejb-jar.xml file for use in CMP and will augment the base ejb-jar.xml file.
    http://download-west.oracle.com/docs/cd/B10464_04/web.904/b10313/pkg_depl.htm#1132804
    TopLink does not generate the container specific file for WebLogic. More details available at:
    http://download-west.oracle.com/docs/cd/B10464_04/web.904/b10313/pkg_depl.htm#1124592
    TopLink does not include any deployment capabilities. This is the roll of yor IDE or scripts.
    Doug

  • What is stringtable.xml and can I delete the files?

    I just looked at my downloads file and there are LOTS of stringtable.xml files.  Can someone please explain what they are and whether or not I can delete them?
    Thank you.

    Google's your friend. A quick search for stringtable.xml brought up https://discussions.apple.com/thread/4650504

  • SOA managed server and SOA infra not starting

    Hi
    I have my database and listener up and running. I can also successfully start SOA Administration server.
    But I am unable to start SOA managed server. I can see SOA managed server getting started with WARNING and SOA infra always fails to start.
    I tried using both from command line as well as from NodeManager but without any luck. As a result I am unable to proceed with Deployment as soa_server1 does not appear in Step 4 in Jdeveloper deployment GUI dialog. I would also like to ask from the Gurus:
    How can I start soa-infra alone as I cannot see any command from the command line to individually start soa-infra ?
    Here is my part of output from soa_server1. The exception errors keep logging in loop and the file is growing. I had to terminate the process:
    <Jun 3, 2010 10:40:03 PM> <INFO> <NodeManager> <Server output log file is '/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.out'>
    ** Setting up SOA specific environment...
    EXTRA_JAVA_PROPERTIES= -da:org.apache.xmlbeans...
    LD_LIBRARY_PATH=/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/native:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/lib/i386/jrockit:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/lib/i386:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/../lib/i386:/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/native:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/thirdparty/edifecs/XEngine/bin
    USER_MEM_ARGS=-Xms512m -Xmx512m
    ** End SOA specific environment setup
    ** SOA specific environment is already set, skipping...
    JAVA Memory arguments: -Xms512m -Xmx512m
    WLS Start Mode=Development
    CLASSPATH=/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/user-patch.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/soa-startup.jar::/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/lib/tools.jar:/home/oracle1/Oracle/Middleware/utils/config/10.3/config-launch.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/home/oracle1/Oracle/Middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.common.adapters_11.1.1/oracle.soa.common.adapters.jar:/home/oracle1/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/home/oracle1/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.xdk_11.1.0/xsu12.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules.xquery_10.3.1.0.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/db2jcc4.jar:/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/soa-infra:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/fabric-url-handler_11.1.1.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/quartz-all-1.6.5.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar:/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/lib/tools.jar:/home/oracle1/Oracle/Middleware/utils/config/10.3/config-launch.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/home/oracle1/Oracle/Middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle1/Oracle/Middleware
    PATH=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/bin:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/bin:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin:/u02/app/oracle/product/11.1.0/db_1/bin:/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_14"
    Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
    BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
    Starting WLS with line:
    /home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da -Dplatform.home=/home/oracle1/Oracle/Middleware/wlserver_10.3 -Dwls.home=/home/oracle1/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/home/oracle1/Oracle/Middleware/wlserver_10.3/server -Ddomain.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1 -Dcommon.components.home=/home/oracle1/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig -Doracle.server.config.dir=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/servers/soa_server1 -Doracle.security.jps.config=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/carml -Digf.arisidstack.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1 -Dtangosol.coherence.clusteraddress=227.7.7.8 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dcom.sun.management.jmxremote -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/home/oracle1/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dbam.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dums.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.2.103:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    [JRockit] Local management server started.
    <Jun 3, 2010 10:40:15 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
    <Jun 3, 2010 10:40:21 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
    <Jun 3, 2010 10:40:35 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 3, 2010 10:40:35 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jun 3, 2010 10:40:36 PM EST> <Notice> <LoggingService> <BEA-320400> <The log file /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jun 3, 2010 10:40:36 PM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log00281. Log messages will continue to be logged in /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log.>
    <Jun 3, 2010 10:40:36 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log is opened. All server side log events will be written to this file.>
    <Jun 3, 2010 10:41:10 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jun 3, 2010 10:41:51 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Jun 3, 2010 10:41:51 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 3, 2010 10:43:51 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
    <Jun 3, 2010 10:43:53 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/worklistapp/r8n7fr]. Make sure the referenced optional package has been deployed as a library.>
    <Jun 3, 2010 10:44:07 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-26024> <Registration of driver Email-Driver did not complete; will retry periodically until messaging server responds.>
    <Jun 3, 2010 10:44:35 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "jsp" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Jun 3, 2010 10:44:46 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh], [Extension-Name: oracle.soa.adapter, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh]. Make sure the referenced optional package has been deployed as a library.>
    <Jun 3, 2010 10:45:00 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "mds-soa": Socket read timed out>
    <Jun 3, 2010 10:45:02 PM EST> <Error> <oracle.mds> <BEA-000000> <
    oracle.mds.lcm.exception.MDSLCMException: MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
    weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out
         at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:170)
         at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
         at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
         at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: oracle.mds.exception.MDSException: MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
    weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out
         at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(ConnectionManagerFactory.java:80)
         at oracle.mds.internal.persistence.db.DBStoreUtils.getConnectionManager(DBStoreUtils.java:389)
         at oracle.mds.persistence.stores.db.DBMetadataStore.checkRepositoryCompatibility(DBMetadataStore.java:815)
         at oracle.mds.persistence.stores.db.DBMetadataStore.checkCompatibility(DBMetadataStore.java:1092)
         at oracle.mds.persistence.stores.db.DBMetadataStore.<init>(DBMetadataStore.java:276)
         at oracle.mds.internal.lcm.MDSLCMManager.createMetadataStore(MDSLCMManager.java:2064)
         at oracle.mds.internal.lcm.deploy.DeployManager.createMetadataStore(DeployManager.java:660)
         at oracle.mds.internal.lcm.deploy.DeployManager.deployToDBRepository(DeployManager.java:974)
         at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:445)
         at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:168)
         at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160)
         at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
         at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
         at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Hi
    Thanks for your reply
    Here is my installation details on Linux 32 bit OS:
    Weblogic server- wls1032_linux32.bin
    Repository Creation Utility- ofm_rcu_linux_11.1.1.2.1_disk1_1of1.zip
    SOA Suite- ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip
    JDeveloper Studio, base install- jdevstudio11112install.jar
    SOA Extension for JDeveloper- ofm_osb_generic_11.1.1.3.0_disk1_1of1.zip
    The installation went very smooth and there was no errors in the same.
    I can successfully start the Weblogic Administration server from the command line but unable to start successfully SOA Managed (soa_server1), Infra and BAM server (bam_server1). I tried starting SOA Managed (soa_server1) from command line as well as from Weblogic console EM (after starting Node Manager) but always receiving the errors I uploaded in my post earlier. As a result I am unable to deploy any composite application
    Please advice
    Thanks
    Rohit

  • Conversion of purchasing idoc to xml and sending with FTP to supplier

    Hello,
    I have a question about something i am not very familar with. And i could not find the answer in this forum.
    We have a supplier who wants to receive our orders by EDI.
    The plan is to convert the IDOC to XML and to send this XML by FTP to our supplier.
    Could anyone give me some hints to achieve this.
    usefull help will be rewarded.
    Gr., Frank

    Hi,
    1. Create XML port in WE21.
    2. Configer the partner profile in WE20 for required message type.
    3. Access the file by using transaction AL11.
    Thanks,
    Asit Purbey

  • Override JNDI names in persistence.xml and @resource annotation

    I have a Java EE 7 application that I am developing for use with both GlassFish and WildFly, but I have discovered that both application servers use a slightly different format for specifying JNDI names.
    In GlassFish the persistence.xml file references the data source jdbc/myDataSouce, but in WildFly the data source needs to be java:/jdbc/myDataSource.The same is also true for classes that are annotated with @Resource. In GlassFish the annotation for a class using JavaMail would be @Resource(name = "mail/myMailSession"), but to deploy onto WildFly this would need to be @Resource(name = "java:mail/myMailSession").
    The only solution I've got at present is using Maven to create two different releases of the EAR file, with one EAR file containing a persistence.xml file with the data source jdbc/myDataSouce for use with GlassFish, and the second EAR file containing a persistence.xml file with the data source java:/jdbc/myDataSource for use with WildFly. Unfortunately, I haven't found a solution for the @Resource annotation.
    I've taken a look at the documentation for glassfish-application.xml and glassfish-ejb-jar.xml and have tried using resource-ref to override the JNDI names but the application fails to deploy due to an error in the name.
    My question is does GlassFish provide any capability to override the JNDI names specified in the persistence.xml file and classes with the @resource annotation?
    Many Thanks
    Paul

    Have you been able to solve this? I'm attempting to understand what Web Server 7 can do with regard to Java Persistence and what elements of it require Glassfish.
    I've also spent great amounts of time in WS6.1 trying to figure out why a JNDI resource couldn't be found. The rules of thumb I've learned are:
    - Try dropping the *'java:/comp/env/* prefix; just use jdbc/pact part
    - Make sure all referrences (in web.xml and sun-web.xml) are identical with regard to that name.
    I'm hoping you're not still dealing with this (it's been two months!) but if anybody else stumbles on this, maybe it'll help them.
    Dave

  • Stateless session Bean - xml and ejb-jar.xml file ???

    Dear Experts,
    Stateless-session bean
    For Creating an ear file
    we need ejb-jar.xml and weblogic-ejb-jar.xml files
    Is these files are already available
    or we have to type these files ??
    Advance Thanks
    Rengaraj.R

    My best advice: surrender to use an IDE.
    You wonder sometimes at how much productivity (read as 'time') could be wasted by doing something that could be done automatically. For a learning experience or a once only exercise is fine but as a routine thing, not worth it.
    Cheers

  • Use Sign.xml and Encrypt.xml for both request AND response within WSDL?

    Hi,
    ALSB: 2.6
    I was wandering if it's possible to use abstract outof the box WS-Policy file within WSDL file to specify encryption
    (Encrypt.xml) and digital signature(Sign.xml) with X509 for both request and response???
    So far, it only works for either request or response BUT not both. i.e. within WSDL file
    <!-- following WSDL works for encrypting and signing request with X509 in test console -->.....
    <wsdl:binding name="DexService2Soap" type="tns:DexService2Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="Message">
                <soap:operation soapAction="urn:moe:dex:dexservice:2.0.0/Message" style="document" />
                              <wsdl:input>
                               <!-- WS-Policy file applied here -->
                             <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                     <soap:body use="literal" />
                               </wsdl:input>
                             <wsdl:output>
                                  <soap:body use="literal" />
                               </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
               Or
    <!-- following WSDL works for encrypting and signing response with X509 in test console -->
    <wsdl:binding name="DexService2Soap" type="tns:DexService2Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="Message">
                <soap:operation soapAction="urn:moe:dex:dexservice:2.0.0/Message" style="document" />
                              <wsdl:input>
                                     <soap:body use="literal" />
                               </wsdl:input>
                             <wsdl:output>
                                       <!-- WS-Policy file applied here -->
                                       <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                  <soap:body use="literal" />
                               </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
    But not both
    <!-- following WSDL doesn't work for encrypting and signing both response and request with X509 in test console -->
    <wsdl:binding name="DexService2Soap" type="tns:DexService2Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="Message">
                <soap:operation soapAction="urn:moe:dex:dexservice:2.0.0/Message" style="document" />
                              <wsdl:input>
                                        <!-- WS-Policy file applied here -->
                                       <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                     <soap:body use="literal" />
                               </wsdl:input>
                             <wsdl:output>
                                       <!-- WS-Policy file applied here -->
                                       <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                  <soap:body use="literal" />
                               </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
    ...      Instead, I got error message like
    <15/01/2008 10:15:04 AM NZDT> <Error> <ALSB Security> <BEA-387023> <An error ocurred during web service security inbound response processing [error-code: Fault
    , message-id: 3917705281899426819-4368b1eb.117762cff6e.-7fdb, proxy: DexServiceX509-Stub/Proxy Services/DexServiceX509-ProxyService, operation: Message]
    --- Error message:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode>
    <faultstring>Failed to get token for tokenType: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3</faultstring></soapenv:Fa
    ult></soapenv:Body></soapenv:Envelope>
    weblogic.xml.crypto.wss.WSSecurityException: Failed to get token for tokenType: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#
    X509v3
    at weblogic.xml.crypto.wss.SecurityBuilderImpl.addEncryption(SecurityBuilderImpl.java:308)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processConfidentiality(SecurityPolicyDriver.java:280)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:75)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:64)
    at weblogic.wsee.security.WssServerHandler.processOutbound(WssServerHandler.java:86)
    Truncated. see log file for complete stacktrace
    >
    <15/01/2008 10:15:24 AM NZDT> <Error> <com.bea.weblogic.kernel> <000000> <Failed to build CertPath
    java.security.cert.CertPathBuilderException: [Security:090603]The certificate chain is invalid because it could not be completed. The trusted CAs did not inclu
    de CN=x509,OU=x509,O=x509,L=Wellington,ST=Wellington,C=NZ.
    at weblogic.security.providers.pk.WebLogicCertPathProviderRuntimeImpl$JDKCertPathBuilder.engineBuild(WebLogicCertPathProviderRuntimeImpl.java:669)
    at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194)
    at com.bea.common.security.internal.legacy.service.CertPathBuilderImpl$CertPathBuilderProviderImpl.build(CertPathBuilderImpl.java:67)
    at com.bea.common.security.internal.service.CertPathBuilderServiceImpl.build(CertPathBuilderServiceImpl.java:86)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
            Truncated. see log file for complete stacktrace
    >
    <15/01/2008 10:15:24 AM NZDT> <Error> <ALSB Security> <BEA-387022> <An error ocurred during web service security inbound request processing [error-code: Fault,
    message-id: 3917705281899426819-4368b1eb.117762cff6e.-7fd8, proxy: DexServiceX509-Stub/Proxy Services/DexServiceX509-ProxyService, operation: null]
    --- Error message:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><soapenv:Fault xmlns:wsse="http://docs.oasis-open.or
    g/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><faultcode>wsse:InvalidSecurityToken</faultcode><faultstring>Security token failed to validate. weblo
    gic.xml.crypto.wss.SecurityTokenValidateResult@3c5347b[status: false][msg [
      Version: V1
      Subject: CN=x509, OU=x509, O=x509, L=Wellington, ST=Wellington, C=NZ
      Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
      Key:  Sun RSA public key, 1024 bits
      modulus: 13052787793731294943682394984664645854838424340012907077330623....
      The 'System Error Handler' from 'Invocation Trace' in ALSB test console is something like
    [pre]     
    $fault:
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
         <con:errorCode>BEA-386201</con:errorCode>
         <con:reason>
              A web service security fault
              occurred[{http://schemas.xmlsoap.org/soap/envelope/}Server][Failed
              to get token for tokenType:
              http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3]
         </con:reason>
         <con:details>
              <err:WebServiceSecurityFault
                   xmlns:err="http://www.bea.com/wli/sb/errors">
                   <err:faultcode
                        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
                        soapenv:Server
                   </err:faultcode>
                   <err:faultstring>
                        Failed to get token for tokenType:
                        http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3
                   </err:faultstring>
              </err:WebServiceSecurityFault>
         </con:details>
         <con:location>
              <con:path>response-pipeline</con:path>
         </con:location>
    </con:fault>
    So is this a feature not supported in ALSB 2.6 yet or am I missing something dead simple?
    Thanks in advance
    Sam

    Instead of specifying policies for input and output separately you could place the policy reference only once in the operation element. Maybe will this solve your problem...
    http://e-docs.bea.com/alsb/docs26/security/ws_policy.html#wp1061166

Maybe you are looking for

  • CRM 2007 : Unable to access the BP_HEAD component

    Hello, I'm a basis guy, very new to SAP CRM. We have been asked to install CRM 2007. We are able to ping the crm server from transaction sicf. The users are able to access the webclient, they're able to acess the component "CRM_UI_FRAME" Therefore, i

  • HT201364 Free up memory space on start up disk

    How do you remove items from start up disk to free memory space?

  • Problem of create file

    Hello everyone. I want to create file ,and the content of the file can refurbish in a two days. What should I do ? Thanks.

  • Processflow to load data in datawarehouse FAILURE

    People, I have the following problem. I would like to fill the datawarehouse with a processflow. i cann see he will run good for a while but after 2hours or something he gives a Failure. a non-numeric character was found where a numeric was expected+

  • Install old version of apps

    Hi I have a 2nd generation iPod Touch, and as such, I can only update it to 4.2.1. The problem is that now most of the apps in the AppStore tell me to get newr versions of the iOS, wich I can't. Is there any way to install older versions of the apps,