Reading SAML attributes inside BPEL on weblogic 11g

Hi,
My customer wants to access to SAML token attributes and username inside BPEL workflow on weblogic 11g.
This workflow is exposed as a webservice and is protected by attached policy.
My question is if it is possible to access SAML token attributes inside BPEL, is yes how to do it.
Thanks
Hubert

Is this what you are looking for??
http://lesterrebollos.blogspot.co.uk/2008/02/extracting-wsse-security-headers-from.html??
best regards Nicolas

Similar Messages

  • Read SAML attributes in Proxy service

    Hi,
    I need to read SAML attributes in a proxy service in OSB. But the SAML is not available.
    The client call a service with encrypted SAML im Header, but when I read the header in Proxy service, the SAML is no more available.
    Client call with:
    Authorization: Basic MTAyOjw/eG1sIHZlcnNpb249IjEuMCIgZW5jb2Rpbmc9IlVURi04Ij8+CjxzYW1sMnA6UmVzcG9uc2UgSUQ9IlJlc3BvbnNlX2YzY2ZkZjM5NWIyNzI3ZWFhZWEyZDlhYTRkMWNhY2RhNzgzNGMxZWMiIElzc3VlSW5zdGFudD0iMjAxMi0wOC0zMFQwNjoyMDoyMC43MDNaIiBWZXJzaW9uPSIyLjAiIHhtbG5zOnNhbWwycD0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6Mi4wOnByb3RvY29sIj48c2FtbDI6SXNzdWVyIHhtbG5zOnNhbWwyPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6YXNzZXJ0aW9uIj5uZXZpc0F1dGg8L3NhbWwyOklzc3Vlcj48c2FtbDJwOlN0YXR1cz48c2FtbDJwOlN0YXR1c0NvZGUgVmFsdWU9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpzdGF0dXM6U3VjY2VzcyIvPjwvc2FtbDJwOlN0YXR1cz48c2FtbDI6QXNzZXJ0aW9uIElEPSJBc3NlcnRpb25fM2MxYzZlZGM1NWQ4ZDVhN2QzNmQ2NTkzMzlmMzgxNzBhOWU1Mzk0NiIgSXNzdWVJbnN0YW50PSIyMDEyLTA4LTMwVDA2OjIwOjIwLjM4OVoiIFZlcnNpb249IjIuMCIgeG1sbnM6c2FtbDI9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphc3NlcnRpb24iIHhtbG5zOnhzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYSI+PHNhbWwyOklzc3Vlcj5uZXZpc0F1dGg8L3NhbWwyOklzc3Vlcj48ZHM6U2lnbmF0dXJlIHhtbG5zOmRzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3htbGRzaWcjIj4KPGRzOlNpZ25lZEluZm8+CjxkczpDYW5vbmljYWxpemF0aW9uTWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS8xMC94bWwtZXhjLWMxNG4jIi8+CjxkczpTaWduYXR1cmVNZXRob2QgQWxnb3JpdGhtPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3htbGRzaWcjcnNhLXNoYTEiLz4KPGRzOlJlZmVyZW5jZSBVUkk9IiNBc3NlcnRpb25fM2MxYzZlZGM1NWQ4ZDVhN2QzNmQ2NTkzMzlmMzgxNzBhOWU1Mzk0NiI+CjxkczpUcmFuc2Zvcm1zPgo8ZHM6VHJhbnNmb3JtIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnI2VudmVsb3BlZC1zaWduYXR1cmUiLz4KPGRzOlRyYW5zZm9ybSBBbGdvcml0aG09Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMTAveG1sLWV4Yy1jMTRuIyI+PGVjOkluY2x1c2l2ZU5hbWVzcGFjZXMgUHJlZml4TGlzdD0ieHMiIHhtbG5zOmVjPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzEwL3htbC1leGMtYzE0biMiLz48L2RzOlRyYW5zZm9ybT4KPC9kczpUcmFuc2Zvcm1zPgo8ZHM6RGlnZXN0TWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnI3NoYTEiLz4KPGRzOkRpZ2VzdFZhbHVlPnRvUzBGM3lxSjdPTXpUZmYzQ05oVFlvQ0x1Yz08L2RzOkRpZ2VzdFZhbHVlPgo8L2RzOlJlZmVyZW5jZT4KPC9kczpTaWduZWRJbmZvPgo8ZHM6U2lnbmF0dXJlVmFsdWU+ClNjTlJBc0cvY2loSFB2cVRPTHhOSkNOQUhjdVNoU0NCZDQ4UTNDK1ZieHQ3OHVoZDZNbHdVdDhuaDVJc1hJK2k4SldWRFJiMnJVMUYKcGxYeUdrcWRDYWRtcVB5bjRUb00wZ2tLRTF3R05wb1lLYkFtaGl5ZDZyai9yK2E0SEVmUUxvQmxxWTQ4TTBzZWRra1dlY0orcGE1NwppbUM3ekNzWlhWbWFSNzdvZEZPVVhsR1FwNFlpbnlBaExrbVk1QjlkNjVZSE91akh3UFhLTURaT3VwSlExMURIcFE3N1p1WjE5WjNWClRWK2ZkRzl1RThBUmpKYVZobnJSdWdETWVEOWNaYnRDbkRyRWdaeFYwanAvWHB2TTg3cTEwYXNuWFZMaDRwWlA5eCtGSkNQQis4MS8KV21PK2VwRVZSZU0rLy85WU1xdlNTaXBaTXJ1N1AxZGs5K3R3eHc9PQo8L2RzOlNpZ25hdHVyZVZhbHVlPgo8ZHM6S2V5SW5mbz48ZHM6WDUwOURhdGE+PGRzOlg1MDlDZXJ0aWZpY2F0ZT5NSUlERERDQ0FmU2dBd0lCQWdJR0FUY3dvTzBVTUEwR0NTcUdTSWIzRFFFQkJRVUFNRll4Q3pBSkJnTlZCQVlUQW1Ob01SUXdFZ1lEClZRUUtEQXRVY21sMllXUnBjeUJCUnpFeE1DOEdBMVVFQXd3b2RISnBkbUZrYVhNZ1EwRWdLR3hqYlRBeE1ERXVZMnh2ZFdRdWRISnAKZG1Ga2FYTXVZMjl0S1RBZUZ3MHhNakExTURrd09EQTBNelphRncweU1qQTFNRGt3T0RBME5ERmFNRGd4Q3pBSkJnTlZCQVlUQW1ObwpNUlF3RWdZRFZRUUtEQXRVY21sMllXUnBjeUJCUnpFVE1CRUdBMVVFQXd3S1lYVjBhRk5wWjI1bGNqQ0NBU0l3RFFZSktvWklodmNOCkFRRUJCUUFEZ2dFUEFEQ0NBUW9DZ2dFQkFKbWhjRTVWQ0JjVXNwTFVaa1JkRkxETFk2VFBjR3JmbUJmSkVFblVCUXF5MTZ5UG5LZmIKRVNFWjEzQnFCSVNKcEQ0aEpFRWJXZTFvY1hUSWJTSTNRaVE0Z1huMzdraXYwVmZkZmdmcGRDeW9zazIwbmRsWEsxbnFQcmdrREQzNwpSU0h5YXhYWW1QOExEWDF0UHNzbTJPT3lBdWtVcXgxVnJtRDc3SGttMHBuVGxKWWhlODVGZndiQnpQaGtJM3pWa0lZYmF5eHh2QkQrCldURjRZa0pQeUNRQmxxRUZGQ0I3enpsVUhRTzBTZngyK0Q0b3MyVSthbThjTHkvUUNQT2F0N0prQkZ0TXJOME5ZbWpOaEFBNWkyYkMKWHNnWldGNXM4bmZTU0Y4R0JYVWdTcXJyMVdKaHg2YVJ0V2xJcUl2ZFpGSStYbmttRHhiNjNtUDBDdVRmMnUwQ0F3RUFBVEFOQmdrcQpoa2lHOXcwQkFRVUZBQU9DQVFFQWF2YXdzMkFJM0NrZzhwclYrcFVOSGxlanV1aE5ZbEFlZGVFaUs3Z09jb29ScjEvV0N6cDA4cFdjCmE5ZThQWEhGTGJPeHJYMUNyeXA1bW9Xc3ZwRXFQMkhVbFZqK3d3ZWtnZERXVzFzaTdYZWI5YURyTmFvSnJQelp6ZzNvK2ZmaXRMM1EKeWYvRTcwemllZTladG5ZQk1Zc1ZIbituWHJzZlVsYVdjMzdYQzNPaWZtajc1WGYrZ0J0MmM1RUJLay8yV1cwaXlEZTJhQVpubisyNwpKTkU2bGE5SHVqWWlWS3pzMUpzRm5lNWJwT1dJZDZ5MW8rUnZSOVpsb1hSMjVMM2tMekd1ajBlRzdjaTE1eXBjY1o1NDlZaTdHRlhPClJxZTlKVnZPZERGcllCQnpEaHE4TWlEZG1aemVZbFEzS3NNNlU1SjE5ODVDRXJLa0NpNUdUTm9yanc9PTwvZHM6WDUwOUNlcnRpZmljYXRlPjwvZHM6WDUwOURhdGE+PC9kczpLZXlJbmZvPjwvZHM6U2lnbmF0dXJlPjxzYW1sMjpTdWJqZWN0PjxzYW1sMjpOYW1lSUQ+MTAyPC9zYW1sMjpOYW1lSUQ+PC9zYW1sMjpTdWJqZWN0PjxzYW1sMjpDb25kaXRpb25zIE5vdEJlZm9yZT0iMjAxMi0wOC0zMFQwNjoyMDoyMC4zODlaIiBOb3RPbk9yQWZ0ZXI9IjIwMTItMDgtMzBUMDY6MjU6MjAuMzg5WiIvPjxzYW1sMjpBdXRoblN0YXRlbWVudCBBdXRobkluc3RhbnQ9IjIwMTItMDgtMzBUMDY6MjA6MjAuMzg5WiI+PHNhbWwyOkF1dGhuQ29udGV4dD48c2FtbDI6QXV0aG5Db250ZXh0Q2xhc3NSZWY+dXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6Mi4wOmFjOmNsYXNzZXM6UGFzc3dvcmRQcm90ZWN0ZWRUcmFuc3BvcnQ8L3NhbWwyOkF1dGhuQ29udGV4dENsYXNzUmVmPjwvc2FtbDI6QXV0aG5Db250ZXh0Pjwvc2FtbDI6QXV0aG5TdGF0ZW1lbnQ+PHNhbWwyOkF0dHJpYnV0ZVN0YXRlbWVudD48c2FtbDI6QXR0cmlidXRlIE5hbWU9ImNsaWVudElkIj48c2FtbDI6QXR0cmlidXRlVmFsdWUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSIgeHNpOnR5cGU9InhzOnN0cmluZyI+MTAwPC9zYW1sMjpBdHRyaWJ1dGVWYWx1ZT48L3NhbWwyOkF0dHJpYnV0ZT48c2FtbDI6QXR0cmlidXRlIE5hbWU9InJvbGVzIj48c2FtbDI6QXR0cmlidXRlVmFsdWUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSIgeHNpOnR5cGU9InhzOnN0cmluZyIvPjwvc2FtbDI6QXR0cmlidXRlPjxzYW1sMjpBdHRyaWJ1dGUgTmFtZT0ic2Vzc2lkIj48c2FtbDI6QXR0cmlidXRlVmFsdWUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSIgeHNpOnR5cGU9InhzOnN0cmluZyIvPjwvc2FtbDI6QXR0cmlidXRlPjxzYW1sMjpBdHRyaWJ1dGUgTmFtZT0ibG9naW5JZCI+PHNhbWwyOkF0dHJpYnV0ZVZhbHVlIHhtbG5zOnhzaT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEtaW5zdGFuY2UiIHhzaTp0eXBlPSJ4czpzdHJpbmciLz48L3NhbWwyOkF0dHJpYnV0ZT48c2FtbDI6QXR0cmlidXRlIE5hbWU9InByb2ZpbGVJZCI+PHNhbWwyOkF0dHJpYnV0ZVZhbHVlIHhtbG5zOnhzaT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEtaW5zdGFuY2UiIHhzaTp0eXBlPSJ4czpzdHJpbmciPjEwMjwvc2FtbDI6QXR0cmlidXRlVmFsdWU+PC9zYW1sMjpBdHRyaWJ1dGU+PC9zYW1sMjpBdHRyaWJ1dGVTdGF0ZW1lbnQ+PC9zYW1sMjpBc3NlcnRpb24+PC9zYW1sMnA6UmVzcG9uc2U+
    Is the security filtered ?
    Thanks
    Yves

    Hi Sura,
    The number of thread-count configured in your proxy-scheme is the number of concurrent client request that you proxy servers can handle. Ideally your (thread-count * proxy servers) = (clients * max requests). Also, you need to check that the byte/message backlog on the proxy servers is close to zero.
    Hope this helps!
    Cheers,
    NJ

  • Read only access for bpel console in SOA Suite 10.1.3.5.1(weblogic)

    Hi
    For SOA Suite 10.1.3.5.1 on weblogic, Is there any way to restrict certain users to some pages in bpel console.. e.g. read only access to bpel console.
    I have found articles on web regarding this but they all are for SOA Suite 10.1.3.3 (and 3.4) on Oracle app server. Article provides a hack by using servlet filters.
    How to do a similar thing in SOA Suite 10.1.3.5.1 on weblogic ?
    Can somebody provide step by step instructions?
    Thanks

    Hi James,
    I have already seen this link and several refined versions of it but it wont work for weblogic. For example
    There is no j2ee/oc4j_soa/applications/orabpel/console directory (i looked into home directory as well but could not found orabpel/console dir).
    So question is where to put filter class and how to make changes in web.xml as this file is not present in j2ee/oc4j_soa/applications/orabpel/console/WEB-INF/
    I checked deployments in weblogic admin console and seems BPELConsole is deployed as a module under BPELPM ear.
    Any idea?
    Thanks.

  • WebLogic 11g data source connection pooling failed with IO error:socket read timed out.

    Hi all,
    We encountered IO Error: Socket read timed out( <Received exception while creating connection for pool "DS_1": IO Error: Socket read timed out> ) during the creation of data sources in WebLogic 11g. Manual data source testing seems to indicate intermittent connection and the server seems to take a long time to start up with multiple IO errors. We increased the timeout at the database side but it does not seems to help. The database is 11g (11.2.0.3). The database services and listener are up which does not indicate that the database instance is down.

    This particular error means your database is down and socket is timedout. Or the query takes so long that the reader timedout -- unlikely.
    Also, the general weblogic socket write errors, which you might see sometimes means that the client got disconnected before the server wrote results back. This is harmless

  • Weblogic 11G error = BEA-000449  Closing socket as no data read from it

    In My Weblogic 11G, i am getting Warning msg in my log file saying Closing socket as no data read from it
    ####<Nov 2, 2010 12:10:53 AM IST> <Warning> <Socket> <TradeServer> <TradeServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1288636853607> <BEA-000449> <Closing socket as no data read from it on 95.66.7.15:58,089 during the configured idle timeout of 25 secs>
    ####<Nov 2, 2010 12:10:53 AM IST> <Warning> <Socket> <TradeServer> <TradeServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1288636853607> <BEA-000449> <Closing socket as no data read from it on 95.66.7.15:58,088 during the configured idle timeout of 25 secs>
    ####<Nov 2, 2010 12:21:37 AM IST> <Info> <JDBC> <TradeServer> <TradeServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1288637497701> <BEA-001128> <Connection for pool "IB_JDBC_Data_Source" closed.>
    I have follow the following step
    If you want to follow this solution. Go to Admin console -> Click on Domain->Configuration->Log Filters->create new Log filter.
    I added this line in expression "(MESSAGE !='Closing socket as no data read from it during the configured idle timeout of 5 secs')"
    Go to your server-(for each server you have to set it individually)->Logging->Advanced->Select this log filter for Standard Out or log file.
    My Filter is "(MESSAGE !=Closing socket as no data read from it ')"
    this is not working in weblogic 11G, any one have the solution to stop this msg.
    Edited by: Amar_Shaw on Nov 3, 2010 1:40 PM

    Hi Amar,
    I think you have given the wrong string in the filter, you are getting "*Closing socket as no data read from it on 95.66.7.15:58,089 during the configured idle timeout of 25 secs*" and you have given in the filter "*Closing socket as no data read from it during the configured idle timeout of 5 secs*".
    You can change it and see if that works for you.
    Also the above option is just to suppress the issue which are getting which in this case is fine as its just a warning message, however you can even try to tune few of the follwoing parameters that too would help you to remove this warning message.
    1. Set the parameter -Dweblogic.client.socket.ConnectTimeout=XXX, in the start-up script of the server which you are seeing this issue under JAVA_OPTIONS
    Note: Where "XXX" is the value in ms.
    Example:
    -Dweblogic.client.socket.ConnectTimeout=500
    2. Try tuning the duration time to a higher value from the below Console path
    Server -> Protocols (tab) -> HTTP (sub-tab) -> Duration
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Middleware Magic | Come, Join Us and Experience The Magic…

  • Unable to udpate WSDLFile attribute of BPEL composite via EM11g-FMW console

    Hello Everyone,
    I have a BPEL project (10.1.3.3) that was designed to invoke worklist webservice provided by my peoplesoft application.
    I opened this project via JDeveloper 11.1.1.1.0 and migrated it to 11g format.
    I updated WSDL of my peoplesoft worklist webservice in the BPEL project, compiled and deployed it to my SOA application server (11.1.1.1.0).
    Now I am able to successfully invoke my peoplesoft worklist service from EM11g-Fusion Middleware console and tested it with one of my peoplesoft test environment.
    Now I would like to retest the same deployment with another peoplesoft environment without having to redeploy a new composite from JDeveloper.
    I figured out there is an option to udpate the WSDLFile attribute for any composite deployed onto SOA server via System MBean Browser on SOA console.
    (Via the following navigation on EM11g-Fusion Middleware control console)
    System MBean Browser > Application Defined MBeans > oracle.soa.config > $Soa server name$ > SCAComposite > $Composite Name$ >SCAComposite.SCAReference > $WSDL File name$
    WSDLFile attribute is shown a Read/Write attribute and there is an option to udpate the new WSDL and apply the changes for a composite.
    However in doing so, I am getting an exception as shown below
    javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
    at javax.management.remote.rmi.RMIConnectionImpl_1031_WLStub.setAttribute(Unknown Source)
    at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.setAttribute(RMIConnector.java:921)
    at weblogic.management.remote.wlx.ClientProvider$WLXMBeanServerConnectionWrapper.setAttribute(ClientProvider.java:263)
    at weblogic.management.remote.wlx.ClientProvider$WLXMBeanServerConnectionWrapper.setAttribute(ClientProvider.java:263)
    at oracle.sysman.emas.model.browser.JMXAccess.setAttribuite(JMXAccess.java:1517)
    at oracle.sysman.emas.model.browser.MBeanNodeInfo.setAttribute(MBeanNodeInfo.java:637)
    at oracle.sysman.emas.view.browser.MBeanBrowserViewBean.attributeApply(MBeanBrowserViewBean.java:1024)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
    at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
    at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1245)
    at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:87)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:298)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:91)
    at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:87)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:87)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:298)
    at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:91)
    at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:81)
    at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
    at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:673)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:273)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:165)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:54)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:527)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: javax.management.RuntimeMBeanException
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doSetAttribute(OracleStandardEmitterMBean.java:764)
    at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalSetAttribute(ContextClassLoaderMBeanInterceptor.java:75)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartInterceptor.internalSetAttribute(MBeanRestartInterceptor.java:140)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalSetAttribute(AbstractMBeanSecurityInterceptor.java:142)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.setAttribute(OracleStandardEmitterMBean.java:712)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:762)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:699)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.setAttribute(JMXContextInterceptor.java:234)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.setAttribute(SecurityInterceptor.java:358)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.setAttribute(WLSMBeanServer.java:294)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9$1.run(JMXConnectorSubjectForwarder.java:551)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9.run(JMXConnectorSubjectForwarder.java:549)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.setAttribute(JMXConnectorSubjectForwarder.java:544)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1449)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
    at javax.management.remote.rmi.RMIConnectionImpl.setAttribute(RMIConnectionImpl.java:683)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    ... 2 more
    Caused by: java.lang.UnsupportedOperationException
    at oracle.fabric.management.composite.mbean.Reference.setWSDLFile(Reference.java:392)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doSetAttribute(OracleStandardEmitterMBean.java:756)
    ... 38 more
    Can somebody help me please?
    Thanks
    Ramprasad

    Hello vamseeq,
    I even tried to override the end point address of the composite via service/reference properties page on EM fusion middle ware console.
    (as per instructions mentioned in your previous note)
    It didn't resolve the issue. It still picks up the old end point and neglects the new end point address.
    I even tried to restart the composite as well as the soa server after I updated the new end point address.
    Thanks
    Ramprasad

  • Some questions regarding BPEL 10g to 11g migration.

    Hi All
    I have the following queries,
    1.Is it mandatory to load xsd's , wsdl's , XREF , DVM into MDS ? or is it allright to keep them in file system ? currently we have a number of xsd's and wsdl's inside each of our 10g project > bpel subfolder. If they need to be deployed to MDS , then which files in 11g will need to be modified to use the new 'oramds:/apps/..... ' reference ?
    do they get automatically loaded into MDS when a Composite is deployed on WLS or do they have to be deployed separately using ant-sca-deploy?
    2. Should we modify fault-bindings.xml , DefaultPolicy.xml before or after upgrading the 10g project ? I understand that their references in composite.xml also need changing.
    3.
    a.Is it mandatory to modify the 10g dbadapter.rar contents (convert oc4j-ra.xml to weblogic-ra.xml ) and deploy the rar on 11g ?
    b.or can we manually create data sources,outbound connection pools> jndi factories etc and redeploy the dbadapter on 11g so that its weblogic-ra.xml gets updated with the data sources,jndi that we manually created ?
    want to know if  'a' and 'b' do the same thing ,so mutually exclusive OR both need to be done .
    same question for JMSAdapter.rar, aqadapter.rar
    4. When upgrading BPEL 10g to 11g using Jdeveloper, should all the data sources used by the project be created on Jdeveloper  ?
    5. Is it necessary to copy properties from 10g domain.xml t0 11g bpel-config.xml,soa-infra-config.xml ?
    6. Should external webservices used by BPEL be up and running , while upgrading from 10g to 11g in jdeveloper , OR only during deployment to wls? if they are needed during upgrading how to link to them from jdeveloper ?
    7. Do BPEL 11g projects needs to be deployed on WLS only as a SAR or are any other formats allowed ?
    Thanks in anticipation

    Hi,
    Please find the links where you can find the most of the answers for your questions.
    http://www.slideshare.net/oracle_imc_team/oracle-soa-suite-upgrade-10g-to-11g
    Oracle soa 10g to 11g migration
    Thaknks

  • Error while deployment of  CMP 2.0 bean on weblogic 11g

    Hi,
    I am not able to deploy my CMP 2.0 bean on Weblogic 11g. There are two JVM available in weblogic 11g.
    1) Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
    2) Oracle JRockit(R) (build R28.1.1-14-139783-1.6.0_22-20101206-0241-windows-ia32, compiled mode)
    When we are using "Oracle JRockit(R) (build R28.1.1-14-139783-1.6.0_22-20101206-0241-windows-ia32, compiled mode)" And deploying the CMP bean then we got the Error as below:
    D:\Oracle\Middleware\wlserver_10.3\server\bin>java weblogic.appc -verbose C:\temp\Jproject.ear\DefinitionWizardBean.jar
    Created working directory: C:\DOCUME~1\cxp\LOCALS~1\Temp\1\appcgen_1309496813354_DefinitionWizardBean.jar
    <01-Jul-2011 06:06:57 o'clock BST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element persis
    tence in the deployment descriptor in C:\temp\Jproject.ear\DefinitionWizardBean.jar/META-INF/weblogic-ejb-jar.xml. A vers
    ion attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of
    the Weblogic Server will reject descriptors that do not specify the JEE version.>
    java.lang.NoClassDefFoundError: EntityBean
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
    at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:296)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
    at weblogic.ejb.container.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:510)
    at weblogic.ejb.container.deployer.BeanInfoImpl.<init>(BeanInfoImpl.java:242)
    at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:156)
    at weblogic.ejb.container.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:115)
    at weblogic.ejb.container.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:695)
    at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:558)
    at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:236)
    at weblogic.ejb.container.ejbc.EJBCompiler.getStandAloneDeploymentInfo(EJBCompiler.java:1185)
    at weblogic.ejb.container.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:156)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:439)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)
    at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:316)
    at weblogic.application.compiler.EJBModule.compile(EJBModule.java:128)
    at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
    at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
    at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:29)
    at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
    at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
    at weblogic.application.compiler.Appc.runBody(Appc.java:203)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.application.compiler.Appc.main(Appc.java:262)
    at weblogic.appc.main(appc.java:14)
    EntityBean
    But I use JVM " Java(TM) SE Runtime Environment (build 1.6.0_22-b04) " and deploying CMP bean then i got error as below:
    D:\Oracle\Middleware\wlserver_10.3\server\bin>d:\Oracle\Middleware\jdk160_21\bin\java weblogic.appc -verbose C:\temp\Tr
    ading.ear\DefinitionWizardBean.jar
    Created working directory: C:\DOCUME~1\cxp\LOCALS~1\Temp\1\appcgen_1309496852057_DefinitionWizardBean.jar
    <01-Jul-2011 06:07:35 o'clock BST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element persis
    tence in the deployment descriptor in C:\temp\Jproject.ear\DefinitionWizardBean.jar/META-INF/weblogic-ejb-jar.xml. A vers
    ion attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of
    the Weblogic Server will reject descriptors that do not specify the JEE version.>
    java.lang.ClassNotFoundException: EntityBean
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
    at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:296)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
    at weblogic.ejb.container.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:510)
    at weblogic.ejb.container.deployer.BeanInfoImpl.<init>(BeanInfoImpl.java:242)
    at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:156)
    at weblogic.ejb.container.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:115)
    at weblogic.ejb.container.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:695)
    at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:558)
    at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:236)
    at weblogic.ejb.container.ejbc.EJBCompiler.getStandAloneDeploymentInfo(EJBCompiler.java:1185)
    at weblogic.ejb.container.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:156)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:439)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)
    at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:316)
    at weblogic.application.compiler.EJBModule.compile(EJBModule.java:128)
    at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
    at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
    at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:29)
    at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
    at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
    at weblogic.application.compiler.Appc.runBody(Appc.java:203)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.application.compiler.Appc.main(Appc.java:262)
    at weblogic.appc.main(appc.java:14)
    EntityBean
    Please assist me regarding above error
    Thanks,
    Amritesh
    Edited by: 869636 on 01-Jul-2011 00:49

    What is the jee version you have on that server? are the environment variables correctly set?

  • Develop in JDev 10.1.3.5, test and deploy to Oracle Weblogic 11g

    Hi,
    I have run into some important issues when trying to migrate my Jdev 10.1.3.5 applications to JDev 11g for deployment to the latest Oracle Weblogic Application server version, see threads:
    Thread: migration problems ADF/ Struts 10.1.3 -> 11.1.1.3
    migration problems ADF/ Struts 10.1.3 -> 11.1.1.3
    Thread: ADF/Swing/JClient application migration problem from 10.1.3.5 to 11.1.1.3
    Re: ADF/Swing/JClient application migration problem from 10.1.3.5 to 11.1.1.3
    - so using JDev 10.1.3.5 with deployment to Oracle Weblogic 11g is a must for us.
    Questions:
    1) Is there a way to use Oracle WEBLOGIC 10.3 for debugging inside JDev 10.1.3.5?
    2) Can I develop with JDev 10.1.3.5 + JDK 1.5 and create an ear to deploy to Oracle WEBLOGIC 10.3 Application server with JDK 1.6 64bits?
    3) Which version of ADF should I install on Oracle WEBLOGIC 10.3 to run my 10.1.3.5 application?
    Your help will be appreciated
    Fred

    Is there a way to use Oracle WEBLOGIC 10.3 for debugging inside JDev 10.1.3.5?While you can't replace the embedded OC4J - you can use an external WLS server and do remote debugging on it. http://www.oracle.com/technetwork/developer-tools/jdev/remotedebugwls-086628.html
    From inside JDeveloper you can also deploy directly to the WLS server.
    Can I develop with JDev 10.1.3.5 + JDK 1.5 and create an ear to deploy to Oracle WEBLOGIC 10.3 Application server with JDK 1.6 64bits?Yes you can. Note that so far we haven't officially certified ADF 10.1.3 on WLS 10.3 - but from various customers and testings we think it works ok. We might certify this combination in the future.
    Follow these steps to get the deployment working:
    http://www.oracle.com/technetwork/developer-tools/jdev/deployingwls-091640.html
    Which version of ADF should I install on Oracle WEBLOGIC 10.3 to run my 10.1.3.5 application?You always install the version of ADF that matches the one your application was developed and compiled with.

  • SAML - USer Principal mapped on a SAML attribute - How to do ???

    Dear security experts,
    I have configured on my weblogic platform a Sender vouches SAML profile.
    I am trying to map the UserPrincipal (the one I get from the webServiceContext in my web service) to a SAML attribute (different from the SAML subject).
    I have written a class that implement the interfaces SAMLIdentityAssertionNameMapper and SAMLIdentityAssertionAttributeMapper .
    Here is an overview of the simplified implementation :
    public String mapNameInfo(SAMLNameMapperInfo info, ContextHandler handler) {
    return "user2";
    public void mapAttributeInfo(Collection<SAMLAttributeStatementInfo> attribStmts, ContextHandler contextHandler) {
    Set<Principal> principals = new HashSet<Principal>();
    principals.add(PrincipalFactory.getInstance().createWLSUser("user1"););
    ((SecurityTokenContextHandler)contextHandler).addContextElement(ContextElementDictionary.SAML_ATTRIBUTE_PRINCIPALS, principals);
    After weblogic has loaded my SAML assertion, I can see in the log that my uibject has two User Principal : user1, user2. When I call getUserPrincipal in my webservice, I always get "user1". I need to get "user2".
    Why mapNameInfo() always has the priority ? Is it the good way to implement this mechanism ?
    Thanks for your help.

    Gyan:
    How is that possible? If you import the VOImpl inside EOImpl, the import statement is ok. But how would you use that? There is no findViewObject method? The OADBTransaction class that I can use has only findObject method that one can use and I tried that but wasn't successful. Shouldn't you have to import OAApplicationModule and a host of other classes? Is that even possible?
    I thought about the entity expert approach but I don't have a need to execute any query. I just need to refer to the view attribute from within the EOImpl. That's what I am looking for. If there is a way to refer to a view attribute from within the EOImpl without having to populate that attribute in a session/transaction variable that would be a better solution for me because there may be more attributes that I need from different VOs later on and everytime I need some VO attribute I don't have to create and populate a session/transaction variable.
    Please let me know if it can be done. Can you please elaborate more on your proposal? I really appreciate your time and help. Thanks!
    - Muzammil

  • Migrating from Non-XA driver type to XA Driver in Weblogic 11g

    I have two data sources created in weblogic 11g which were configured in following manner and we are using this configuration since our application started supporting weblogic as application server that's Weblogic 9i.
    Database A: Participates in Global Transaction
    Driver Type: Oracle Thin Driver non-XA
    Support Global Transaction option is disabled for this data source.
    Database B: Participates in Global Transaction
    Driver Type: Oracle Thin Driver non-XA
    Support Global Transaction option is enabled for this data source with One Phase Commit enabled.
    If we use this configuration our application run just fine without any issues.
    Now we have a requirement of adding another data source which participates in global transactions.When I create this data source with following settings,
    Driver Type: Oracle Thin Driver non-XA
    Support Global Transaction option is enabled for this data source with One Phase Commit enabled.
    This results in error (which was expected) "
    "*SQL ERROR: Connection has already been created in this tx context for pool named CMDEMO. Illegal attempt to create connection from another pool: EXPDB*"
    and even when I enable "Support Global Transaction" option with LLR or Emulate Two phase Commit option this results is error,
    "*Database Error: Unexpected exception in Non XA Resource enlistment. Resource=JDBC LLR, pool=EXPDB, table=WL_LLR_ADMINSERVER Cannot enlist more*
    than one Non XA Resource. Attempt to enlist 'WL_JDBC_LLR_POOL.EXPDB' when 'WL_JDBC_LLR_POOL.CMDEMO' is already enlisted."
    Now we are planning to move to "Oracle Thin Driver XA" driver type for all the three data sources.I tested this config. and all global transaction are getting executed perfectly.
    But before we adopt this change,I just wanted to check what all are the limitations of using XA driver or any potential issues that needs to be tested. I explored about this and came to know that XA comes with performance overhead ,frequent database locking with SQL Server driver, and some conflicts with multibyte character sets etc.
    Can someone please provide some input on how to tread ahead and what all things needs to tested.

    How are you using these connection pools in your application?
    Do you have different EJB's, which have the default transaction attribute configured (@TransactionAttribute(TransactionAttributeType.REQUIRED)),
    and are calling each other?
    If one EJB is using connection pool A and the other is using connection pool B, you get in trouble because the transaction is already
    started by EJBone and is propagated to EJBother. In this case you can use @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW).
    Now a new transaction is started for EJBother.
    Some information about XA
    The primary difference is that data sources that support global transactions are JTA transaction-aware.
    Realize that JTA transactions do not necessarily mean XA transactions and two-phase commits (2PC). JTA
    transactions also allow two independently written components that modify the same database to participate
    in a transaction without having to know about each other. Non-XA database transactions require the
    use of a single database connection to provide the proper transactional semantics. If you choose not to
    use the Supports Global Transactions option, you need to write your application components in such
    a way that they get a database connection from the pool at the start of every transaction and pass that
    connection around to every component that participates in the transaction. This is clearly not desirable
    and not even possible with certain types of components (for example, JPA managed entities).
    A data source that supports global transactions will make sure that your components participating in a
    JTA transaction get the proper transactional semantics whether or not they are using XA transactions.
    When not using XA transactions, the data source accomplishes this by associating a database connection
    with a JTA transaction context. Every time a component asks for a database connection using the data
    source that supports global transactions, WebLogic Server will check to see if the current transaction
    already has a database connection, and if so, it will always hand back the same underlying database connection.
    This allows non-XA transactions to maintain the proper database semantic guarantees without
    having to worry about what database connection to use and what the transactional boundaries are for
    the application.

  • Regarding Error in weblogic 11g deployment

    The following Error occured when i deploy my Application in WEBLOGIC 11G Please can anyone help me for resolving this Urgent Issue..
    Error occurred while processing weblogic-rdbms-bean.xml file: ‘fileName‘. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean).EJB Name:com.foursoft.elog.chargeBasis.ejb.cmp.chargeBasisBean.XML processor:'Weblogic.ejb.container.cmp.rdbms.weblogicCmp20Loader_WLS810'

    The following Error occured when i deploy my Application in WEBLOGIC 11G Please can anyone help me for resolving this Urgent Issue..
    Error occurred while processing weblogic-rdbms-bean.xml file: ‘fileName‘. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean).EJB Name:com.foursoft.elog.chargeBasis.ejb.cmp.chargeBasisBean.XML processor:'Weblogic.ejb.container.cmp.rdbms.weblogicCmp20Loader_WLS810'

  • Weblogic 11g Error

    Hello ,
    We are having an Spring based application which was running in weblogic 8.1 , we are migrating to weblogic 11g .
    I created all the configurations in 11g as it was in 8.1 . But I am getting a set of errors as shown below while deploying the application.
    Error while deploying
    •     Substituted for missing class org.springframework.beans.FatalBeanException - Can't resolve reference to bean 'prixcarAdapter' while setting property 'messageHandler' on bean 'ftpAdapter';
    •     nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'prixcarGateway' while setting property 'gateway' on bean 'prixcarAdapter';
    •     nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'jmsPrixcarConnectionFactory' while setting property 'connectionFactory' on bean 'prixcarGateway';
    •     nested exception is: org.springframework.beans.FatalBeanException: afterPropertiesSet() on bean with name 'jmsPrixcarConnectionFactory' threw exception;
    •     nested exception is: javax.naming.NameNotFoundException: Unable to resolve 'PrixcarConnectionFactory'. Resolved ''; remaining name 'PrixcarConnectionFactory'
    Log file error
    The Message-Driven EJB: PRIXCAR_IMPORT_GATEWAY_QUEUE is unable to connect to the JMS destination: jms.PrixcarDamageQueue. The Error was: javax.naming.NameNotFoundException: Unable to resolve 'jms.PrixcarDamageQueue'. Resolved 'jms'; remaining name 'PrixcarDamageQueue' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393) at javax.naming.InitialContext.lookup(InitialContext.java:392) at weblogic.jms.common.CDS$2.run(CDS.java:222) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216) at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1295) at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1092) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java
    In the spring xml I have configured the bean as shown below
    <bean id="jmsPrixcarQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
    <property name="jndiName"><value>jms.PrixcarDamageQueue</value></property>
    <property name="inContainer"><value>false</value></property>
    </bean>
    <bean id="jmsPrixcarConnectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
    <property name="jndiName"><value>jms.PrixcarConnectionFactory</value></property>
    <property name="inContainer"><value>false</value></property>
    </bean>
    And in weblogic-ejb-jar.xml it is as shown below
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
    "http://www.oracle.com/technology/weblogic/weblogic-ejb-jar/1.1/weblogic-ejb-jar.xsd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>PRIXCAR_IMPORT_GATEWAY_QUEUE</ejb-name>
    <message-driven-descriptor>
    <pool>
    <max-beans-in-free-pool>1</max-beans-in-free-pool>
    <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
    </pool>
    <destination-jndi-name>jms.PrixcarDamageQueue</destination-jndi-name>
    </message-driven-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    I configured jms modules in weblogic 11g server console with the jndi names
    jms.PrixcarDamageQueue
    jms.PrixcarConnectionFactory
    Please let us know the reason for this error also the doctype for 11g in weblogic-ejb-jar.xml above.
    Edited by: user13295341 on Jun 15, 2010 5:21 AM

    Jay and Maxence , I tried what you guys said by removing the jms. and using only PrixcarDamageQueue and PrixcarConnectionFactory but still I am getting an error like Namenotfound as shown below,
    The Message-Driven EJB: PRIXCAR_IMPORT_GATEWAY_QUEUE is unable to connect to the JMS destination: PrixcarDamageQueue. The Error was: javax.naming.NameNotFoundException: Unable to resolve 'PrixcarDamageQueue'. Resolved ''; remaining name 'PrixcarDamageQueue' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393) at javax.naming.InitialContext.lookup(InitialContext.java:392) at weblogic.jms.common.CDS$2.run(CDS.java:222) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216) at
    My doubt is will queue be displayed in JNDI tree ?? I mean there is a JNDI tree in weblogic admin screen and I am getting only the PrixcarConnectionFactory in that and not the PrixcarDamageQueue , may be thats why its showing "unable to connect to the JMS ???" Please advice.....
    I changed both the xml's and the JNDI names in the admin screen.

  • Oracle Portal returns 500 error running under Weblogic 11g server

    I've got Oracle Portal set up under Weblogic 11g.
    SSO running, talking to OID 11g, also running under the same Weblogic 11g server. Tested SSO, it is working well.
    After the install (no errors or issue on install), I go to http://<server>:8090/portal/pls/portal and geta Error 500 - Internal Server Error.
    I traced down the problem to OHS - in ohs1.log:
    [2009-08-04T10:09:15.0512-05:00] [OHS] [ERROR:32] [OHS-9999] [odl_log.c] [host_id: <server>] [host_addr: 127.0.0.1] [tid: 1320139072] [user: oracle] [ecid: 004S594zs25Fw000jzwkno0002740001NK] [rid: 0] [VirtualHost: main] Request Failed for : /portal/pls/portal, Resp Code : [500]
    [2009-08-04T10:09:15.1212-05:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: <server> [host_addr: 127.0.0.1] [tid: 1330628928] [user: oracle] [ecid: 004S5953tHhFw000jzwkno0002740001NL] [rid: 0] [VirtualHost: main] File does not exist: /opt/oracle/Middleware/asinst_2/config/OHS/ohs1/htdocs/favicon.ico
    So the problem is favicon.ico is missing, which I confirmed. Does this mean a bad deployment of an .EAR file? What should I do?

    Yes, it seems you are correct....this is from WLS_PORTAL-diagnostic.log
    Looks like the real problem is ERROR: Failed to load C shared library in RepositoryGateway after calling RepositoryGatewayJNI.load:
    [2009-08-05T08:32:08.333-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBekbL6Fw000jzwkno1AU3uT000001,0] [APP: portal] Portal Servlet Context Listener destroy started
    [2009-08-05T08:34:14.191-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] Initializing Portal Servlet Context Listener
    [2009-08-05T08:34:14.534-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] Creating Repository Service
    [2009-08-05T08:34:14.540-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] In RepositoryService.constructor(<3 args>), PLSQL_CONFIG_FILE = /opt/oracle/Middleware/user_projects/domains/pfrd/servers/WLS_PORTAL/stage/portal/portal/configuration/portal_plsql.conf[[args: serverInfo=WebLogic Server 10.3.1.0 Thu Jun 11 00:26:56 EDT 2009 1227385 , contextRoot=/portal, logMode=error]]
    [2009-08-05T08:34:14.578-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] In RepositoryServiceConfig, DAD_CONFIG_FILE = /opt/oracle/Middleware/user_projects/domains/pfrd/servers/WLS_PORTAL/stage/portal/portal/configuration/portal_dads.conf, CACHE_CONFIG_FILE = /opt/oracle/Middleware/user_projects/domains/pfrd/servers/WLS_PORTAL/stage/portal/portal/configuration/portal_cache.conf
    [2009-08-05T08:34:14.582-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] In RepositoryServiceConfig, dadRetriever = oracle.webdb.repository.service.DadFileConfigRetriever@26d4835, cacheRetriever = [email protected]7
    [2009-08-05T08:34:14.622-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] Calling RepositoryGatewayJNI.load ...
    **ERROR STARTS HERE
    [2009-08-05T08:34:14.637-05:00] [WLS_PORTAL] [ERROR] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] ERROR: Failed to load C shared library in RepositoryGateway!
    [2009-08-05T08:34:14.665-05:00] [WLS_PORTAL] [ERROR] [] [oracle.portal] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId:
    <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] ERROR: Repository Service creation failed. Please check previous log entries for possible cause.
    [2009-08-05T08:34:14.911-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal.config.modplsql.mbeans.DadManagerMXBeanImpl] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] **** Inside Reloaded, NOW Register mbean = : /pls/portal
    [2009-08-05T08:34:14.915-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portal.config.modplsql.mbeans.DadManagerMXBeanImpl] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IBel63LFw000jzwkno1AUOdM000000,0] [APP: portal] **** Inside RegisterBean, global beanName = : oracle.portal.config:subtype=DADs,name=/pls/portal,type=PortalConfig,Application=portal
    [2009-08-05T08:36:16.717-05:00] [WLS_PORTAL] [NOTIFICATION] [] [oracle.portlet.server.wsrp.mbean.WSRPTransientConfigMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000IBelXi4Fw000jzwkno1ARF2b0004Zm,1:5002] [APP: wsrp-tools] Found WLS AppDeployment MBean com.bea:Name=portalTools#11.1.1.1.0,Type=AppDeployment

  • How to use external Java API in Java Embedd inside BPEL

    How to use external classes inside the BPEL in Java Embed Activity ? Any sample code availble ? Like i want to use log4j API inside BPEL.

    No you dont have to change your startManagedServer.cmd/.sh everytime you need to have a Java Embedding activity. You only need it in case of using Log4J. As log4j requires a configuration xml viz log4j.debug.xml and log4j.dtd you need to let the soa managed server know about it. The best way to load this configuration files is using the JAVA_OPTIONS command during server startup.
    Hope the explanation helps.

Maybe you are looking for