JHeadstart release for Weblogic 10.3.3

We've had licenses for JHeadstart since November of 2009, but because our web hosting group only supported Weblogic 10.3.2, we were unable to deploy until the JHeadstart 11.1.1.2.29 version was released in April. But, now they are immediately moving to Weblogic 10.3.3, which requires JDeveloper 11.1.1.3.0, and because the production JHeadstart 11g is not compatible, we again will be unable to deploy a JHeadstart application.
Can ADF for 11.1.1.2 be installed under Weblogic 10.3.3 (though it is not officially supported), along with ADF 11.1.1.3.0 that would allow the production JHeadstart 11g to be deployed?
When do you anticipate a JDeveloper 11.1.1.3.0 compatible Jheadstart becoming available?

That is good news. I will try to add JHeadstart 11.1.1.2 to JDeveloper 11.1.3.3; thought I had tried that first and JHeadstart failed to install, but must have missed some installation instruction.

Similar Messages

  • BPM for Weblogic configuration is failed

    1, I install BPM for Weblogic.
    2, I create a domain for weblogic using config tool and start it.
    3, I create a new directory.
    However, the configuration is failed.
    The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
    The log is as follows:
    For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
    changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
    The edit lock associated with this edit session is released
    once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) 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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) 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 weblogic.WLST.main(WLST.java:29)
    Exiting WebLogic Scripting Tool.
    <Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
    Do you want to cancel this wizard?

    Hi,
    Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
    -------------------log message-------------------------------
    TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
    TO_MSG
    TO_MSG Your environment has been set.
    TO_MSG
    TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
    TO_MSG
    TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
    TO_MSG
    TO_MSG Welcome to WebLogic Server Administration Scripting Shell
    TO_MSG
    TO_MSG Type help() for help on available commands
    TO_MSG
    TO_MSG Starting server BPMServer
    TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
    TO_MSG Starting weblogic server ...
    TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
    TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ26￥ﾈﾆ58￧ﾧﾒ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00￧ﾧﾒ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00￧ﾧﾒ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
    TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ12￧ﾧﾒ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ13￧ﾧﾒ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
    TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15￧ﾧﾒ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ16￧ﾧﾒ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
    TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ24￧ﾧﾒ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    TO_MSG Server started successfully.
    TO_MSG Started Server. Trying to connect to the server ...
    TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
    TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
    TO_MSG
    TO_MSG Warning: An insecure protocol was used to connect to the
    TO_MSG server. To ensure on-the-wire security, the SSL port or
    TO_MSG Admin port should be used instead.
    TO_MSG
    TO_MSG Location changed to edit tree. This is a writable tree with
    TO_MSG DomainMBean as the root. To make changes you will need to start
    TO_MSG an edit session via startEdit().
    TO_MSG
    TO_MSG For more help, use help(edit)
    TO_MSG
    TO_MSG Starting an edit session ...
    TO_MSG Started edit session, please be sure to save and activate your
    TO_MSG changes once you are done.
    TO_MSG creating mbean of type JMSServer ...
    TO_MSG creating mbean of type JMSSystemResource ...
    TO_MSG creating mbean of type SubDeployment ...
    TO_MSG creating mbean of type Queue ...
    TO_MSG creating mbean of type Topic ...
    TO_MSG creating mbean of type ConnectionFactory ...
    TO_MSG creating mbean of type ConnectionFactory ...
    TO_MSG creating mbean of type Server ...
    TO_MSG creating mbean of type JDBCSystemResource ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type JDBCSystemResource ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Realm ...
    TO_MSG creating mbean of type RoleMapper ...
    TO_MSG creating mbean of type CredentialMapper ...
    TO_MSG creating mbean of type CertPathProvider ...
    TO_MSG creating mbean of type Authorizer ...
    TO_MSG creating mbean of type Adjudicator ...
    TO_MSG creating mbean of type AuthenticationProvider ...
    TO_MSG creating mbean of type AuthenticationProvider ...
    TO_MSG setting attributes for mbean type JMSServer
    TO_MSG setting attributes for mbean type JMSSystemResource
    TO_MSG setting attributes for mbean type SubDeployment
    TO_MSG setting attributes for mbean type Queue
    TO_MSG setting attributes for mbean type Topic
    TO_MSG setting attributes for mbean type JMSConnectionFactory
    TO_MSG setting attributes for mbean type JMSConnectionFactory
    TO_MSG setting attributes for mbean type Server
    TO_MSG setting attributes for mbean type JDBCSystemResource
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
    TO_MSG setting attributes for mbean type JDBCDriverParams
    TO_MSG setting attributes for mbean type JDBCDataSource
    TO_MSG setting attributes for mbean type DefaultIdentityAsserter
    TO_MSG setting attributes for mbean type SecurityConfiguration
    TO_MSG setting attributes for mbean type SecurityParams
    TO_MSG setting attributes for mbean type EmbeddedLDAP
    TO_MSG setting attributes for mbean type SecurityParams
    TO_MSG setting attributes for mbean type Domain
    TO_MSG setting attributes for mbean type JDBCDataSource
    TO_MSG setting attributes for mbean type JDBCXAParams
    TO_MSG setting attributes for mbean type JDBCDataSourceParams
    TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
    TO_MSG setting attributes for mbean type JDBCDriverParams
    TO_MSG setting attributes for mbean type JDBCDataSourceParams
    TO_MSG setting attributes for mbean type JDBCSystemResource
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG Saving all your changes ...
    TO_MSG Saved all your changes successfully.
    TO_MSG Your edit session is not stopped, you can continue your edits.
    TO_MSG Activating all your changes, this may take a while ...
    TO_MSG The edit lock associated with this edit session is released
    TO_MSG once the activation is completed.
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG
    TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
    TO_MSG that require server re-start:
    TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
    TO_MSG Attributes changed : RotateLogOnStartup
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
    TO_MSG Attributes changed : ListenAddress
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
    TO_MSG Attributes changed : RotateLogOnStartup
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
    TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
    TO_MSG Attributes changed : RotateLogOnStartup
    TO_MSG
    TO_MSG Activation completed
    TO_MSG Creating a user ...
    TO_MSG
    TO_MSG Created user successfully
    TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ01￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ08￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
    TO_MSG .................Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ29￥ﾈﾆ48￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ30￥ﾈﾆ45￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ00￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ31￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
    TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48￧ﾧﾒ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48￧ﾧﾒ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
    TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
    TO_MSG WLST-WLS-1249792014056:      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
    TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
    TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.open(Native Method)
    TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:117)
    TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:133)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
    TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
    TO_MSG WLST-WLS-1249792014056: >
    TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
    TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.open(Native Method)
    TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.Fil

  • Configuration is failed - BPM for Weblogic 10.3.1

    1, I install BPM for Weblogic.
    2, I create a domain for weblogic using config tool and start it.
    3, I create a new directory.
    However, the configuration is failed.
    The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
    The log is as follows:
    For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
    changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
    The edit lock associated with this edit session is released
    once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear], to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 [archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear], to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.      at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)      at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)      at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536)      at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429)      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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)      at org.python.core.PyMethod.__call__(PyMethod.java:96)      at org.python.core.PyObject.__call__(PyObject.java:248)      at org.python.core.PyObject.invoke(PyObject.java:2016)      at org.python.pycode._pyx17.deploy$8(<iostream>:223)      at org.python.pycode._pyx17.call_function(<iostream>)      at org.python.core.PyTableCode.call(PyTableCode.java:208)      at org.python.core.PyTableCode.call(PyTableCode.java:404)      at org.python.core.PyFunction.__call__(PyFunction.java:184)      at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623)      at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py)      at org.python.core.PyTableCode.call(PyTableCode.java:208)      at org.python.core.PyTableCode.call(PyTableCode.java:256)      at org.python.core.PyFunction.__call__(PyFunction.java:169)      at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738)      at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py)      at org.python.core.PyTableCode.call(PyTableCode.java:208)      at org.python.core.PyCode.call(PyCode.java:14)      at org.python.core.Py.runCode(Py.java:1135)      at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)      at weblogic.management.scripting.WLST.main(WLST.java:129)      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 weblogic.WLST.main(WLST.java:29)
    Exiting WebLogic Scripting Tool.
    <Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
    Do you want to cancel this wizard?

    Hi Ye,
    I noticed this afternoon that Oracle's refering to Oracle WebLogic 10.3.1 as "Oracle WebLogic 11g".
    Know this comes as no surprise to you, but when I tried to install Oracle BPM 10gR3 Enterprise on WebLogic 11g (WebLogic 10.3.1) this afternoon it failed. A friend pointed out to me that Oracle WebLogic 11g does not support the DataDirect JDBC driver. Since Oracle BPM Enterprise 10gR3 uses this driver to connect to both its Engine database and Directory Service databases, he's thinking this might be the cause of our problem.
    It would be worth verifying this with Support. Here's what I think they'll point you to. The Oracle BPM 10gR3 release notes(http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/relnotes/release_notes_OracleBPM10gR3.htm#N65589) indicate that the only WebLogic application servers supported are Oracle WebLogic 10.3 (10gR3), Oracle WebLogic 10.0 MP1.
    Again, talk to Support, but I don't think there's a workaround. The only thing I think you can do is to uninstall WebLogic 10.3.1 and then install WebLogic 10.3 if you want to install Oracle BPM 10gR3 Enterprise on it.
    Dan

  • Workshop for WebLogic and Solaris

    I know there is no support for this currently. Is this something which may change down the road?
    I am one of a few people in our company that would like to be able to do development on our solaris x86 boxes, but end up having to remote desktop into a development windows server in order to be able to do so.
    another option/question, would it be possible to just get the weblogic plugins - assuming we have support - in order to put them into eclipse ourselves since we can get eclipse for solaris x86. It isn't that we NEED the plugins, but it does make some of the work much nicer/easier.
    thanks
    t-

    I'm not aware of planned Solaris support, but will check on that.
    The next release of Workshop for WebLogic will allow you to use an existing Eclipse rather than requiring you to use the Eclipse it installs.
    -Chris

  • Oracle JHeadstart 10g for ADF - Evaluation Copy Available

    All,
    The evaluation copy of the new JHeadstart release 10.1.2 for ADF is now available. With the evaluation copy you are allowed to build a prototype only. You can dowload this evaluation copy on the JHeadstart Product Center.
    http://www.oracle.com/technology/consulting/9iservices/files/jdg_rference1012.html
    If you are building applications that you plan to take in production you will have to acquire the right license. Please ask your Oracle Consulting representative for more details or send an e-mail to [email protected]
    Regards,
    Ton van Kooten
    Oracle JHeadstart Team

    Boris,
    we are in the process of externalizing the 10.1.2 release. Next week we expect to be able to announce it. Please be patient and check in the coming days.
    Regards,
    Ton
    JHeadstart Team

  • SimpleCallbackHandler no longer in weblogic.jar for WebLogic 10.3g

    I was using the weblogic.security.SimpleCallbackHandler in WebLogic 9.2 to authenticate users. I looked at the documentation for 10.3g and it still mentions this class is available, however it is not in the weblogic.jar file nor in the javadocs. Here is the URL where I was looking. http://e-docs.bea.com/wls/docs103/security/thin_client.html#wp1035574.
    The only CallbackHandler in the 10.3g release seems to be the weblogic.security.URLCallbackHandler class. I tried replacing the SimpleCallbackHandler with this class. When I put the weblogic.jar in my classpath and build, I get the following error.
    class file for weblogic.security.acl.internal.AuthenticatedSubject not found
    ServletAuthentication.runAs(mySubject, request);
    Indeed, this class is not in the weblogic.jar file. Both SimpleCallbackHandler and AuthenticatedSubject were in the weblogic.jar for WebLogic 9.2
    <code>
    import javax.security.auth.Subject;
    import weblogic.security.SimpleCallbackHandler;
    import weblogic.security.services.Authentication;
    public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws Exception {
    LoginForm loginForm = (LoginForm) form;
    Subject subject = Authentication.login(new SimpleCallbackHandler(loginForm.getUsername(), loginForm.getPassword().getBytes()));
    weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
    <./code>
    Why were these removed and not deprecated???

    SimpleCallbackHandler does not exist in weblogic.jar. Used the following code to get around this. WebLogic documentation offers this as an alternative to using SimpleCallbackHandler.
    Subject subject = Authentication.login(new URLCallbackHandler(uid, pwd));
    weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
    This code agrees with the snippet provided in WebLogic documentation
    Project does not compile with the following error:
    Project: C:\apps\11g\PrismMainApp\ViewController\ViewController.jpr
    C:\apps\11g\PrismMainApp\ViewController\src\adr\prismmain\view\managed\PrismLogin.java
    Error(70,28): cannot access weblogic.security.acl.internal.AuthenticatedSubject

  • Preview Release of WebLogic Portal 9 and Workshop 9

    I would like to get my hands on a developer preview release of WebLogic Portal 9 and Workshop 9. I can't seem to find it online so I'm hoping someone can point me in the right direction. We're currently evaluating portal products and I would hate to decide against BEA based on the lack of availability of the forthcoming version.
    Anybody know where a developer release of either of these two products can be found?

    The Technology Preview for WLP 9.x and WLW 9.x will be available in early December. Please contact your BEA account team to let them know that you are interested.
    At present the plan is to have a GroupSpace community site for use by all customers participating in the Technology Preview. A BEA technical field staff member (SE, PS, etc.) assigned to your account will use this site to send you an invitation, and when you join you will have access to the installation. Questions, discussions, etc. for the Technology Preview will all go through the GroupSpace site. If you don't know who your BEA technical account member(s) are, you should find out as they will be the key to obtaining the Technology Preview.
    If you can't wait for the Technology Preview, please ask your BEA acount team to contact myself or others in Product Management. We'll be happy to go over the product features, show you demos from current builds, etc.
    Thanks,
    Skip Sauls
    Senior Product Manager, WebLogic Portal

  • Jolt for weblogic (5.1) and encryption ?

    Hi.
    I'm trying to use encryption between Jolt for Weblogic clients and Jolt servers
    (JSL/JSH), but I can't get it work.
    The JSL's "-Z" option is set to 40, and it boots without errors. Tuxedo 6.5 Security
    add-on is installed. Everything works fine without the "-Z" option.
    However, the Jolt client, while connecting to JSL, always catches a SessionException
    with the following message:
    Reason:NwHdlr: open: J_DH Bad Reply\nbea.jolt.JoltException: NwHdlr: open: J_DH
    Bad Reply
    and nothing is logged on the server side...
    Is there something to configure or install on client (i.e. weblogic) side ? Has
    anyone already succeeded in using Jolt's encryption ?
    Any help welcome...
    PS: I have posted this question on several groups, as far as it seems that nobody
    knows about Jolt's encryption...

    Hi Mathieu,
    You may need to install a Tuxedo rolling patch. You need at least:
    Tuxedo 6.4 Rolling Patch level 210,
    Tuxedo 6.5 rolling patch level 47,
    see the following CR:
    CR016914 (Jolt only) DiffieHellman Key exchange for Jolt
    Also, you may need to have WLS SP 10 installed in order to use
    40-bit encryption. See CR 45413 with additional information in the Service
    Pack release notes.
    CR 45413: Added an international version of Jolt client which is required to talk
    with International Tuxedo.
    Scott Lynch
    Michael Young <[email protected]> wrote:
    Hi.
    Try posting this to one or both of the following newsgroups:
    weblogic.developer.interest.general or tuxedo.general. If you get no
    response then I
    suggest you open a case with BEA support.
    Thanks,
    Michael
    Mathieu Chauvin wrote:
    Hi.
    I'm trying to use encryption between Jolt for Weblogic clients andJolt servers
    (JSL/JSH), but I can't get it work.
    The JSL's "-Z" option is set to 40, and it boots without errors. Tuxedo6.5 Security
    add-on is installed. Everything works fine without the "-Z" option.
    However, the Jolt client, while connecting to JSL, always catches aSessionException
    with the following message:
    Reason:NwHdlr: open: J_DH Bad Reply\nbea.jolt.JoltException: NwHdlr:open: J_DH
    Bad Reply
    and nothing is logged on the server side...
    Is there something to configure or install on client (i.e. weblogic)side ? Has
    anyone already succeeded in using Jolt's encryption ?
    Any help welcome...
    PS: I have posted this question on several groups, as far as it seemsthat nobody
    knows about Jolt's encryption...--
    Developer Relations Engineer
    BEA Support

  • Writing a plugin for Weblogic

    Hi,
    Is it possible to add a mechanism to Weblogic which would intercept
    EJB lookups and requests (on a per bean and per method basis), and
    perform custom access control logic? This mechanism should be seamless
    and transparent to client code so that existing apps would not have to
    be modified. In effect, I would like to create a plugin for Weblogic
    in much the same way as you can create a plugin for web servers like
    Apache, IIS, etc.
    Alternatively, if this effect could be achieved simply through
    configuration changes, then even better. Customized security realms do
    not exactly fit what I want to do because they have to be manually
    created per client, and I would also like to perform additional logic
    besides access control.
    Thanks in advance,
    Steve Au

    Wouldn't EJB clients have to be rewritten to access this proxy bean instead? What
    would prevent clients from accessing the "secured" EJBs directly?
    Thanks.
    "Michael Girdley" <----> wrote:
    We do not offer such an interface natively to write your own security
    interceptors. But, I can imagine someone writing a session bean proxy
    that
    intercept all EJB calls in this way before forwarding them along.
    We plan to offer such functionality in a future release without requiring
    any kludges.
    Michael Girdley
    BEA Systems
    Learning WebLogic? http://learnweblogic.com
    Buy the only book covering J2EE & WebLogic 6:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/103-9227026-
    4636613
    "Steve Au" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    Is it possible to add a mechanism to Weblogic which would intercept
    EJB lookups and requests (on a per bean and per method basis), and
    perform custom access control logic? This mechanism should be seamless
    and transparent to client code so that existing apps would not haveto
    be modified. In effect, I would like to create a plugin for Weblogic
    in much the same way as you can create a plugin for web servers like
    Apache, IIS, etc.
    Alternatively, if this effect could be achieved simply through
    configuration changes, then even better. Customized security realmsdo
    not exactly fit what I want to do because they have to be manually
    created per client, and I would also like to perform additional logic
    besides access control.
    Thanks in advance,
    Steve Au

  • WSRP Support Kit for WebLogic Platform 8.1 SP2

    The WSRP Support Kit for WebLogic Platform SP2 has just been released at
    http://dev2dev.bea.com/products/wlportal81/articles/wsrp_support_kit.jsp.
    Please note that this is a preview release, and requires WebLogic
    Platform 8.1 SP2.
    Regards,
    Subbu

    There is a release planned for mid Summer, but it is too early to confirm.
    In case you must add WSRP support to apps in platform domain, you can do
    so manually, and here are the steps.
    - Create a platform domain before installing WSRP Support Kit.
    - Create a portal domain after installing WSRP Support Kit.
    - Replace <Security> element in config.xml in the platform domain with
    the one from portal domain.
    - Add wsrp-common.jar file to the system classpath for the platform domain.
    Let me know if this helps.
    Subbu
    Murtaza Sonaseth said the following on 01/07/2004 02:51 PM:
    Is there an planned final release date for WSRP or at least a rough timeframe?
    Thanks,
    M Sonaseth.

  • When JHeadstart release to support Struts?

    Guys can I ask again for another update.
    I've been chasing since Feb and have been told it will be released end of March, then May, then June.
    It's now approaching mid July and I don't really see the value of the Supplementary option at this stage.
    Given that JD 9.0.4 and 9.0.5 are imminent can we expect to wait 6-12 months post their release to get a compatible JHeadstart release?
    Regards
    Mal

    We are truly sorry to keep you waiting.
    One of the reasons we delayed the new release a couple of times, was because we want it to fully support Struts. The latest date given (end August) still seems feasible.
    Jan Kettenis

  • Supporting JDK for weblogic 12.1.2.0

    Hi,
           We have installed weblogic 12.1.2.0 with RHEL 5.6 and oracle hotspot JDK 1.7_15.
           We are running the server side applications in "Production Mode", my doubt is whether the above mentioned JDK is recommended to run the server in Production Mode.  I didn't found any  
           suitable JRockit JDK for this weblogic 12.1.2.0 release.  Please provide any information regarding this. 
    Regards,
    Ananda Krishnan S

    Hello Ananda,
    Though MOS Certification tab shows that JRockit 6u33 R28.2.4+ is certified to run with WLS 12c(12.1.2.0) on RedHat Linux5, I do NOT encourage you to go for that in your PROD environment for the following notes:
    1. Oracle JRockit Not Supported For Execution of WebLogic Server 12.1.2 Server Applications:
    http://docs.oracle.com/middleware/1212/wls/WLSRN/issues.htm#BCFBDIEG
    2. JRF Domains Do Not Support JRockit in 12.1.2:
    http://docs.oracle.com/middleware/1212/core/RNINF/upgrade.htm
    3. The same info can be verified downloading the following file inclided in "Oracle Fusion Middleware Supported System Configurations" OTN page:
    http://www.oracle.com/technetwork/middleware/fusion-middleware/documentation/fmw-1212certmatrix-1970069.xls
    All the above notes tells/clarifies the same info:
    In Oracle Fusion Middleware 12.1.2. JRockit is supported only for WebLogic Server client-side applications, but not for execution of WLS server applications.
    Hope that helps,
    Murad

  • Workshop IDE for WebLogic Platform - JSF Portlet Development

    Hello,
    I am trying to develop JSF based portlets using BEA Workshop for WebLogic Platform IDE. The capabilities of the IDE in terms of JSF is like a simple text editor. Since the IDE is eclipse based, I wanted to to use some Third Party Plugin for JSF development.
    I evaluated the following:
    1. Workshop Studio for JSF
    2. MyEclipse PlugIn for JSF
    Problem 1:
    Workshop Studio for JSF is a separate product and cannot be installed as an plugin over the Workshop IDE.
    Is this acheivable?
    Problem 2:
    I created a Portal application Workspace through Workshop for Platform and opened the same using Workshop Studio for JSF. It crashed saying some runtime exceptions.
    Problem 3:
    MyEclipse PlugIn for JSF doesnt integrate properly with Workshop IDE. The Faces navigational flow view is not working properly.
    Questions:
    1. What is BEA's recommendation for JSF development?
    2. Can you guide me how other developers are using the IDE for JSF development?
    Thanks and regards,
    Pazhanikanthan. P

    Hi Pazhanikanthan,
    Unfortunately, in the current release the JSF features cannot be used to create JSF portlets.
    Please check the following URL for additional information on JSF portlet creation
    http://e-docs.bea.com/wlp/docs92/portlets/building.html#wp1062147
    If you are planning on building JSF web applications, you can always evaluate and purchase a copy of Workshop for JSF or Workshop Studio.
    if you are planning on building JSF based pportlets, you will need to sue the tooling provided by Workshop for WebLogic 9.2
    Applications built in Workshop for WebLogic cannot be imported into Workshop Studio. On the other hand, you can always create a webapp in Workshop Studio,a nd then import it into Workshop for WebLogic as a component.
    hope this helps.
    cheers
    Raj
    If you have additional questions specific to portlet development, please post to the portal newsgroup at http://newsgroups.bea.com/bea/forum.jspa?forumID=2044

  • Struts support in Oracle Workshop for WebLogic Version 10.3

    Hello:
    Which version of Struts does Oracle Workshop for WebLogic Version 10.3 support?
    I can't get it in the Release Notes or in the tutorial http://download.oracle.com/docs/cd/E13224_01/wlw/docs103/guide/webapplications/struts/strutsTutorial/0.intro.html.
    Thanks for any input.

    Hi,
    Currently workshop 10.3 facets will only provide struts 1.2 / 1.1 / 1.0
    But we can use latest version of the struts like 1.3 also as we need to add those jar files under windows preference >> weblogic shared library.
    But later we can change the Facets file and try to work with newer version of struts.
    Let me know if you need any further help on this issue.
    Regards,
    Kal.

  • Service packs for Weblogic 6.1 with J2EE 1.3 disabled

    We are planning to migrate to Weblogic 6.1 from 5.1.
    Is BEA supporting 6.1 release with J2EE 1.3 disabled? I see that 6.1
    with J2EE 1.3 is at sp4, whereas there is no service pack for 6.1 with
    J2EE 1.3 disabled.
    If BEA is not supporting 6.1 release with J2EE 1.3 disabled, then we
    have to go to 6.1 with J2EE 1.3.

    Rakesh Kalra wrote:
    We are planning to migrate to Weblogic 6.1 from 5.1.
    Is BEA supporting 6.1 release with J2EE 1.3 disabled? I see that 6.1
    with J2EE 1.3 is at sp4, whereas there is no service pack for 6.1 with
    J2EE 1.3 disabled.
    If BEA is not supporting 6.1 release with J2EE 1.3 disabled, then we
    have to go to 6.1 with J2EE 1.3.Why is 1.3 a problem for you? In any case, there must be a way to do what you want.
    Looking at the Service Packs, the last couple sentences of the description discuss it.
    Maybe you would just need help with the WLS Start scripts. Or you would need to start
    with a base product that has 1.3 disabled and take it from there. I'm sure someone
    could find the files for you, they are just not out in the open.
    Best Wishes,
    Wayne Scott
    http://commerce.bea.com/SoftwareProductDetailWLS?SWName=WebLogic+Server+Service+Pack&SWVersion=Version+6.1&SWPlatform=Service+Pack+2+for+UNIX
    Evaluation Product Details
    Service Pack 2 for WebLogic Server 6.1 (UNIX platforms)
    File Size
    47,543,493 Bytes
    Description
    This service pack contains files that resolve some issues pertaining to the released
    product. A detailed list of these issues is provided in the release notes.
    The Service Pack upgrade installers for WebLogic Server 6.1 will update all existing
    WebLogic installations to run with J2EE 1.3 features enabled when starting the server
    with the startscripts provided within the WLS distribution. With J2EE 1.3 features
    enabled, WebLogic Server will still inform you whenever an application is deployed that
    uses J2EE 1.3 features. If you desire to disable J2EE 1.3 features and you had
    originally installed WebLogic Server 6.1 with J2EE 1.3 feature disabled, you can restore
    the WebLogic Start scripts from the backups created during the Service Pack
    installation. Go to "Viewing and Recovering Files Replaced or Deleted by a Service Pack
    Installation" on our Installing BEA WebLogic Server Page.

Maybe you are looking for