I don't Configuring Access Manager in SSL Mode

i only install am7.1 and ws7.0 in windows2003 pack 1.
then, i read "Sun Java SystemAccess Manager 7.1 Postinstallation Guide" .
it said that "Login to theWeb Server console.The default port is 8888." but i can't find the default port .
i think my web server console's default port is 8989.

Hi,
As a part of my requirement, I need to Configure Access Manager in SSL Mode. For that, I followed all the steps(Change http to https in web server instance in Access Manager, Install Certificate, Modify AMConfig.properties) mentioned in the PostInstallation Guide of Sun Access Manager to configure the SSL using Selfsigned certificate. so, after doing all these steps, as soon as the hit the Access Manager URL httsp://machinename:portno/amserver/UI/Login, it shows "page cannot be displayed" error. I have checked the web server with SSL enabled in it and its running fine.
On one of forum post, I read that you need to set this property to true "com.sun.am.jssproxy.trustAllServerCerts" if you are not installing the ROOTCA certificate however this is not listed in the AM documentation.
Any help on this would be highly appreciated. Let me know if am missing any steps.

Similar Messages

  • Can not configure Access Manager

    Hi all,
    1. I istalled Sun java messaging server 6.
    2. I edit amsamplesilent to prepare amsamplesilent.my:
    # cd /opt/SUNWam/bin
    #mv amsamplesilent amsamplesilent.my
    3. I configure Access Manager:
    #./amconfig -s amsamplesilent.my but get the following error:
    # ./amconfig amsamplesilent.my
    Usage: amconfig -s <silentinputfile>
    ./amconfig: Sourcing ./amutils
    ln: cannot create /opt/SUNWam/lib/jaxrpc-spi.jar: File exists
    chown: jaxrpc-spi.jar: No such file or directory
    full install
    ./amdsconfig: Sourcing ./amutils
    LD_LIBRARY_PATH is --- /usr/lib/mps/secv1:/usr/lib/mps/secv1:/usr/lib/mps/secv1:/opt/SUNWam/lib:/opt/SUNWam/ldaplib/ldapsdk
    CLASSPATH is --- /opt/SUNWam/locale:/etc/opt/SUNWam/config:/opt/SUNWam/lib:/opt/SUNWam/lib/am_services.jar:/opt/SUNWam/lib/ldapjdk.jar:/usr/share/lib/mps/secv1/jss3.jar:/opt/SUNWam/lib/am_sdk.jar
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    sleep 3
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    sleep 4
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    sleep 5
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    sleep 6
    ERROR : Loading of Access Manager schema into the Directory failed
    Starting the tag swapping of the install.ldif and installExisting.ldif
    ROOT_SUFFIX is dc=iplanet,dc=com
    People_NM_ROOT_SUFFIX is People_dc=iplanet_dc=com
    SERVER_HOST sample.red.iplanet.com
    DIRECTORY_SERVER sample.red.iplanet.com
    DIRECTORY_PORT 389
    USER_NAMING_ATTR uid
    ORG_NAMING_ATTR o
    CONSOLE_DEPLOY_URI /amconsole
    ORG_OBJECT_CLASS sunismanagedorganization
    RS_RDN iplanet
    USER_OBJECT_CLASS inetorgperson
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    sleep 3
    ERROR : Configuring/Loading of the default DIT in the Directory Server failed
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    sleep 3
    Warning : Plugins and Indexes already exist.
    ./amsvcconfig: Sourcing ./amutils
    LD_LIBRARY_PATH is --- /usr/lib/mps/secv1:/usr/lib/mps/secv1:/usr/lib/mps/secv1:/opt/SUNWam/lib:/opt/SUNWam/ldaplib/ldapsdk
    CLASSPATH is --- /opt/SUNWam/locale:/etc/opt/SUNWam/config:/opt/SUNWam/lib:/opt/SUNWam/lib/am_services.jar:/opt/SUNWam/lib/ldapjdk.jar:/usr/share/lib/mps/secv1/jss3.jar:/opt/SUNWam/lib/am_sdk.jar
    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    Loading service schema XML files ...
    Info 112: Entering ldapAuthenticate method!
    Error 15: Cannot authenticate user.
    LDAP authentication failed.
    Error 9: Operation failed: Error 15: Cannot authenticate user.
    Error occured while loading: /etc/opt/SUNWam/config/ums/ums.xml
    ./amws61config: Sourcing ./amutils
    /opt/SUNWam/console.war: No such file or directory
    current web app is applications
    copying files from sunwamconsdk
    Swapping tag swap in index.html files ...
    Making amconsole.war
    Successfully done making warfile ...
    Deploying from /opt/SUNWam/web-src/applications (/opt/SUNWam/amconsole.war) to /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/applications for /amconsole
    wdeploy deploy -u /amconsole -i https-sample.red.iplanet.com -v https-sample.red.iplanet.com -d /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/applications /opt/SUNWam/amconsole.war
    [wdeploy] The war file name is /opt/SUNWam/amconsole.war
    [wdeploy] Fatal error in parsing XML file ..Premature end of file.
    [wdeploy] (-1, -1) in file null
    [wdeploy] Error encountered while parsing /opt/SUNWwbsvr/https-sample.red.iplanet.com/config/server.xml
    Failed deploying /amconsole
    /opt/SUNWam/services.war: No such file or directory
    current web app is services
    Swapping tag swap in index.html files ...
    Making amserver.war
    Successfully done making warfile ...
    Deploying from /opt/SUNWam/web-src/services (/opt/SUNWam/amserver.war) to /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/services for /amserver
    wdeploy deploy -u /amserver -i https-sample.red.iplanet.com -v https-sample.red.iplanet.com -d /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/services /opt/SUNWam/amserver.war
    [wdeploy] The war file name is /opt/SUNWam/amserver.war
    [wdeploy] Fatal error in parsing XML file ..Premature end of file.
    [wdeploy] (-1, -1) in file null
    [wdeploy] Error encountered while parsing /opt/SUNWwbsvr/https-sample.red.iplanet.com/config/server.xml
    Failed deploying /amserver
    /opt/SUNWam/password.war: No such file or directory
    current web app is password
    Swapping tag swap in index.html files ...
    Making ampassword.war
    Successfully done making warfile ...
    Deploying from /opt/SUNWam/web-src/password (/opt/SUNWam/ampassword.war) to /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/password for /ampassword
    wdeploy deploy -u /ampassword -i https-sample.red.iplanet.com -v https-sample.red.iplanet.com -d /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/password /opt/SUNWam/ampassword.war
    [wdeploy] The war file name is /opt/SUNWam/ampassword.war
    [wdeploy] Fatal error in parsing XML file ..Premature end of file.
    [wdeploy] (-1, -1) in file null
    [wdeploy] Error encountered while parsing /opt/SUNWwbsvr/https-sample.red.iplanet.com/config/server.xml
    Failed deploying /ampassword
    /opt/SUNWam/introduction.war: No such file or directory
    current web app is common
    Swapping tag swap in index.html files ...
    Making amcommon.war
    Successfully done making warfile ...
    Deploying from /opt/SUNWam/web-src/common (/opt/SUNWam/amcommon.war) to /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/common for /amcommon
    wdeploy deploy -u /amcommon -i https-sample.red.iplanet.com -v https-sample.red.iplanet.com -d /opt/SUNWwbsvr/https-sample.red.iplanet.com/is-web-apps/common /opt/SUNWam/amcommon.war
    [wdeploy] The war file name is /opt/SUNWam/amcommon.war
    [wdeploy] Fatal error in parsing XML file ..Premature end of file.
    [wdeploy] (-1, -1) in file null
    [wdeploy] Error encountered while parsing /opt/SUNWwbsvr/https-sample.red.iplanet.com/config/server.xml
    Failed deploying /amcommon
    Checking if Web Server is already configed with Access Manager
    Configuring Web Server
    Mime type: 'type=text/vnd.wap.wml' already exists: Skipping ....
    Mime type: 'type=image/vnd.wap.wbmp' already exists: Skipping ....
    I tried again but I still get this error.
    Any Ideas for this problem?
    Thanks.

    ldap_simple_bind: Can't connect to the LDAP server - No route to host
    i would consider this a fatal error.
    The system cannot locate where your Directory Server is. "no route to host" means that it's trying to get to the host, but your networking isn't set up correctly, and it doesn't find any route to get to the specified host.

  • How do I configure Access Manager?

    I don't have idea how to configure Access Manager, I installed ans configure Directory and Web Server and working well, but I need to configure access Manager, there is a script called " amsamplesilent " it has some variables that i dont understand very well, how do I do to configure?
    Plz help me.

    So you used "configure later" option while installing Access Manager - correct?
    amsamplesilent is not a script - it's an input file for the command "amconfig"
    copy this file and adjust it to your settings (which variables haven't you understood?)
    run amconfig -f <your_sample_install_file>
    -Bernhard

  • Configuring Access Manager as Service Provider

    Hi All,
    What documentation explains how to configure SSO with Access Manager 7 as Sefrvice Provider using redirect-artifact (or else) binding according to SAML v.2? I have SiteMinder 6.0 as IdP ready to go.
    Thanks

    Bernhard,
    We have upgraded our Web PA to version 2.1-09. One of your previous replies stated the com.iplanet.am.naming.ignoreNamingservice property was not availalbe in the PA agent properties but only in the Java SKD. Indeed we do not see such a key in the new Web PA AMAgent.properties.
    Can you please explain how to configure the AMAgent.properties and/or the Access Manager server (or properties) so that subsequent calls to the services (returned by the call to the naming service) get directed thru the load balancer? Below are the setting in our AMAgent and AMConfig properties files
    AMAgent.properties
    com.sun.am.namingURL = https://lb-mydomain.com:443/amserver/namingservice
    com.sun.am.policy.am.loginURL = https://lb-mydomain.com:443/amserver/UI/Login
    AMConfig.properties
    com.iplanet.am.server.protocol=https
    com.iplanet.am.server.host=am.mydomain.com
    com.iplanet.am.server.port=443
    com.iplanet.am.console.protocol=https
    com.iplanet.am.console.host=lb-mydomain.com
    com.iplanet.am.console.port=443
    com.iplanet.am.profile.host=lb-mydomain.com
    com.iplanet.am.profile.port=443
    com.iplanet.am.naming.url=https://lb-mydomain.com:443/amserver/namingservice
    com.iplanet.am.notification.url=https://lb-mydomain.com:443/amserver/notifica
    tionservice
    If we set com.iplanet.am.server.host=lb-mydomain.com we get an exception when trying to start the AM web container. I don't know if this may be partof our issue or not. Please comment.
    Thanks,
    Craig

  • Portal 7.1 + Access Manager in realm mode

    OS Solaris SPARC 9.
    Components already installed: SJES Directory Server + SJES5 Web Server + SJES5 Access Manager (configured in realm mode with 'Configure now' option selected).
    Web Server is listenin on port 8088.
    It is said in "SJES5 Installation Guide for UNIX) that Portal Server supports Realm mode only if Access Manager is configured with Directory Server, with AMSDK configured for the data store.
    I've installed AMSDK at the same time when installed AM itself. No postinstallition configuration was made.
    But when I try to install Portal 7.1 (using SJES5 GUI installer, in 'configure now' mode) in realm mode, i receive following errors during installition:
    Sun enterprise system 5 - installed
    Java DB - installed (configure after install)
    System Registry 3.1 installed (configure after install)
    Java System Portal - installed (configuration failed)
    Exploring /var/opt/SUNWportal/logs/config/portal.fabric.0.0.log shows following errors:
    WARNING     SJS Portal Server     debug.com.sun.portal.fabric.config     "ThreadID=10; ClassName=com.sun.portal.fabric.config.ValidatePortalInputData; MethodName=validateSharedComponents; "     PSFB_CSPFC0301:The Directory PrivateLibDir is *not* being validated.
    SEVERE     SJS Portal Server     debug.com.sun.portal.fabric.config     "ThreadID=10; ClassName=com.sun.portal.fabric.config.ValidatePortalInputData; MethodName=checkPSAMInstallData; "     PSFB_CSPFC0061:The Access Manager Configuration File /etc/opt/SUNWam/config/AMConfig.properties exists with required permissions.     
    SEVERE     SJS Portal Server     debug.com.sun.portal.fabric.util     "ThreadID=10; ClassName=com.sun.portal.fabric.util.NetworkUtil; MethodName=isPortValid; "     PSFB_CSPFU0011: The Port 8989 on server.org.com is being used.     
    SEVERE     SJS Portal Server     debug.com.sun.portal.fabric.util     "ThreadID=10; ClassName=com.sun.portal.fabric.util.NetworkUtil; MethodName=isPortValid; "     PSFB_CSPFU0011: The Port 8088 on server.org.com is being used.     
    SEVERE     SJS Portal Server     debug.com.sun.portal.fabric.config     "ThreadID=10; ClassName=com.sun.portal.fabric.config.PortalConfigurator; MethodName=createPortalInstances; "     PSFB_CSPFC0041:Failed invoking mbean action : create instance.
    javax.management.MBeanException: Exception thrown in operation createAndFinalizeInstance                              
    "     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:435)"                              
    "     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)"                              
    "     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)"                              
    "     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)"                              
    "     at com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)"                              
    "     at com.sun.jdmk.interceptor.MBeanServerInterceptorWrapper.invoke(MBeanServerInterceptorWrapper.java:512)"                              
    "     at com.sun.portal.admin.server.PortalServerLoggingInterceptor.invoke(PortalServerLoggingInterceptor.java:422)"                              
    "     at com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)"                              
    "     at com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:618)"                              
    "     at com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)"                              
    "     at com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:106)"                              
    "     at javax.management.remote.generic.ServerIntermediary.handleRequest(ServerIntermediary.java:280)"                              
    "     at javax.management.remote.generic.ServerIntermediary$PrivilegedRequestJob.run(ServerIntermediary.java:951)"                              
    "     at java.security.AccessController.doPrivileged(Native Method)"
    "     at javax.management.remote.generic.ServerIntermediary$RequestHandler.handleMBSReqMessage(ServerIntermediary.java:727)"
    "     at javax.management.remote.generic.ServerIntermediary$RequestHandler.execute(ServerIntermediary.java:629)"
    "     at com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl$RemoteJob.run(ServerSynchroMessageConnectionImpl.java:249)"
    "     at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)"
    "     at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)"
    Caused by: com.sun.portal.admin.common.PSMBeanException: java.lang.SecurityException: authentication failure: Authentication failed: Error occurred while processing XML request.
    Connection refused
    com.sun.cacao.agent.impl.CacaoJmxConnectorProvider.newJMXConnector(CacaoJmxConnectorProvider.java:388)
    javax.management.remote.JMXConnectorFactory.getConnectorAsService(JMXConnectorFactory.java:415)
    javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:307)
    javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    com.sun.portal.admin.common.util.AdminUtil.getConnector(AdminUtil.java:813)
    com.sun.portal.admin.server.AdminServerUtil.getJMXConnector(AdminServerUtil.java:81)
    com.sun.portal.fabric.mbeans.Portal.createAndFinalizeInstance(Portal.java:549)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    java.lang.reflect.Method.invoke(Method.java:585)
    com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
    com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)
    com.sun.jdmk.interceptor.MBeanServerInterceptorWrapper.invoke(MBeanServerInterceptorWrapper.java:512)
    com.sun.portal.admin.server.PortalServerLoggingInterceptor.invoke(PortalServerLoggingInterceptor.java:422)
    com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)
    com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:618)
    com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)
    com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:106)
    javax.management.remote.generic.ServerIntermediary.handleRequest(ServerIntermediary.java:280)
    javax.management.remote.generic.ServerIntermediary$PrivilegedRequestJob.run(ServerIntermediary.java:951)
    java.security.AccessController.doPrivileged(Native Method)     
    javax.management.remote.generic.ServerIntermediary$RequestHandler.handleMBSReqMessage(ServerIntermediary.java:727)     
    javax.management.remote.generic.ServerIntermediary$RequestHandler.execute(ServerIntermediary.java:629)     
    com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl$RemoteJob.run(ServerSynchroMessageConnectionImpl.java:249)     
    com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)     
    com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)     
    "     at com.sun.portal.fabric.mbeans.Portal.createAndFinalizeInstance(Portal.java:564)"     
    "     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:585)"     
    "     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)"     
    "     ... 18 more"     
    [#     2007-06-14T19:35:27.195+0400     SEVERE     SJS Portal Server     debug.com.sun.portal.fabric.config     "ThreadID=10; ClassName=com.sun.portal.fabric.config.PortalConfigurator; MethodName=configurePortal; "     PSFB_CSPFC0034:Encountered Exception while configuring the Portal
    com.sun.portal.fabric.tasks.ConfigurationException: javax.management.MBeanException: Exception thrown in operation createAndFinalizeInstance                              
    "     at com.sun.portal.fabric.config.PortalConfigurator.createPortalInstances(PortalConfigurator.java:1314)"                              
    "     at com.sun.portal.fabric.config.PortalConfigurator.configurePortal(PortalConfigurator.java:842)"                              
    "     at com.sun.portal.fabric.config.ConfigurePortal.main(ConfigurePortal.java:189)"                              
    Caused by: javax.management.MBeanException: Exception thrown in operation createAndFinalizeInstance                              
    "     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:435)"                              
    "     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)"                              
    "     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)"                              
    "     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)"                              
    "     at com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)"                              
    "     at com.sun.jdmk.interceptor.MBeanServerInterceptorWrapper.invoke(MBeanServerInterceptorWrapper.java:512)"                              
    "     at com.sun.portal.admin.server.PortalServerLoggingInterceptor.invoke(PortalServerLoggingInterceptor.java:422)"                              
    "     at com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)"                              
    "     at com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:618)"                              
    "     at com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)"                              
    "     at com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:106)"
    "     at javax.management.remote.generic.ServerIntermediary.handleRequest(ServerIntermediary.java:280)"
    "     at javax.management.remote.generic.ServerIntermediary$PrivilegedRequestJob.run(ServerIntermediary.java:951)"
    "     at java.security.AccessController.doPrivileged(Native Method)"
    "     at javax.management.remote.generic.ServerIntermediary$RequestHandler.handleMBSReqMessage(ServerIntermediary.java:727)"
    "     at javax.management.remote.generic.ServerIntermediary$RequestHandler.execute(ServerIntermediary.java:629)"
    "     at com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl$RemoteJob.run(ServerSynchroMessageConnectionImpl.java:249)"
    "     at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)"
    "     at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)"
    Caused by: com.sun.portal.admin.common.PSMBeanException: java.lang.SecurityException: authentication failure: Authentication failed: Error occurred while processing XML request.
    Connection refused
    com.sun.cacao.agent.impl.CacaoJmxConnectorProvider.newJMXConnector(CacaoJmxConnectorProvider.java:388)
    javax.management.remote.JMXConnectorFactory.getConnectorAsService(JMXConnectorFactory.java:415)
    javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:307)
    javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    com.sun.portal.admin.common.util.AdminUtil.getConnector(AdminUtil.java:813)
    com.sun.portal.admin.server.AdminServerUtil.getJMXConnector(AdminServerUtil.java:81)
    com.sun.portal.fabric.mbeans.Portal.createAndFinalizeInstance(Portal.java:549)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    java.lang.reflect.Method.invoke(Method.java:585)
    com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
    com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)
    com.sun.jdmk.interceptor.MBeanServerInterceptorWrapper.invoke(MBeanServerInterceptorWrapper.java:512)
    com.sun.portal.admin.server.PortalServerLoggingInterceptor.invoke(PortalServerLoggingInterceptor.java:422)
    com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)
    com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:618)
    com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)
    com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:106)
    javax.management.remote.generic.ServerIntermediary.handleRequest(ServerIntermediary.java:280)
    javax.management.remote.generic.ServerIntermediary$PrivilegedRequestJob.run(ServerIntermediary.java:951)
    java.security.AccessController.doPrivileged(Native Method)
    javax.management.remote.generic.ServerIntermediary$RequestHandler.handleMBSReqMessage(ServerIntermediary.java:727)
    javax.management.remote.generic.ServerIntermediary$RequestHandler.execute(ServerIntermediary.java:629)
    com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl$RemoteJob.run(ServerSynchroMessageConnectionImpl.java:249)
    com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)
    com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)
    "     at com.sun.portal.fabric.mbeans.Portal.createAndFinalizeInstance(Portal.java:564)"
    "     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:585)"
    "     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)"
    "     ... 18 more"                              
    [#     2007-06-14T19:35:27.792+0400     SEVERE     SJS Portal Server     debug.com.sun.portal.fabric.config     "ThreadID=10; ClassName=com.sun.portal.fabric.config.ConfigurePortal; MethodName=main; "     PSFB_CSPFC0014:Failed configuring Portal Server!!
    com.sun.portal.fabric.tasks.ConfigurationException: com.sun.portal.fabric.tasks.ConfigurationException: javax.management.MBeanException: Exception thrown in operation createAndFinalizeInstance                              
    "     at com.sun.portal.fabric.config.PortalConfigurator.configurePortal(PortalConfigurator.java:849)"                              
    "     at com.sun.portal.fabric.config.ConfigurePortal.main(ConfigurePortal.java:189)"                              
    Caused by: com.sun.portal.fabric.tasks.ConfigurationException: javax.management.MBeanException: Exception thrown in operation createAndFinalizeInstance                              
    "     at com.sun.portal.fabric.config.PortalConfigurator.createPortalInstances(PortalConfigurator.java:1314)"                              
    "     at com.sun.portal.fabric.config.PortalConfigurator.configurePortal(PortalConfigurator.java:842)"                              
    "     ... 1 more"                              
    Caused by: javax.management.MBeanException: Exception thrown in operation createAndFinalizeInstance                              
    "     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:435)"                              
    "     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)"                              
    "     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)"                              
    "     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)"                              
    "     at com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)"
    "     at com.sun.jdmk.interceptor.MBeanServerInterceptorWrapper.invoke(MBeanServerInterceptorWrapper.java:512)"
    "     at com.sun.portal.admin.server.PortalServerLoggingInterceptor.invoke(PortalServerLoggingInterceptor.java:422)"
    "     at com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)"
    "     at com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:618)"
    "     at com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)"
    "     at com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:106)"
    "     at javax.management.remote.generic.ServerIntermediary.handleRequest(ServerIntermediary.java:280)"
    "     at javax.management.remote.generic.ServerIntermediary$PrivilegedRequestJob.run(ServerIntermediary.java:951)"
    "     at java.security.AccessController.doPrivileged(Native Method)"
    "     at javax.management.remote.generic.ServerIntermediary$RequestHandler.handleMBSReqMessage(ServerIntermediary.java:727)"
    "     at javax.management.remote.generic.ServerIntermediary$RequestHandler.execute(ServerIntermediary.java:629)"
    "     at com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl$RemoteJob.run(ServerSynchroMessageConnectionImpl.java:249)"
    "     at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)"
    "     at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)"
    Caused by: com.sun.portal.admin.common.PSMBeanException: java.lang.SecurityException: authentication failure: Authentication failed: Error occurred while processing XML request.
    Connection refused
    com.sun.cacao.agent.impl.CacaoJmxConnectorProvider.newJMXConnector(CacaoJmxConnectorProvider.java:388)
    javax.management.remote.JMXConnectorFactory.getConnectorAsService(JMXConnectorFactory.java:415)
    javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:307)
    javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    com.sun.portal.admin.common.util.AdminUtil.getConnector(AdminUtil.java:813)
    com.sun.portal.admin.server.AdminServerUtil.getJMXConnector(AdminServerUtil.java:81)
    com.sun.portal.fabric.mbeans.Portal.createAndFinalizeInstance(Portal.java:549)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    java.lang.reflect.Method.invoke(Method.java:585)
    com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
    com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:203)
    com.sun.jdmk.interceptor.MBeanServerInterceptorWrapper.invoke(MBeanServerInterceptorWrapper.java:512)
    com.sun.portal.admin.server.PortalServerLoggingInterceptor.invoke(PortalServerLoggingInterceptor.java:422)
    com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)
    com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInterceptor.java:618)
    com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)
    com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefaultForwarder.java:106)
    javax.management.remote.generic.ServerIntermediary.handleRequest(ServerIntermediary.java:280)
    javax.management.remote.generic.ServerIntermediary$PrivilegedRequestJob.run(ServerIntermediary.java:951)
    java.security.AccessController.doPrivileged(Native Method)
    javax.management.remote.generic.ServerIntermediary$RequestHandler.handleMBSReqMessage(ServerIntermediary.java:727)
    javax.management.remote.generic.ServerIntermediary$RequestHandler.execute(ServerIntermediary.java:629)
    com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl$RemoteJob.run(ServerSynchroMessageConnectionImpl.java:249)
    com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)
    com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)
    "     at com.sun.portal.fabric.mbeans.Portal.createAndFinalizeInstance(Portal.java:564)"     
    "     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:585)"     
    "     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)"     
    "     ... 18 more"     
    May the problem be that AMSDK need additional configuration for datastore?

    Yes, copy config is enabled in all organisations.
    I also tried to create an ldap data store instead of amsdk, but same behavior.
    I have "fixed" the issue through a hack now by creating my own ldap login module, simply copied the original one and replaced LDAPPrincipal with my own version. It returns now a correct dn for the user in portal instead of the username only.
    Works this way. Alas, it is just a hack...
    As far as I can see, the problem is in the IDRepository. Its somewhat:
    If (username is a DN) return username;
    else return UniversalID;
    This universal ID is then used by ps to get desktop information and since it is not a valid dn in ldap the desktop servlet cannot proceed...
    I guess the problem does not appear in your environment. Maybe it was introduced with update 1? Do you use update 2?
    Thanks, Chris

  • SSL connection between Dist Auth UI Server and Access Manager

    Hi,
    I have a Dist Auth UI Server installed in Web Server 7 and working properly, but now i want to configure it to talk with Access Manager with a secure port.
    I have configured Access Manager (also deployed in Web Server 7) in a secure port (443). I have requested and installed the server certificate in the Access Manager Web Server instance and also the root entity certificate.
    My question is: how must i configure the UI Server to communicate with the Access Manager Server in a secure way and trust the certificate that the WS of the AM presents ?
    Regards,

    There have been a few reports of the same behaviour with other customers - specifically with the handling of the encoding of "+" characters to " ". It relates to how cookie encoding/decoding is performed (as you have already observed).
    The solution for these customers was the following:
    => AM server/client side:
    Ensure that com.iplanet.am.cookie.encode=false in AMConfig.properties and AMAgent.properties on all systems.
    => AM client (UWC) side:
    - Set <property name="encodeCookies" value="false"/> in /var/opt/SUNWuwc/WEB-INF/sun-web.xml. This will prevent UWC from trying to urldecode the cookie it receives and therefore stops it turning the + into a space e.g.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 Servlet 2.3//EN' 'file:///net/wajra.india.sun.com/export/share/dtd/sun-web-app_2_3-1.dtd'>
    <sun-web-app>
       <property name="encodeCookies" value="false"/>
       <session-config>
          <session-manager/>
       </session-config>
       <jsp-config/>
    <property name="allowLinking" value="true" />
    </sun-web-app>Regards,
    Shane.

  • Load Balancing Directory Servers with Access Manager - Simple questions

    Hi.
    We are in the process of configuring 2 Access Manager instances (servers) accessing the same logical LDAP repository (comprising physically of two Directory Servers working together with Multi-Master Replication configured and tested) For doing this, we are following guide number 819-6258.
    The guide uses BigIP load balancer for load balancing the directory servers. However, we intend to use Directory Proxy Server. Since we faced some (unresolved) issues last time that we used DPS, there are some simple questions that I would be very grateful to have answers to:
    1. The guide, in section 3.2.10 (To configure Access Manager 1 with the Directory Server load balancer), talks about making changes at 4 places, and replacing the existing entry (hostname and port) with the load balancer's hostname and port (assuming that the load balancer has already been configured). It says that changes need not be made on Access Manager 2 since the LDAPs are in replication, and hence changes will be replicated at all places. However, the guide also states that changes have to be made in two files, namely AMConfig.properties, and the serverconfig.xml file. But these changes will not be reflected on Access Manager 2, since these files are local on each machine.
    Question 1. Do changes have to be made in AMConfig.properties and serverconfig.xml files on the other machine hosting Access Manager 2?
    Question 2: What is the purpose of putting these values here? Specifically, what is achieved by specifying the Directory server host and port in AMConfig.properties, as well as in serverconfig.xml?
    Question 3. In the HTTP console, there is the option of specifying multiple primary LDAP servers, as well as multiple secondary LDAP servers. What is the purpose of these? Are secondary servers attempted when none of the list in the primary list are accessible? Also, if there are multiple entries in the primary server list, are they accessed in a round robin fashion (hereby providing rudimentary load balancing), or are other servers accessed only when the one mentioned first is not reachable etc.?
    2. Since I do not have a load balancer setup yet, I tried the following deviation to the above, which, according to me, should have worked. If viewed in the HTTP console, LDAP / Membership / MSISDN and Policy configuration all pointed to the DS on host 1. When I changed all these to point to the directory server on host 2 (and made AMConfig.properties and serverconfig.xml on host 1 point to DS of host 2 as well), things should have worked fine, but apparently Access manager 1 could not be started. Error from Webserver:
    [14/Aug/2006:04:30:36] info (13937): WEB0100: Loading web module in virtual server [https-machine_1_FQDN] at [search]
    [14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Exception in thread "EventService" java.lang.ExceptionInInitializerError
    [14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.iplanet.services.ldap.event.EventServicePolling.run(EventServicePolling.java:132)
    [14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at java.lang.Thread.run(Thread.java:595)
    [14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Caused by: java.lang.InterruptedException
    [14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.sun.identity.sm.ServiceManager.<clinit>(ServiceManager.java:74)
    [14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: ... 2 more
    In effect, AM on 1 did not start. On rolling back the changes, things again worked like previously.
    Will be really grateful for any help / insight / experience on dealing with the above.
    Thanks!

    Update to the above, incase anyone is reading:
    We setup a similar setup in Windows, and it worked. Here is a detailed account of what was done:
    1. Host 1: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
    All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST1:389)
    2. Host 2: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
    All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST2:389)
    3. Host 1: Started replication. Set to Master
    4. Host 2: Started replication. Set to Master
    5. Host 1: Setup replication agreement to Host 2
    6. Host 2: Setup replication agreement to Host 1
    7. Initiated the remote replica from Host 1 ----> Host 2
    Note that since default installation uses abc.....xyz as the encryption key, setting this to same was not an issue.
    9. Started webserver for Host 1 and logged into AM as amadmin.
    10. Added Host 2 FQDN in DNS Aliases / Realms
    11. Added http://HOST2_FQDN:80 in the Platform server (instance) list.
    12. Started Host 2 webserver. Logged in AM on Host 2, things worked fine.
    At this stage, note the following:
    a) Host 1:
    AMConfig.properties file has
    com.iplanet.am.directory.host=host1_FQDN
    and
    com.iplanet.am.directory.port=389
    serverconfig.xml has:
    <Server name="Server1" host="host1_FQDN" port="389" type="SIMPLE" />
    b) Host 2:
    AMConfig.properties file has
    com.iplanet.am.directory.host=host2_FQDN
    and
    com.iplanet.am.directory.port=389
    serverconfig.xml has:
    <Server name="Server1" host="host2_FQDN" port="389" type="SIMPLE" />
    c) If one logs into AM, and checks LDAP servers for LDAP / Policy Configuration / Membership etc services, they all contain Host2_FQDN:389 (which makes sense, since replica 2 was initialized from 1)
    Returning back to the configuations:
    13. On Host 1, login into the Admin server console of the Directory server. Navigate to the DPS, and confgure the following:
    a) Network Group
    b) LDAP servers
    c) Load Balancing
    d) Change Group
    e) Action on-bind
    f) Allow all actions (permit modification / deletion etc.).
    g) any other configuations required - Am willing to give detailed steps if someone needs them to help me / themselves! :)
    So now, we have DPS configured and running on Host1:489, and distributing load to DS1 and DS2 on a 50:50 basis.
    14. Now, log into AM on Host 1, and instead of Host1_fqdn:389 (for DS) in the following places, specify Host1_fqdn:489 (for the DPS)--
    LDAP Authentication
    MSISDN server
    Membership Service
    Policy configuation.
    Verified that this propagated to the Policy Configuration service and the LDAP authentication service that are already registered with the default organization.
    15. Log out of AM. Following the documentation, modify directory.host and directory.port in AMConfig.properties to point to Host 1_FQDN and 489 respectively. Make this change in AMConfig.properties of both Host 1 as well as 2.
    16. Edit serverconfig.xml on both hosts, and instead of they pointing to their local directory servers, point both to host1_FQDN:489
    17. When you start the webserver, it will refuse to start. Will spew errors such as:
    [https-host1_FQDN]: Sun ONE Web Server 6.1SP5 B06/23/2005 17:36
    [https-host1_FQDN]: info: CORE3016: daemon is running as super-user
    [https-host1_FQDN]: info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_04] from [Sun Microsystems Inc.]
    [https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amserver]
    [https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
    [https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [ampassword]
    [https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
    [https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amcommon]
    [https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amconsole]
    [https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
    [https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [search]
    [https-host1_FQDN]: warning: CORE3283: stderr: netscape.ldap.LDAPException: error result (32); matchedDN = dc=sun,dc=com; No such object (DN changed)
    [https-host1_FQDN]: warning: CORE3283: stderr: Got LDAPServiceException code=-1
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getConnection(DSConfigMgr.java:357)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewFailoverConnection(DSConfigMgr.java:314)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewConnection(DSConfigMgr.java:253)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:184)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:194)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.initLdapPool(DataLayer.java:1248)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.(DataLayer.java:190)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:215)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:246)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:156)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.(SMSLdapObject.java:124)
    [https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    [https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    [https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    [https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
    [https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance0(Class.java:350)
    [https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance(Class.java:303)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.SMSEntry.(SMSEntry.java:216)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ServiceSchemaManager.(ServiceSchemaManager.java:67)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetector.java:219)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.(AMClientDetector.java:94)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:322)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:120)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3271)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3747)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
    [https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
    [https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
    [https-host1_FQDN]: failure: WebModule[amserver]: WEB2783: Servlet /amserver threw load() exception
    [https-host1_FQDN]: javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
    [https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
    [https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
    [https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
    [https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
    [https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
    [https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
    [https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
    [https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
    [https-host1_FQDN]: ----- Root Cause -----
    [https-host1_FQDN]: java.lang.NullPointerException
    [https-host1_FQDN]: at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
    [https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
    [https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
    [https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    [https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
    [https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
    [https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
    [https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
    [https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
    [https-host1_FQDN]:
    [https-host1_FQDN]: info: HTTP3072: [LS ls1] http://host1_FQDN:58080 [i]ready to accept requests
    [https-host1_FQDN]: startup: server started successfully
    Success!
    The server https-host1_FQDN has started up.
    The server infact, didn't start up (nothing even listening on 58080).
    However, if AMConfig.properties is left as it originally was, and only serverconfig.xml files were changed as mentioned above, web servers started fine, and things worked all okay. (Alright, except for some glitches when viewed in /amconsole. If /amserver/console is accessed, all is good. Can this mean that all is still not well? I am not sure).
    So far so good. Now comes the sad part. When the same is done on Solaris 9, things dont work. You continue to get the above error, OR the following error, and the web server will refuse to start:
    Differences in Solaris and Windows are as follows:
    1. Windows hosts have 1 IP and hostname. Solaris hosts have 3 IPs and hostnames (for DS, DPS, and webserver).
    No other difference from an architectural perspective.
    Any help / insight on why the above is not working (and why the hell does the documentation seem so sketchy / insecure / incorrect).
    Thanks a bunch!

  • Installing Access Manager under App Server platform

    We have done an install of Access Manager 2005Q1 under App Server platform edition 2005Q1 (v8.1) on Linux Redhat Enterprise edition (v3).
    When starting up Access Manager, we get a NoClassDefFound exception. Some postings mention some issues with the SUN mobile access, and suggest uninstalling / reinstalling, but these seem to apply to Solaris only. We have had no luck with this suggestion with Linux.
    Does anyone have any other suggestions?
    Thanx,
    GB
    [#|2005-09-14T10:50:34.118-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterpri
    se.system.container.web|_ThreadID=10;|WebModule[/a
    mserver]Exception starting filter amlcontroller
    java.lang.NoClassDefFoundError
    at com.iplanet.services.ldap.LDAPUser.getPasswd(LDAPUser.java:117)
    at
    com.iplanet.services.ldap.ServerInstance.getPasswd(ServerInstance.java:128)
    at
    com.sun.identity.security.ServerInstanceAction.run(ServerInstanceAction.java
    :92)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:210)
    at
    com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:143)
    at
    com.sun.identity.sm.ldap.SMSLdapObject.<init>(SMSLdapObject.java:118)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
    Method)
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
    sorImpl.java:39)
    at
    sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
    torAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at java.lang.Class.newInstance0(Class.java:308)
    at java.lang.Class.newInstance(Class.java:261)
    at com.sun.identity.sm.SMSEntry.<clinit>(SMSEntry.java:116)
    at
    com.sun.identity.sm.ServiceSchemaManager.<clinit>(ServiceSchemaManager.java:
    67)
    at
    com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetecto
    r.java:219)
    at
    com.iplanet.am.util.AMClientDetector.<clinit>(AMClientDetector.java:94)
    at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
    at
    org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilter
    Config.java:229)
    at
    org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFil
    terConfig.java:312)
    at
    org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterCon
    fig.java:83)
    at
    org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:38
    81)
    at
    org.apache.catalina.core.StandardContext.start(StandardContext.java:4528)
    at com.sun.enterprise.web.WebModule.start(WebModule.java:241)
    at
    org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1086)
    at
    org.apache.catalina.core.StandardHost.start(StandardHost.java:833)
    at
    org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1086)
    at
    org.apache.catalina.core.StandardEngine.start(StandardEngine.java:483)
    at org.apache.catalina.startup.Embedded.start(Embedded.java:894)
    at com.sun.enterprise.web.WebContainer.start(WebContainer.java:707)
    at
    com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:507)
    at
    com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifec
    ycle.java:54)
    at
    com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java
    :300)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]

    Everytime I click the Access Manager in the JES 2005Q4installer the directory server would click itself. Unchecking this prompted me for a remote repository which worked.
    I wasn't able to get the install to complete with the state file, it stopped before configuring access manager.

  • Error while accessing Access Manager

    Hi All,
    I am getting the following error after configuring access manager and restarting the web server.
    [25/May/2006:18:14:16] info ( 1724): CORE1116: Sun Java System Web Server 6.1SP5 B01/15/2006 23:04
    [25/May/2006:18:14:30] info ( 1724): HTTP3072: [LS ls1] http://GDYESSER33609.wipro.com:13004 ready to accept requests
    [25/May/2006:18:14:30] info ( 1724): CORE3274: successful server startup
    [25/May/2006:18:15:29] warning ( 1724): CORE3283: stderr: Exception in thread "amStats" java.lang.ExceptionInInitializerError
    [25/May/2006:18:15:29] warning ( 1724): CORE3283: stderr:      at com.sun.identity.authentication.service.AuthStatsListener.printStats(AuthStatsListener.java:56)
    [25/May/2006:18:15:29] warning ( 1724): CORE3283: stderr:      at com.iplanet.am.util.StatsRunner.run(StatsRunner.java:91)
    [25/May/2006:18:15:29] warning ( 1724): CORE3283: stderr: Caused by: java.lang.NullPointerException
    [25/May/2006:18:15:29] warning ( 1724): CORE3283: stderr:      at com.iplanet.services.cdm.ClientsManager.getDefaultInstance(ClientsManager.java:108)
    [25/May/2006:18:15:29] warning ( 1724): CORE3283: stderr:      at com.sun.identity.authentication.service.AuthUtils.<clinit>(AuthUtils.java:199)
    I have configured and restarted the web server, when i try to access the access manager I get the above error. Someone please respond at the earliest.
    Thanks.

    Hi Tanya,
    Thank you for posting in Windows Server Forum.
    From which device you are trying to access RemoteApp program?
    For getting any remote session or accessing RemoteApp the user must be added under “Remote Desktop Users” local group. So please under user under that group and verify. 
    Also add the user under System>Remote Settings>Remote Tab>Allow remote connection to this computer and add the user under that. Now after performing this above steps verify whether user can login remotely.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Sun Java System Access Manager 7.1 config. failed during installation

    {color:#0000ff}Hi,
    I have installed sun java communication suite 5 on a single host on sun solaris 10.
    I have installed required packages and it works fine.
    But as per organization need, I have to change domain name.
    So i have uninstalled everything and tried to install again with new domain name.
    I have made proper entries in hosts file and resolve.conf file.
    But duing the first phase of installation only , i failed in configuring access manager 7.1
    I have also cerate same scenario in my test environment, but everytime i face the same error.
    and sun java access manager 7.1 fails in first stage of installation only.
    So would like to know the proper installation procedure while i change the domain name on same hardware...
    I have checked both installation logs & summary logs.
    But no error, no failed , no severe.
    Attached is the summary of installation logs.
    Summary Logs :
    Installation Summary Report
    Install Summary
    Sun Java(TM) Communications Suite : Installed
    Sun Java(TM) System Web Server 7.0 : Installed, Configured
    Java DB : Installed, Configure After Install
    Sun Java(TM) System Message Queue 3.7 UR1 : Installed
    Sun Java(TM) System Monitoring Console 1.0 : Installed, Configure After Install
    Sun Java(TM) System Directory Preparation Tool : Installed
    Sun Java(TM) System Directory Server Enterprise Edition 6.0 : Installed, Configured
    Sun Java(TM) System Access Manager 7.1 : Installed, Configuration Failed
    Sun Java(TM) System Messaging Server 6.3 : Installed, Configure After Install
    Sun Java(TM) System Communications Express 6 : Installed, Configure After Install
    Communication Services Delegated Administrator : Installed, Configure After Install
    Configuration Data
    Sun Java(TM) System Web Server 7.0 :
    Web Server Instance installation Directory : /var/opt/SUNWwbsvr7
    Web Server installation Directory : /opt
    Web Server Administration Server Host : RADAGWMSG221.myreliancemail.com
    Web Server Admin Server Mode : true
    Web Server only CLI installation : false
    Sun Java(TM) System Directory Preparation Tool :
    Directory Preparation Tool Installation Directory : /opt/SUNWcomds
    Sun Java(TM) System Directory Server Enterprise Edition 6.0 :
    Directory Server Installation Directory : /opt/SUNWdsee
    Sun Java(TM) System Access Manager 7.1 :
    Access Manager Installation Directory : /opt
    Access Manager Protocol : http
    Access Manager Port : 80
    LDAP User ID : amldapuser
    Administrator User ID : amAdmin
    Web Container : WebServer
    Access Manager Web Server Host Name : RADAGWMSG221.myreliancemail.com
    Access Manager Web Server Instance Directory : /var/opt/SUNWwbsvr7/https-RADAGWMSG221.myreliancemail.com
    Access Manager Web Server Port : 80
    Access Manager Console Host (for Existing console) : RADAGWMSG221.myreliancemail.com
    Access Manager Console Deploy URI : amconsole
    Access Manager Password Deploy URI : ampassword
    Access Manager Host : RADAGWMSG221.myreliancemail.com
    Access Manager Console Port(for Existing console) : 80
    Access Manager Services Deploy URI : amserver
    Access Manager Cookie Domain List : .myreliancemail.com
    Access Manager Common Domain Deploy URI : amcommon
    Access Manager Directory Server Host Name : RADAGWMSG221
    Access Manager Directory Server Host : RADAGWMSG221.myreliancemail.com
    Access Manager Directory Server Port : 389
    Access Manager Directory Root Suffix : o=rmail
    Access Manager Directory Manager DN : cn=Directory Manager
    Organization Marker Object Class : sunISManagedOrganization
    User Marker Object Class : inetorgperson
    Organization Naming Attribute : o
    User Naming Attribute : uid
    Sun Java(TM) System Messaging Server 6.3 :
    Messaging Server Installation Directory : /opt/SUNWmsgsr
    Sun Java(TM) System Communications Express 6 :
    Communications Express Installation Directory : /opt/SUNWuwc
    Communication Services Delegated Administrator :
    Communication Services Delegated Administrator Installation Directory : /opt/SUNWcomm
    {color}

    Rushi-Reliance wrote:
    Kindly let us know how to proceed further as we are waiiting some reply from your team.As I already advised in your previous posting (http://forums.sun.com/thread.jspa?threadID=5359095), you are best off re-installing solaris from scratch and installing Communication Suite 6 update 1 if you cannot get Access Manager 7.1 configured.
    Regards
    Shane.

  • Sun access Manager session failover

    Hi,
    I am trying to install Sun Access Manager (2005Q1) with Session failover. I have hardware load balancer under which i have configuring Access Manager on two seperate boxes.
    For session failover i have configured Berkelay database on both system but am unable to start the database.
    Now i got the information that Access Manager 6.1 does not support session failover.
    Can anyone confirm if access manager 6.1 supports failover or we need to upgrade it?
    Thx in advance.
    ASN
    Message was edited by:
    asn123

    One clarification. AM 6.1 did have session failvoer feature. But it was container dependent. It used container features to provide this. Each container had its on configuration. It was made independent of the containers in AM 6.3 release. I would stonglry recommend using AM 6.3 or above if you are using session failover.
    shivaram

  • Not able to install Access Manager 7.1 in Legacy Mode with amsamplesilent

    HI All,
    I am building test setup on Solaris Zones.Recently it was patched to following level *5.10 Generic_138888-03*
    I am trying to install Access Manager in Legacy mode with amsamplesilent file.
    SERVER_NAME=sesamesso1
    SERVER_HOST=$SERVER_NAME.example.com
    SERVER_PORT=80
    ADMIN_PORT=8989
    DS_HOST=ssoldap1.example.com
    DS_DIRMGRPASSWD=l0cuz123
    ROOT_SUFFIX="dc=example,dc=com"
    SM_CONFIG_BASEDN=$ROOT_SUFFIX
    ADMINPASSWD=l0cuz123
    AMLDAPUSERPASSWD=l0cuz123am
    DEBUG_LEVEL=error
    DEBUG_DIR=/logs/sso/debug
    COOKIE_DOMAIN=.example.com
    AM_ENC_PWD=""
    NEW_OWNER=wbsrv
    NEW_GROUP=javaes
    PAM_SERVICE_NAME=other
    WEB_CONTAINER=WS
    AM_REALM=disabledBut AM is getting installed in Realm Mode. I need to install portal server with this Access Manager.
    please confirm,I am doing any mistake in my installation and please let me know whether portal server supports access manager realm mode or not.
    Thanks in Advance
    Madhu

    Thanks for the reply.
    I will give a try to install sun portal server 7.2 with accessmanager 7.1 in realm mode.Before patch updation my solaris sparc OS level was *5.10 Generic_118833-36* and I was able to install access manager 7.1 in legacy mode
    Is there any thing to be done for new patch level(*5.10 Generic_138888-03*) to install access manager 7.1 in legacy mode.
    Please let me know
    Thanks
    Madhu

  • Installing Access Manager and Directory Server

    Can I install the Access Manager 2005Q4 without installing the directory server?
    The products selected for installation have dependency requirements or installation options as indicated below.
    Sun Java(TM) System Directory Server 5 2005Q4
    ------------------------------------------------------------------------

    Everytime I click the Access Manager in the JES 2005Q4installer the directory server would click itself. Unchecking this prompted me for a remote repository which worked.
    I wasn't able to get the install to complete with the state file, it stopped before configuring access manager.

  • Time-based log rotation in Access Manager

    Hi,
    We have configured Access Manager for size-based log rotation. So the log files undergo rotation whenever the log files reach the size limit specified.
    But I would like to know if the Access Manager Logging module provides options for:
    Time-based Log Rotation : so that log files get rotated on a periodic basis.
    Log File Name Customization: At present the old log files get suffixed with -n (e.g. amPolicy.access-1), where 'n' denotes the number in the rotation sequence . Is it possible to configure Access Manager to generate a timestamp as a suffix for old log files.
    e.g. amPolicy.access-05_29_2005.
    Regards,
    Chetan Desai

    The AM admin guide (ftp://docs-pdf.sun.com/817-7647/817-7647.pdf) page 335 has listed all available Logging attribute. It doesn't have the time based parameter and time stamp suffix. If you wish to have those features, please contact Sun Identity sales for filing a RFE. Also checking Logging API and see whether you can program yourself to achieve those features. (see page 47 of 817-7650.pdf) Jerry

  • How to configure Node manager on Linux on ssl port

    Hi,
    I have installed SOA BPM 11.1.1.3 on linux with ssl enabled. I am trying to configure Node Manager but it's not working.
    Here are the steps I did to configure.
    1. Created a machine
    2. Added managed servers to the machine i.e. soa,bam
    3. Enroll domain using nmEnroll using
    cd $BEA_HOME/user_projects/domains/<domain_name>/bin/
    . setDomainEnv.sh
    java weblogic.WLST
    wls> connect(’weblogic’,'weblogic1’, ‘t3://mymachine.mydomain:7001’)
    wls> nmEnroll(’$BEA_HOME/user_projects/domains/<domain_name>’, ‘$BEA_HOME/wlserver_<version>/common/nodemanager’)
    here 7001 is the admin server non-ssl port but when I try 7002 ssl port it doesn't connect. But I need to enroll it on ssl port as I have ssl enabled.
    4. reset the node manager user/password same as weblogic console
    5. started the node manager using $WL_HOME\server\bin\startNodeManager.sh
    But when I log back into console and try to start my manage server it gives the following error
    SEVERE: java.io.FileNotFoundException: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/./config/jps-config.xml (No such file or directory)
    <Aug 6, 2010 5:30:16 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.I did not add my Admin server to be part of the machine.
    Any help if I am missing anything or doing anything wrong.
    Thanks

    Hi,
    Do I need to add Admin Server also part of the Machine where I added bam,soa servers. I tried again following the steps but gets the below error again. Appreciate if someone can list the steps as the docs are a bit vague:
    <Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh >
    Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh
    <Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Working directory is '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain'>
    Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
    '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/servers/bam_server1/logs/bam_server1.out'
    <Aug 6, 2010 6:14:02 PM> <INFO> <wcbpm_domain> <bam_server1> <Server failed during startup so will not be restarted>
    Aug 6, 2010 6:14:02 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Aug 6, 2010 6:14:02 PM> <WARNING> <Exception while starting server 'bam_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
            at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
            at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
            at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
            at weblogic.nodemanager.server.Handler.run(Handler.java:70)
            at java.lang.Thread.run(Thread.java:619)
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    Unknown option or illegal argument: -XX:+UseParallelGC.
    Please check for incorrect spelling or review documentation of startup options.
    Could not create the Java virtual machine.
    <Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <Waiting for the process to die: 590>
    <Aug 6, 2010 6:14:02 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Don't know if I hve missed any steps in node manager configuration.
    Thanks

Maybe you are looking for