Configuring BPM in Clustered/Managed Server

Hi,
I have completed the deployment for Oracle BPM and SB installation in the WebLogic Server successfully which includes BPM Engine, BPM workspace and all with the configuration wizard.
Now i am looking for reference material to configure the BPM to the Managed Server.
Have went through the BPM congfiguration guide, but cannot get the information on what i am looking for.BTW this is the first time i am heading to deploy in the managed server.
Kindly share how can i proceed to deploy in the managed server.
Thanks and Regards
Jeevan

You can try the 10g documentation about configuring on a J2EE environment.
[http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html|http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html]
Or the 6.0 documentation may describe it a bit better.
[http://edocs.bea.com/albsi/docs60/config_wls/index.html|http://edocs.bea.com/albsi/docs60/config_wls/index.html]
Hope that was what you were looking for!
-Kevin

Similar Messages

Query regarding the Node manager configuration(WLS and OAM Managed server)

Query regarding the Node manager configuration(WLS and OAM Managed server):
1) In the nodemanager.properties I have added the ListenAddress:myMachineName and ListenPort: 5556
My setup : One physical Linux machine(myMachineName) has : WLS admin server, managed server(OAM 11G) and nodemanager.No clustered environment.
2) nodemanager.log has the following exception when I start the oam_server1 using EM(Enterprise Manager11g):
Mar 23 2012 1:39:55 AM> <SEVERE> <Fatal error in node manager server>
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.<init>(ServerSocket.java:202)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:125)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
Default port on which node manager listen for requests is localhost:5556.I have changed it to point to my machine. The port should be of WLS admin server or it should be the managed server port?
3) I have started the NodeManager using the startNodeManager.sh script.
4) The admin server port is 7001 and the oam managed server port is 14100.
Any inputs on what might be wrong in the setup will be helpful.Thanks !

By using netstat -anp|grep 5556 you can check which process on your machine is using the 5556 port.

Error configuring and starting Managed Server in WebLogic 10.3

Hi,
I am able to configure and start the Managed Server on windows environment. I am trying to configure Managed Server on linux environment. I am configuring the Managed Server with custom keystore. When I configured the Managed Server I specified the keystore/trustsote information in the Keystores tab of the Admin Console for Managed Server settings. Specified Private Key Alias, Password in SSL tab.But when I am starting the Managed Server from command line, I see the process looking for demo trust files and failing.
Here is the command I run to start the Managed Server:
./startManagedWebLogic.sh MyManagedServer1 https://localhost.localdomain:8443
Below is the console output:
<Mar 11, 2015 12:37:44 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>
<Mar 11, 2015 12:37:45 PM PDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:beaadmin
Enter password to boot WebLogic server:
<Mar 11, 2015 12:37:53 PM PDT> <Info> <Security> <BEA-090908> <Using default WebLogic SSL Hostname Verifier implementation.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks.>
<Mar 11, 2015 12:37:53 PM PDT> <Error> <Security> <BEA-090132> <Could not open the keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks for read access. Exception: java.io.FileNotFoundException: /opt/wlserver_10.3/server/lib/DemoTrust.jks (No such file or directory)>
<Mar 11, 2015 12:37:53 PM PDT> <Warning> <Security> <BEA-090164> <Failed to load trusted certificates from keystore /opt/wlserver_10.3/server/lib/DemoTrust.jks of type jks>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jre1.6.0_45/lib/security/cacerts.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at https://localhost.localdomain:8443.>
<Mar 11, 2015 12:37:55 PM PDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 11, 2015 12:37:55 PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320400> <The log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log00015. Log messages will continue to be logged in /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log is opened. All server side log events will be written to this file.>
<Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090837]The configured keystore location for the PKI Credential Mapper is either null or empty.>
<Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090815]The password provided for the keystore configured for the PKICredential Mapper was null.>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 11, 2015 12:37:57 PM PDT> <Critical> <Security> <BEA-090403> <Authentication for user beaadmin denied>
<Mar 11, 2015 12:37:57 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User beaadmin weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        Truncated. see log file for complete stacktrace
>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Mar 11, 2015 12:37:57 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Why is it looking for demotrust.jks file to start the Managed Server. We don't use the demo trust and cannot copy to the location it is referring to. I followed the solution provided at the below link:
http://serverfault.com/questions/106499/custom-trust-and-custom-identity-keystore-in-weblogic-10-3
There are 2 options given in the link. To update the boot.properties of the Admin Server and appending JAVA_OPTIONS to DomainEnv file. Both of these caused the failure of Admin Server. I couldn't bring up the server after these changes.I also came across posts talking about boot.properties for Managed Server. I don't see the security folder that has boot.properties for my Managed Server (verified it on both windows and linux boxes).
Thanks in advance.
-nn.

Hi Faisal,
Here is the config.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd"
        xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security"
        xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <name>JCRMDomain</name>
    <domain-version>10.3.4.0</domain-version>
    <security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml">
        <name>JCRMDomain</name>
        <realm>
            <sec:authentication-provider xsi:type="wls:default-authenticatorType">
                <sec:control-flag>SUFFICIENT</sec:control-flag>
            </sec:authentication-provider>
            <sec:authentication-provider xmlns:ext="http://xmlns.oracle.com/weblogic/security/extension" xsi:type="ext:jcrm-authenticatorType">
                <sec:name>JcrmAuthenticator</sec:name>
                <sec:control-flag>SUFFICIENT</sec:control-flag>
            </sec:authentication-provider>
            <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
            <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
            <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
            <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
            <sec:credential-mapper xsi:type="wls:pki-credential-mapperType">
                <sec:name>PKICredentialMapper</sec:name>
            </sec:credential-mapper>
            <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
            <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
            <sec:user-lockout-manager>
                <sec:lockout-threshold>3</sec:lockout-threshold>
                <sec:lockout-duration>15</sec:lockout-duration>
                <sec:lockout-reset-duration>99999</sec:lockout-reset-duration>
            </sec:user-lockout-manager>
            <sec:deploy-role-ignored>false</sec:deploy-role-ignored>
            <sec:deploy-policy-ignored>false</sec:deploy-policy-ignored>
            <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
            <sec:security-dd-model>DDOnly</sec:security-dd-model>
            <sec:combined-role-mapping-enabled>true</sec:combined-role-mapping-enabled>
            <sec:name>myrealm</sec:name>
            <sec:delegate-m-bean-authorization>false</sec:delegate-m-bean-authorization>
            <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator"
                                    xsi:type="pas:system-password-validatorType">
                <sec:name>JCRMPasswordValidator</sec:name>
                <pas:max-password-length>31</pas:max-password-length>
                <pas:min-password-length>15</pas:min-password-length>
                <pas:min-numeric-characters>2</pas:min-numeric-characters>
                <pas:min-lowercase-characters>2</pas:min-lowercase-characters>
                <pas:min-uppercase-characters>2</pas:min-uppercase-characters>
                <pas:min-non-alphanumeric-characters>2</pas:min-non-alphanumeric-characters>
            </sec:password-validator>
            <sec:deployable-provider-synchronization-enabled>false</sec:deployable-provider-synchronization-enabled>
        </realm>
        <default-realm>myrealm</default-realm>
        <credential-encrypted>{AES}cpwhv2peqwl0Z8Ma1Jk7KlmC6d1gtCAqxnzrmR5ssybHpM9AUzbBRJ7rE7m4/7U16IHgsTMkcOr/5/abZJ4NeuHR45jdDK1EjFmnUuPssISmGkan3EIpCKHmPPIynVxh</credential-encrypted>
        <node-manager-username>wdUXiuwL5A</node-manager-username>
        <node-manager-password-encrypted>{AES}UDiZjaLOrm0y+/I9noQVURudpzmRKMBOQR2B8ofNIt8=</node-manager-password-encrypted>
    </security-configuration>
    <server>
        <name>AdminServer</name>
        <max-http-message-size>10000000</max-http-message-size>
        <ssl>
            <name>AdminServer</name>
            <enabled>true</enabled>
            <hostname-verifier xsi:nil="true"></hostname-verifier>
            <hostname-verification-ignored>true</hostname-verification-ignored>
            <client-certificate-enforced>false</client-certificate-enforced>
            <listen-port>8443</listen-port>
            <two-way-ssl-enabled>true</two-way-ssl-enabled>
            <server-private-key-alias>localhost.localdomain</server-private-key-alias>
            <server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
            <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
            <allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
            <use-server-certs>true</use-server-certs>
            <jsse-enabled>true</jsse-enabled>
        </ssl>
        <listen-port-enabled>false</listen-port-enabled>
        <web-server>
            <keep-alive-secs>60</keep-alive-secs>
            <https-keep-alive-secs>60</https-keep-alive-secs>
        </web-server>
        <listen-address/>
        <java-compiler>javac</java-compiler>
        <tunneling-enabled>true</tunneling-enabled>
        <tunneling-client-ping-secs>45</tunneling-client-ping-secs>
        <tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
        <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
        <key-stores>CustomIdentityAndCustomTrust</key-stores>
        <custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
        <custom-identity-key-store-type>JKS</custom-identity-key-store-type>
        <custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
        <custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
        <custom-trust-key-store-type>JKS</custom-trust-key-store-type>
        <custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
    <overload-protection>
      <panic-action>system-exit</panic-action>
      <failure-action>force-shutdown</failure-action>
      <server-failure-trigger>
        <max-stuck-thread-time>600</max-stuck-thread-time>
        <stuck-thread-count>3</stuck-thread-count>
      </server-failure-trigger>
    </overload-protection>
    </server>
    <server>
      <name>MyManagedServer1</name>
      <ssl>
        <enabled>true</enabled>
        <listen-port>8445</listen-port>
        <server-private-key-alias>localhost.localdomain</server-private-key-alias>
        <server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
      </ssl>
      <machine xsi:nil="true"></machine>
      <listen-port>8444</listen-port>
      <listen-port-enabled>true</listen-port-enabled>
      <cluster xsi:nil="true"></cluster>
      <web-server>
        <web-server-log>
          <number-of-files-limited>false</number-of-files-limited>
        </web-server-log>
      </web-server>
      <listen-address></listen-address>
      <key-stores>CustomIdentityAndCustomTrust</key-stores>
      <custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
      <custom-identity-key-store-type>JKS</custom-identity-key-store-type>
      <custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
      <custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
      <custom-trust-key-store-type>JKS</custom-trust-key-store-type>
      <custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
      <data-source>
        <rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
      </data-source>
    </server>
    <production-mode-enabled>false</production-mode-enabled>
    <embedded-ldap>
        <name>JCRMDomain</name>
        <credential-encrypted>{AES}LNAnq4qCQQmy9rCOMN+uIZVPq1bVvPrwQqqtOScZrnYmwESt9aruHNVy4IjqMWz7</credential-encrypted>
    </embedded-ldap>
    <administration-port-enabled>true</administration-port-enabled>
    <configuration-version>10.3.4.0</configuration-version>
    <admin-server-name>AdminServer</admin-server-name>
</domain>
It has 'CustomIdentityAndCustomTrust' for both Admin Server as well as managed Server in it.
Thanks,
nn

Error starting managed server in a cluster

Hi,
Now am facing an issue while starting managed servers. Its only selective managed servers( 3 out of 8) . All are configured in the same way but the servers come to warning state after a restart.
The error is given below
<Emergency> AdminServer not reachable at http://192.44.12.147:7001
<Aug 5, 2010 2:43:53 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
     at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     Truncated. see log file for complete stacktrace
Please let me know from where this error comes. The weblogic server is running in devleopment mode only. So not sure where the authentication failed. Also is there any problem with the configuration done??? I need to know the root cause so as to avoid in future. Also I cannot reboot the servers as and when desired (to solve the issue). Please help
Thanks,
Charan
Edited by: charan27 on Aug 6, 2010 12:59 AM

Hi Charan,
if your ManagedServers are not in Configured for MSI Mode (Managed Server Indepence Mode) then you wont be able to start your Servers until the AdminServer is Already Running. I can see that the Exception u pasted that...your AdminServer is not reachable....It may be due to AdminServer Vs ManagedServer BOX Network Issue or Your AdminServer might be down when u tried to start the ManagedServer.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

Managed server loading demo trust when using admin port

I am trying to get the administration port to work in a weblogic 9.2 domain, but for some reason, the managed server is loading the demo trust store (Demotrust.jks) and java cacerts instead of the trust store configured in config.xml. Since the administration server certificate is not located in either of these trust stores, ssl handshake fails and the server tries to start in msi mode. (which also fails with weblogic.security.SecurityInitializationException because it doesn't have any users in it's ldap)
Is this the expected behaviour when starting a managed server with administration port?
1. Check -Dweblogic.management.server, if t3s, load demo trust.
2. Connect to admin server.
3. Fails? Start in msi mode, load config.xml etc, etc.
Or does the managed server look in config.xml, even if not starting in msi mode:
1. Check -Dweblogic.management.server, if t3s, check which trust stores is configured in config.xml. If none, load demo trust.
2. Connect to admin server.
3. Fails? Start in msi mode, load config.xml etc, etc.
If #1, what is the solution? Import admin server certificate in DemoTrust? Or configure ssl for the managed server on the command line, for it to load the correct certs?
If someone has seen this behaviour before and has a solution, it would be much appreciated.
Regards
Olov Pettersson

Yeah, and it works when importing the admin server cert in cacerts, but it isn't really an option here...

SOA OSB Single Managed Server Why?

I am trying to understand why the option exists to run OSB and SOA in the same managed server (same jvm). Can someone answer this question for me please? I inherited a SOA/OSB server and the previous administrator has taken this approach. I have not been able to find any documentation on the subject, it is briefly mentioned in the OSB install guide but with out explanation as to why someone would want to do this http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBDGGBE
Thanks

Troubleshooting Interoperability Between OSB and SOA Suite 10g and 11gR1 [ID 1267207.1]
Should OSB and SOA Suite Run in one single JVM?
To run OSB and SOA Suite in one single JVM, i.e. one single WebLogic Server instance, is very handsome for scenarios that only have low load and low memory requirements. For these development or test systems, OSB and SOA Suite can be set up to run in one of the following topologies:
Both OSB and SOA Suite in one single Admin Server (supported in 11.1.1.4 and upwards).
In a domain with one Admin Server and one single, non-clustered managed server to run OSB and SOA Suite on it (supported in 11.1.1.3 and upwards).
However, this is only recommended and supported for development or test environments.

Starting Managed Server on port below 1024

I am trying to configure the Managed Server to listen on port 80. I have tried several configurations but haven't got the right picture yet.
Let's see.
My configuration is an Admin Server and a Managed Server.
I configure a Machine and set the user ID and group ID to weblogic user; configures Node Manager to listen on "localhost:5555" and assigns the Managed Server to the Machine just created.
From now on, which operating system user should start each piece of this configuration?
- Is root starting Node Manager?
- Is weblogic user starting Administration Server?
- Is root starting Managed Server?
- Is it automatic or need to be done manually (by script or command prompt)?
any help whould be appreciated.
Regards,
Mariano

You start the nodemanager as root, and (you typically would) configure the machine to have a post-bind uid/gid (see UnixMachine configuration) that the WLS managed server should assume for all other operations - That is, you need root priviliges only for listening on a well-known port and nothing else.
It does not matter what other components run as.
Venkat

Trying to run the SOA/BPM managed server withOUT running the Admin server

(This is for demo/development purposes... Using 11.1.1.4 in Windows 7 with 4gb)
Because of memory constrains I am trying to run the BPM/workspaces application without needing the Admin to be running.
When they both run, I can use the credentials I create with the Admin server but the response time is prohibitive and all my memory is used...
It seems to run much faster when only the bpm managed server is running but then I cannot login ...
So my question is simply: Whats the easiest way to set it up so I can use credentials elsewhere without requiring the admin server to be running?
( I could connect to an OID instance I have outside this server or the seeded demo they refer to in other posts ... but do these also require the admin server to be running???)
aTdHvAaNnKcSe ! (thanks IN advance)
Claudio
Edited by: clichten on Aug 20, 2011 9:35 AM

I don't know if what you want is possible. Only did a suggestion that works fine for me. I'm running SOA Suite and BPM Suite 11.1.1.5 on WLS 10.3.5
Configure a new WLS domain and see if the BPM Dev template is available in your version.
I've tuned my startup script (setSOADomainEnv.cmd) as follows:
set JAVA_OPTIONS=%JAVA_OPTIONS%
set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms1536m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
Use visualvm that's available from your jdk/bin directory to monitor your jvm and optimize it accordingly
Regards,
Melvin

Managed server taking 15-25 minute to start with SOA/ADF/BPM application installed on it

Hi,
We are seeing issue with our Prod/non prod environment where Admin server is getting started in 5 minute which is normal but managed server(clustering) or non clustering environment are takiing 15-25 minute to start. We are using weblogic 10.3.6 installed on Solaris 11 64 bit server. Our managed server contain SOA 11g and BPM composites.
I have checked through the logs and other file but dont see any error, could someone please suggest me if this normal behavior or something is wrong with installation.
though this is not impacting anything but during maintenance window, its taking hour + for a claim restart.

Hi - Thanks for your reply.
I have checked through my server directory and can see weblogic.xml file under
./wlserver_10.3/server/lib/consoleapp/webapp/WEB-INF/weblogic.xml
while scanning this file, I dont see any attribute which talks about precompile as true.
do I need to add this paramater in this file as
<jsp-descriptor>
<precompile>true</precompile>
</jsp-descriptor>
please advise.

Configure Managed Server from Admin Console - Java arguments

Hi There;
I am configuring a managed server from the admin console and the one item that me up is when I add the following into the Arguments sections:
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol'|'oracle.fabric.common.classloaderurl.handler'|'oracle.fabric.common.uddiurl.handler'|'oracle.bpm.io.fs.protocol.
Note The command line script used double quotes (") but the console gave an error - Arguments may not contain '"' This sounded reasonable so I switched the double quotes to single quotes.
Switching to single quotes allowed me to bypass the error.
The managed server fails when I start it from the console:
Error message:
oracle.fabric.common.classloaderurl.handler ' is not recognized as an internal or external command, operable program or batch file.- it is like it ignores the values after the single quotes and fials.
How can I configure this parameter?
note: I am running weblogic 10.3.6 on widows 2008. it is a SOA Managed Server I am trying to setup to run from the Admin Console.
J

Try leaving out the quotes
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol
See also the documentation: URL (Java Platform SE 7 ) "interpreted as a list of packages separated by a vertical slash character |"

ADF Library Error on Remote Managed Server for Clustering

I wanted to configure 2 managed servers on different PCs for clustering. For this purpose first I created 2 managed servers on my test domain which is on my PC1. Tested my ADF applications for each managed server (srv1 and srv2) on PC1. They passed. When I moved one of these servers to another PC (PC2) with the following commands below, the commands said it was succeeded.
on PC1:
pack -managed=true -domain=E:\Oracle\Middleware\user_projects\domains\test_domain -template=E:\Oracle\Middleware\user_template\TEST_DOMAIN.jar -template_name="TEST"
onPC2: (Remote PC)
unpack -domain=test_domain -template=D:\oracle\Middleware\user_template\TEST_DOMAIN.jar
After these steps, I started my servers on command line by using the commands below:
on PC1:
startManagedWebLogic.cmd srv1 http://localhost:7011
on PC2: (Remote Managed Server)
startManagedWebLogic.cmd srv2 http://30.1.2.192:7011
srv1 changed its state to RUNNING mode easily, however srv2 changed its state to RUNNING with a lot of errors which were pointing that the ADF libraries and applications couldn't be found.
After the errors on srv2, I removed srv2 from the targets of libraries by using the Deployments screen of administration console.
Then I stopped srv2 and started it by using command line. It worked without any library and application. There was no error.
After those steps, I want to add srv2 to the targets of libraries. When I tried to do this I faced with the error message below:
An error occurred during activation of changes, please see the log for details.
[Deployer:149003]Unable to access application source information in 'E:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adf.oracle.domain.ear' for application 'adf.oracle.domain [LibSpecVersion=1.0,LibImplVersion=11.1.1.2.0]'. The specific error is: [Deployer:149158]No application files exist at 'E:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adf.oracle.domain.ear'..
My applications can not run without ADF libraries and I couldn't find any solution to the error above.
Can anyone help me on this subject

Hi,
<h3>Please Confirm Point -1 :</h3>
NOTE: the Absolute Path of the *"WLS Installation"* and *"Domain Directory"* must be same (Identical) in both the BOXES. Looks like the Path *"E:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adf.oracle.domain.ear"* doesnt exist in your Remote Box (PC-2). D:\oracle\Middleware.
I Think mistakenly u have installed WLS in <font color=red>E:\</font> in one Box and <font color=red>D:\</font> in another Box.
<h3>Please Confirm Point -2 :</h3>
Please refer to the following link: http://download.oracle.com/docs/cd/E12839_01/webcenter.1111/e12405/wcadm_deploy.htm#BABEJEEA
Which says that you must install a few Libraries (including ADF) in order to utilize the ADF features ...in every Managed Server, to avoid these kind of issues. You must deploy the following libraries to the new managed server or cluster:
<font color=maroon><b>
adf.oracle.domain(1.0,11.1.1.0.0)
adf.oracle.domain.webapp(1.0,11.1.1.1.0)</b></font><BR>
jsf(1.2,1.2.9.0)
jstl(1.2,1.2.0.1)
ohw-rcf(5,5.0)
ohw-uix(5,5.0)
UIX(11,11.1.1.1.0)
<font color=maroon><b>oracle.adf.dconfigbeans(1.0,11.1.1.0.0)
oracle.adf.management(1.0,11.1.1.1.0)</b></font><BR>
oracle.dconfig-infra
oracle.jrf.system.filter
oracle.jsp.next(11.1.1,11.1.1)
oracle.sdp.client(11.1.1,11.1.1)
oracle.soa.workflow.wc(11.1.1,11.1.1)
oracle.webcenter.framework(11.1.1,11.1.1)
oracle.webcenter.framework.view(11.1.1,11.1.1)
oracle.webcenter.jive.dependency(11.1.1,11.1.1)
oracle.webcenter.skin(11.1.1,11.1.1)
oracle.wsm.seedpolicies(11.1.1,11.1.1)
oracle.portlet-producer.jpdk(11.1.1,11.1.1)
oracle.portlet-producer.wsrp(11.1.1,11.1.1)
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

Problem when we created the managed server to configure different ports.

I am trying to configure different ports for admin console and my communication service as we can’t share admin port to the outside world.
So that only admin can access admin console using admin port.
And out side clients can access my webapplication using different port.
For this i have created the managed server in weblogic.and I deployed the application on managed server.
Now admin server is running on 8001 port and my Communication Service application is running on 7001 port.
But when I tried to configure MBeans related to myCommunicationServiceApplication those were disapper on admin console. And the other wlng services are appearing on admin console.
1. Since my application deployed on managed server MBeans registration happened from myapplication hence it’s disappear on admin console.
Now If I want to configure Mbeans (related to my communication service) how can I configure it?
2. My communication service using configurationStore module and other wlng services.
When I tried to start my application on managed server I got the below error:
<Apr 28, 2009 12:22:44 PM IST> <Error> <Deployer> <BEA-149231> <dscp11166.TechMahindra.com> <Unable to set the activation state to true for the application 'wlng_nt_qualcomm_active_mediation [Version=1.0]'.
com.bea.wlcp.wlng.api.storage.configuration.ConfigurationException: Configuration store module is not available.
3. I tried to target all wlngResources to manged server by editing config.xml file.
Then all wlng services disappears on admin console. If this is the case how can I configure container/account services on wlng?
I have created the Basicweblogic domain.
Below is the config.xml for reference.
"QualcommServer" is managed server name.
Can any one please suggest me how to configure this kind of scenarios?
<server>
<name>AdminServer</name>
<machine>new_Machine_1</machine>
<listen-port>8001</listen-port>
<default-iiop-user>weblogic</default-iiop-user>
<default-iiop-password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</default-iiop-password-encrypted>
<listen-address>localhost</listen-address>
</server>
<server>
<name>QualcommServer</name>
<machine>new_Machine_1</machine>
<listen-address>localhost</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>C:\Program Files\Java\jdk1.6.0</java-home>
<class-path>C:\bea\wlng400\server\lib\weblogic.jar;C:\bea\wlng_pds400\lib\wlng\wlng.jar</class-path>
<bea-home>C:\bea</bea-home>
<username>weblogic</username>
<password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>managedserver</name>
<credential-encrypted>{3DES}9q80YuFJueVVJxoWduJA1OGhbqk14EpgQWWyTrzlmxo=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.0.1.0</configuration-version>
<app-deployment>
<name>wlng_nt_session#4.0</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/wlng_nt_session.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>interceptors</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/interceptors.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlng_prm</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/wlng_prm.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlng_nt_qualcomm_active_mediation#1.0</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>servers\AdminServer\upload\wlng_nt_qualcomm_active_mediation.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>new_Machine_1</name>
<node-manager>
<name>new_Machine_1</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>JMSServer-AdminServer</name>
<target>AdminServer</target>
</jms-server>
<jms-system-resource>
<name>WLNGJMSResource</name>
<target>QualcommServer</target>
<descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>networktier</name>
<target>AdminServer</target>
<descriptor-file-name>custom/nt.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
</custom-resource>
<custom-resource>
<name>wlng-edr</name>
<target>AdminServer</target>
<descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>wlng.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>wlng.localTX.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Thanks,
Srinu Babu P

Dear Nariharan,
Today I faced a simlar issue, and this SAP Note helped me fix it: 1966807 - Duplication of AET table records in change processing
In my case, cardinality of AET table was 1:1, and I was getting duplicate PARENT_ID every time when trying to create a subsequent service request for my activity.
Regards,
Andrew

How to use jspx deployed in different managed server from bpm work space

Hi,
I have created and deployed my view project having all the jspx files and managed beans into a different managed server(created a new server,not into the soa server).
I have created a bpm process and now I want to use the jspx page(deployed into the new managed server) in my bpm wrokspace.
Can anyone help me how I can do it.
thanks in advance.
Regards,
Tukuna

Hi ,
I tried with the below url and still i am not able to open the jspx page deployed into the admin server.
http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/bp_designtf.htm#BDCFBJIE
28.8.4 How To Deploy a Task Form to a non-SOA Oracle WebLogic Server
Any help on this is appreciatable.
Many thanks
Tuku

After LDAP Configuration Starting biserver1(Managed Server) is getting Fail

I have Configured the LDAP(OID) by following the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition
11g Release 1 (11.1.1) (Section 3) Completed sucessfully with out any errors.. Users also imported sucessfully. after that when I am starting the biserver1(Managed Server) I am getting error like
"Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied"
was taken from biserver log file. please find the below attachment for the same.
Please help me for the same
biserver.log
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Server> <usstuobitest03.diversey.com> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241307> <BEA-002609> <Channel Service initialized.>
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241317> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241317> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241317> <BEA-000406> <PosixSocketMuxer was built on Apr 24 2007 16:05:00>
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241339> <BEA-000436> <Allocating 3 reader threads.>
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241339> <BEA-000446> <Native IO Enabled.>
####<Mar 22, 2012 2:40:41 PM CDT> <Info> <IIOP> <usstuobitest03.diversey.com> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241572> <BEA-002014> <IIOP subsystem enabled.>
####<Mar 22, 2012 2:40:46 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445246302> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
####<Mar 22, 2012 2:40:46 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445246667> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
####<Mar 22, 2012 2:40:46 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445246944> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_lDqprIBb69IOInpk4TtgfToFVP8=>
####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247141> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247707> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247719> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247891> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server bi_server1 for security realm myrealm.>
####<Mar 22, 2012 2:40:47 PM CDT> <Notice> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247892> <BEA-090082> <Security initializing using security realm myrealm.>
####<Mar 22, 2012 2:40:47 PM CDT> <Critical> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247908> <BEA-090403> <Authentication for user denied>
####<Mar 22, 2012 2:40:47 PM CDT> <Critical> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247909> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
     at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
     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.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy36.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
     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.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy54.authenticate(Unknown Source)
     at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
####<Mar 22, 2012 2:40:47 PM CDT> <Notice> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247917> <BEA-000365> <Server state changed to FAILED>
####<Mar 22, 2012 2:40:47 PM CDT> <Error> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247917> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Mar 22, 2012 2:40:47 PM CDT> <Notice> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247918> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Mar 22, 2012 2:40:47 PM CDT> <Info> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247923> <BEA-000236> <Stopping execute threads.>

WebLogic has 2 accounts that were created on install..BISystemUser and weblogic or whatever you may have called that. Are the passwords of BISystemUser the same in EM and WebLogic? Also, I believe you had to create a BISystemUser in OID. That password should match to the BISystemUser in EM and WL.

Getting error while starting Managed server configured in ALSB(ClusteredEnv

Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
Kartheek

You probably changed your system password in the console?
Look for your boot.properties file in the following location:
[domain]\servers\[server]\security
change the following line:
password={3DES}Ytm72Oh4zE0bsptrYn13Xw==
to:
password=mynewpassword
WebLogic Server will encrypt the password on the next boot, and your problem should be resolved.

Configuring BPM in Clustered/Managed Server

Similar Messages

Maybe you are looking for