Psconsole

I know it's not supported, but does anyone have psconsole working on an application server that's not Sun Appserver or Sun WebServer? I'd like to get it working on BEA WL 8.1 so we have only one application environment to support. Just wondering what kind of pain I'm in for.
Thanks in advance
--Frank                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

No it does not work. BEA WL 8.x bundles an older version of JMX and psconsole requires newer version. Even if the new version of JMX is bundled into the psconsole war file WL ignores it. So due to the JMX version mismatch psconsole cannot be made to work on WL8.x
_raju                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Similar Messages

  • Psconsole  Authentication Failed, Please reenter username and password

    Hi,
    I have JES5 installed ( App server + Directory server + Portal server + Access manager) on a windows 2003 server with Oracle 10g. After the installation i was able to access the amconsole, psconsole, and the admin console without any errors.
    After the server was restarted, i started the application server and the directory server (dsadm start) and now i can login to admin console and /amconsle and also to the /portal/dt, but i am not able to login to /psconsole.
    i have used the default login details(amadmin) login for both the /amconsole and the /psconsle, /amconsole logins sucessfully but /psconsole gives me the error "Authentication Failed, Please reenter username and password"
    the log details of portal.admin.console.0.0.log are:
    [#|2008-01-08T12:13:58.672+0530|SEVERE|SJS Portal Server|debug.com.sun.portal.admin.console|ThreadID=21; ClassName=com.sun.portal.admin.console.common.PSBaseBean; MethodName=log; |Failed to authenticate with JMX Server: LoginBean.login()
    javax.management.remote.JMXProviderException: Connection refused: connect
         at com.sun.cacao.agent.impl.CacaoJmxConnectorProvider.newJMXConnector(CacaoJmxConnectorProvider.java:388)
         at javax.management.remote.JMXConnectorFactory.getConnectorAsService(JMXConnectorFactory.java:415)
         at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:307)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
         at com.sun.portal.admin.common.util.AdminUtil.getConnector(AdminUtil.java:813)
         at com.sun.portal.admin.common.util.AdminClientUtil.getJMXConnector(AdminClientUtil.java:113)
         at com.sun.portal.admin.common.util.AdminClientUtil.getJMXConnector(AdminClientUtil.java:139)
         at com.sun.portal.admin.common.util.AdminClientUtil.getJMXConnector(AdminClientUtil.java:163)
         at com.sun.portal.admin.console.common.LoginBean.JMXConnect(LoginBean.java:287)
         at com.sun.portal.admin.console.common.LoginBean.authenticate(LoginBean.java:256)
         at com.sun.portal.admin.console.common.LoginBean.login(LoginBean.java:230)
         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.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:146)
         at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:92)
         at javax.faces.component.UICommand.broadcast(UICommand.java:332)
         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:287)
         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:401)
         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:95)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
         at sun.reflect.GeneratedMethodAccessor139.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at com.sun.web.ui.util.UploadFilter.doFilter(UploadFilter.java:203)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:210)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
         at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:235)
         at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2114)
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:516)
         at java.net.Socket.connect(Socket.java:466)
         at java.net.Socket.<init>(Socket.java:366)
         at java.net.Socket.<init>(Socket.java:179)
         at com.sun.jmx.remote.socket.SocketConnection.connect(SocketConnection.java:94)
         at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:69)
         at javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:177)
         at javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:119)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at com.sun.cacao.agent.JmxClient.getUnknownJmxClientConnection(JmxClient.java:904)
         at com.sun.cacao.agent.impl.CacaoJmxConnectorProvider.newJMXConnector(CacaoJmxConnectorProvider.java:362)
         ... 52 more
    Also, when i try to start the cacaoadm or check for the status i get the Perl lib version (v5.8.3) doesn't match executable version (v5.8.8) error.
    i have JES5 and Oracle 10G installed on a windows 2003 server,
    can you please let me know what do i have to correct here.
    C:\Program Files\Sun\JavaES5\share\cacao_2\bin>cacaoadm.bat status
    Perl lib version (v5.8.3) doesn't match executable version (v5.8.8) at E:\oracle
    \product\10.2.0\db_1\perl\5.8.3\lib/MSWin32-x86-multi-thread/Config.pm line 32.
    Compilation failed in require at E:\oracle\product\10.2.0\db_1\perl\5.8.3\lib/Fi
    ndBin.pm line 97.
    BEGIN failed--compilation aborted at E:\oracle\product\10.2.0\db_1\perl\5.8.3\li
    b/FindBin.pm line 97.
    Compilation failed in require at C:\PROGRA~1\Sun\JavaES5\share\cacao_2\lib\tools
    \scripts\cacaoadm.pl line 17.
    BEGIN failed--compilation aborted at C:\PROGRA~1\Sun\JavaES5\share\cacao_2\lib\t
    ools\scripts\cacaoadm.pl line 17.
    Thanks in advance
    Regards
    Gani

    Hi,
    depending on the cacao version used. The only authorized user (user allowed to use cacao) may be a privileged user (user part of local administrator group).
    to know the version of cacao just run "cacaoadm -V" .
    from 2.1 , non privileged user can install their own copy of cacao.
    Your case (login on pconsole failing) may be a credential
    probleme. did you check the password given for the connection ?
    For the service part (enabling cacao) you must not touch the configuration. Everything is done using the command line.
    you should not modify information set in the service manager.
    just use the command line "cacaoadm enable -f <password file>". the Password file must contain the password of the Administrator who installed cacao.
    hope this helps

  • Psconsole fails to redirect

    We have installed Portal Server 7.2 in solaris 10 on sparc and deployed all our portlets.
    After some time, when we try to access psconsole, the IE browser says 'redirecting' and waits infinitely.
    We cannot see the login page.
    Any idea how to overcome this problem?
    We have Sun App Server, Directory Server, Access Manager, installed in the same machine.
    Portal itself is working great. But cannot see the psconsole login page.
    Thanks in advance.

    Hi,
    I recommend to use the code below to see if the issue still occurs:
    onclick=”javascript: if (!Page_ClientValidate()) return false; {ddwrt:GenFireServerEvent(‘__commit;__redirect={/teams/ho3/sitepages/ARBThankYou.aspx }‘)}”
    You can also redirect the InfoPath form by changing the source URL value in the URL.
    http://mysharepointexp.blogspot.com/2011/12/redirecting-infopath-form-after-submit.html
    More reference:
    http://blogs.technet.com/b/sharepointwarrior/archive/2012/03/16/sp-2010-how-to-redirect-infopath-form-to-a-custom-thank-you-page.aspx
    Thanks,
    Victoria
    Forum 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 Subscriber Support, contact
    [email protected]
    Victoria Xia
    TechNet Community Support

  • Create a Different instance with Separte amserver,psconsole,directory serve

    Hi
    I have created different instance in same node using webserver 7.0(Sun Java Sytem portal Server 7.1 Update 2). i want to know about how to create different instance each instance have separate acessmanager, psconsole and directory server, is it possible?? i am using sun java sytem portal server 7.1 update 2.
    Can you any one please tell me the further steps..
    Cheers..
    Sekar M

    This is possible but not easy to explain in a few lines on a forum. You may want to consider using Solaris 10 zones instead and just put each stack into a separate zone.

  • PS 7.1 (JES 5u1-Linux) - Can't deploy psconsole

    Hi,
    I've installed Portal 7.1 for Redhat Linux (JES 5 u1) using the Application Server as the web container. I know from reading the forums that the installer doesn't install the PSconsole and that it needs to be deployed manually after installation. The problem is that I can't deploy it.
    Note: After trying this, I then applied the patch 124303-11 (ps71u2), and tried again but it produced the same errors.
    Here's how I try to deploy the psconsole.war:
    /opt/sun/portal/bin/psadmin deploy-portlet -u amadmin -f /opt/sun/passfile -p portal1 -g /opt/sun/portal/admin/psconsole.war
    Invalid Portlet war file. Possible reason can be error reading WEB-INF/portlet.xml from portlet war file,
    please check the cli debug logs or MBean debug logs for more details.
    Here's a snip from the log file /var/opt/sun/portal/logs/admin/portal.0.0.log:
    <snip>
    [#|2008-08-28T16:33:34.762-0400|SEVERE|SJS Portal Server|debug.com.sun.portal.portlet.admin.mbeans|ThreadID=14; ClassName=com.sun.portal.portlet.admin.mbeans.PortletAdmin;
    MethodName=deploy; |PSPL_CSPPAM0004 : PortletDeployerException:
    com.sun.portal.portlet.admin.mbeans.tasks.PortletDeployerException: invalidWar
    at com.sun.portal.portlet.admin.mbeans.tasks.PDDeploy.process(Unknown Source)
    at com.sun.portal.portlet.admin.mbeans.PortletAdmin.deploy(Unknown Source)
    at com.sun.portal.portlet.admin.mbeans.PortletAdmin.deployAll(Unknown Source)
    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)
    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(Unknown Source)
    at com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:736)
    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:266)
    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: java.lang.NullPointerException
    at java.util.zip.ZipFile.getInputStream(ZipFile.java:286)
    at java.util.jar.JarFile.getInputStream(JarFile.java:387)
    ... 26 more
    |#]
    </snip>
    and snip from log file /var/opt/sun/portal/logs/admin/portal.admin.cli.0.0.log:
    <snip>
    [#|2008-08-28T16:33:34.782-0400|SEVERE|SJS Portal Server|debug.com.sun.portal.admin.cli.commands|ThreadID=10; ClassName=com.sun.portal.admin.cli.commands.portlet.DeployPort
    letCommand; MethodName=runCommand; |PSALI_CSPACCP0001:Exception
    com.sun.portal.admin.common.PSMBeanException: java.lang.NullPointerException
    at com.sun.portal.portlet.admin.mbeans.PortletAdmin.deploy(Unknown Source)
    at com.sun.portal.portlet.admin.mbeans.PortletAdmin.deployAll(Unknown Source)
    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)
    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(Unknown Source)
    at com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:736)
    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:266)
    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: java.lang.NullPointerException
    at java.util.zip.ZipFile.getInputStream(ZipFile.java:286)
    at java.util.jar.JarFile.getInputStream(JarFile.java:387)
    at com.sun.portal.portlet.admin.mbeans.tasks.PDDeploy.process(Unknown Source)
    ... 25 more
    |#]
    </snip>
    Does anybody have any suggestions?
    Thanks,
    Kevin

    I believe you are simply using the incorrect port number. Port 4849 is the port reserved for use by the App Server Domain Administration Server console. A default installation of Sun App Server creates another instance using ports 8080/8181 for HTTP/S respectively. You should be able to reach psconsole with:
    http://host.domain:8080/psconsole
    https://host.domain:8181/psconsoleLog in using the amadmin account credentials that were configured for Access Manager.
    You can also run psadmin list-portals to see where the portal was deployed.
    - Jim

  • Psconsole on windows xp

    Hello,
    I have a problem calling psconsole in an Windows XP environment, if I start the portal server from an usual windows user account. The windows user is in the administrator group.
    The login of psconsole always states Authentication Failed - Please reenter username and password. But the login data where valid.
    If I start the server from windows user "Administrator" all seams to work fine.
    Even starting the server using "run as... Administrator" does not work.
    For several circumstances I have to work as usual user and not as Administrator on my windows system.
    Can anybody give a hint what to do?
    My configuration:
    - Portal Server 7.1 Update 1
    - Java 1.5.0_09
    - Windows XP Sp2

    Hi,
    depending on the cacao version used. The only authorized user (user allowed to use cacao) may be a privileged user (user part of local administrator group).
    to know the version of cacao just run "cacaoadm -V" .
    from 2.1 , non privileged user can install their own copy of cacao.
    Your case (login on pconsole failing) may be a credential
    probleme. did you check the password given for the connection ?
    For the service part (enabling cacao) you must not touch the configuration. Everything is done using the command line.
    you should not modify information set in the service manager.
    just use the command line "cacaoadm enable -f <password file>". the Password file must contain the password of the Administrator who installed cacao.
    hope this helps

  • Deploy psconsole in different container

    Hey All,
    Is it possible to deploy the psconsole to a different container than the portal itself? Both containers would be Sun One Web Server. Just wanted to have them on different web servers.
    Thanks

    You can just deploy the psconsole.war file onto another webcontainer instance.
    Once you have psconsole on the new webcontainer instance functional, you can undeploying the psconsole webapplication from the webcontainer instance running the portal webapp.. using the webcontainer undeploy tool.

  • Failure to login to PSConsole

    Ehlo all,
    i have an instance of PS7 running on Solaris 10 SPARC machine. For days before, it work ok.
    I can login to amconsole as well as psconsole using amadmin account.
    However, today, i can not. I am still able to login to amconsole, but can not to psconsole with the same user/pwd.
    Log from
    /var/opt/SUNWportal/logs/admin/portal.admin.console.0.0.log
    are attached below.
    No idea, i have restart the machine and the process ... Any pointer to solution is, for sure, appreciated.
    Cheers,
    Eko Budhi S
    LOG
    [#|2006-07-18T19:08:13.031+0700|SEVERE|SJS Portal Server|debug.com.sun.portal.admin.console|ThreadID=20; ClassName=com.sun.portal.admin.console.common.PSBaseBean; MethodName=log; |Failed to authenticate with JMX Server: LoginBean.login()
    java.lang.SecurityException: java.lang.SecurityException: Authentication failed: Error occurred while creating SSOToken.
    at com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:337)
    at com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:144)
    at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:71)
    at javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:177)
    at javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:119)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
    at com.sun.cacao.agent.JmxClient.getUnknownJmxClientConnection(JmxClient.java:876)
    at com.sun.portal.admin.common.util.AdminClientUtil.getJMXConnector(AdminClientUtil.java:114)
    at com.sun.portal.admin.common.util.AdminClientUtil.getJMXConnector(AdminClientUtil.java:140)
    at com.sun.portal.admin.common.util.AdminClientUtil.getJMXConnector(AdminClientUtil.java:164)
    at com.sun.portal.admin.console.common.LoginBean.JMXConnect(LoginBean.java:273)
    at com.sun.portal.admin.console.common.LoginBean.authenticate(LoginBean.java:242)
    at com.sun.portal.admin.console.common.LoginBean.login(LoginBean.java:216)
    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.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
    at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
    at javax.faces.component.UICommand.broadcast(UICommand.java:312)
    at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:267)
    at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:381)
    at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:75)
    at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
    at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
    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 org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
    at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
    at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
    at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at com.sun.web.ui.util.UploadFilter.doFilter(UploadFilter.java:203)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
    at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
    at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:226)
    at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2071)

    Problem solved, somehow.
    Actually, we installed 2 access manager instances, which use also 2 directory server which synchronize in multi-master scenario.
    one in jes1.sun.co.id, other in jes2.sun.co.id
    Somehow, the psconsole is required connection (for what ?) to jes2.sun.co.id
    Last time, i comment this line in /etc/hosts
    # 172.16.0.83 jes2.sun.co.id
    No idea yet why like this. I can login now ... I expect somebody give me explanation ...
    Cheers,
    Eko Budhi S

  • Login Failure with psconsole

    I am new with Sun Portal 7.1. I have successfully installed and configure the Portal Server 7.1
    But the moment i log out from the psconsole and try to log in with amadmin and the correct password,
    the system gives me authentication failure.
    Pls help is urgently needed.
    I have the Portal Server running in a SLES 10 VM.
    sco

    hi,
    could you please post any log messages?
    u can give this a shot if u're running on solaris machine.
    here's a checklist.
    1) are you able to login to amconsole? if access manager is deployed on a different container from portal server, start that container (if AM is on web server & PS on appserver, start both)
    2) is your directory server up and running? if not, start it using /opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dsins1
    3) is the cacao running? try cacaoadm status & see if it is. if not, do "cacaoadm start". in case u get command not found, do "/opt/SUNWcacao/bin/cacaoadm start"
    if none of these work, please post log messages so that we can see where the problem lies.

  • PSConsole attribute error

    When trying to update information in my portal console, (changing the desktop type for my new organization), I am faced with this error. Any idea of what to do?
    | ! Failed to save Desktop Attributes. |
    | Template already exists for SunPortalportal1DesktopService |
    My process for creating this new desktop was:
    1) Create a new org
    2) Add all services to this org
    3) Create a user of this new org, give him all services
    4) copy an exisiting desktop to a new location
    5) in psconsole, add the new dn/org
    6) Try to adjust the desktop/containers/upload display profile all to errors.
    What to try now oh Sun experts?

    Could be a bug. Try restarting the cacao server and logging in again
    through the psconsole.
    To restart cacao use:
    /opt/SUNWcacao/bin/cacaoadm restartHope it helps

  • How to get security roles in a JSF portlet

    I need to get the LDAP user-roles available in the Sun Portal Server 7 in my JSF-168 portlet.
    I've added the mapping file, updated the portlet.xml and web.xml, deployed the portlet (psconsole). But the portlet shows the "content not available" error with javax....title title.
    I've probably messed up the descriptors, but I don't see what is wrong. Here they are:
    roleMaps.properties
    cn\=VSM.Administrator,dc\=neco,dc\=cz=Administrator
    web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.4">
      <context-param>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>server</param-value>
      </context-param>
      <context-param>
        <param-name>javax.faces.CONFIG_FILES</param-name>
        <param-value>/WEB-INF/navigation.xml,/WEB-INF/managed-beans.xml</param-value>
      </context-param>
      <context-param>
        <param-name>com.sun.faces.validateXml</param-name>
        <param-value>true</param-value>
      </context-param>
      <context-param>
        <param-name>com.sun.faces.verifyObjects</param-name>
        <param-value>false</param-value>
      </context-param>
      <filter>
        <filter-name>UploadFilter</filter-name>
        <filter-class>com.sun.rave.web.ui.util.UploadFilter</filter-class>
        <init-param>
          <description>
              The maximum allowed upload size in bytes.  If this is set
              to a negative value, there is no maximum.  The default
              value is 1000000.
            </description>
          <param-name>maxSize</param-name>
          <param-value>1000000</param-value>
        </init-param>
        <init-param>
          <description>
              The size (in bytes) of an uploaded file which, if it is
              exceeded, will cause the file to be written directly to
              disk instead of stored in memory.  Files smaller than or
              equal to this size will be stored in memory.  The default
              value is 4096.
            </description>
          <param-name>sizeThreshold</param-name>
          <param-value>4096</param-value>
        </init-param>
      </filter>
      <filter-mapping>
        <filter-name>UploadFilter</filter-name>
        <servlet-name>Faces Servlet</servlet-name>
      </filter-mapping>
      <servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
      </servlet>
      <servlet>
        <servlet-name>ExceptionHandlerServlet</servlet-name>
        <servlet-class>com.sun.errorhandler.ExceptionHandler</servlet-class>
        <init-param>
          <param-name>errorHost</param-name>
          <param-value>localhost</param-value>
        </init-param>
        <init-param>
          <param-name>errorPort</param-name>
          <param-value>25444</param-value>
        </init-param>
      </servlet>
      <servlet>
        <servlet-name>ThemeServlet</servlet-name>
        <servlet-class>com.sun.rave.web.ui.theme.ThemeServlet</servlet-class>
      </servlet>
      <servlet>
        <description>Generated By Sun Java Studio Creator</description>
        <display-name>CreatorPortlet Wrapper</display-name>
        <servlet-name>VSMPortal</servlet-name>
        <servlet-class>org.apache.pluto.core.PortletServlet</servlet-class>
        <init-param>
          <param-name>portlet-class</param-name>
          <param-value>com.sun.faces.portlet.FacesPortlet</param-value>
        </init-param>
        <init-param>
          <param-name>portlet-guid</param-name>
          <param-value>VSMPortal.VSMPortal</param-value>
        </init-param>
      </servlet>
      <servlet-mapping>
        <servlet-name>ExceptionHandlerServlet</servlet-name>
        <url-pattern>/error/ExceptionHandler</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>ThemeServlet</servlet-name>
        <url-pattern>/theme/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>VSMPortal</servlet-name>
        <url-pattern>/VSMPortal/*</url-pattern>
      </servlet-mapping>
      <welcome-file-list>
        <welcome-file>faces/null</welcome-file>
      </welcome-file-list>
      <error-page>
        <exception-type>javax.servlet.ServletException</exception-type>
        <location>/error/ExceptionHandler</location>
      </error-page>
      <error-page>
        <exception-type>java.io.IOException</exception-type>
        <location>/error/ExceptionHandler</location>
      </error-page>
      <error-page>
        <exception-type>javax.faces.FacesException</exception-type>
        <location>/error/ExceptionHandler</location>
      </error-page>
      <error-page>
        <exception-type>com.sun.rave.web.ui.appbase.ApplicationException</exception-type>
        <location>/error/ExceptionHandler</location>
      </error-page>
      <jsp-config>
        <jsp-property-group>
          <url-pattern>*.jspf</url-pattern>
          <is-xml>true</is-xml>
        </jsp-property-group>
      </jsp-config>
         <security-role>
              <role-name>Administrator</role-name>
         </security-role>          
    </web-app>
    portlet.xml
    <?xml version='1.0' encoding='UTF-8' ?>
    <portlet-app xmlns='http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd                         http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd' version='1.0'>
         <portlet>
              <description>Created By Java Studio Creator</description>
              <portlet-name>VSMPortal</portlet-name>
              <display-name>VSMPortal Portlet</display-name>
              <portlet-class>com.sun.faces.portlet.FacesPortlet</portlet-class>
              <init-param>
                   <name>com.sun.faces.portlet.INIT_VIEW</name>
                   <value>/Uctarna.jsp</value>
              </init-param>
              <expiration-cache>0</expiration-cache>
              <supports>
                   <mime-type>text/html</mime-type>
                   <portlet-mode>VIEW</portlet-mode>
              </supports>
              <supported-locale>en</supported-locale>
              <portlet-info>
                   <title>VSMPortal</title>
                   <short-title>VSMPortal</short-title>
                   <keywords>Creator</keywords>
              </portlet-info>
              <security-role-ref>
                   <role-name>Administrator</role-name>
                   <role-link>Administrator</role-link>
              </security-role-ref>          
         </portlet>
    </portlet-app>If I don't use the security-role and security-role-ref tags, the portlet works, and the isUserInRole method obviously doesn't.

    Nobody uses the LDAP roles in a portlet? Anybody knows other thread discussing similar issue (I can't find anything)?

  • Powershell script monitor with encrypted password

    I have created a powershell script based monitor in my management pack and everything is ok but I can't get my credentials work inside the script. I want to open pssession to another computer with my credentials. I have triple checked that my pssession is
    working because I can access it from powershell console.
    This works perfectly at local server from PSconsole:
    $EncryptedPassword ="01000000d08c9ddf0115d1118c7a00c04fc297eb01000000534b2....etc...etc..."
    $pw = convertto-securestring -String $EncryptedPassword
    $cred = new-object System.Management.Automation.PSCredential -argumentlist "MyDOMAIN\MyACCOUNT",$pw
    $s = New-PSSession -ComputerName "MyServer" -Port MyPort -Credential $cred
    But when I run the same lines inside my management pack the convertto-securestring
    does nothing, it just wont convert the encrypted password to secure string!
    I have tried this plain text method and it works
    inside my management pack, but I don't want to use it because you can see the password in plain text:
    ConvertTo-SecureString -String "myPlainTextPassword" -AsPlainText -Force
    This is the $error variable, so it's basically says that I don't have anything in the password secure string variable because the convertion did not work for some reason:
    The argument is null. Provide a valid value for the argument, and then try running the command again. Cannot process argument transformation on parameter 'Credential'. PromptForCredential Exception calling ".ctor" with "2" argument(s):
    "Cannot process argument because the value of argument "password" is null. Change the value of argument "password" to a non-null value." The system cannot find the file specified. Exception calling "SecureStringToBSTR"
    with "1" argument(s): "Value cannot be null. Parameter name: s" The system cannot find the file specified. Exception calling "SecureStringToBSTR" with "1" argument(s): "Value cannot be null. Parameter name: s"
    The system cannot find the file specified. 
    So is there some known issue with SCOM Agent / management pack when you are dealing with convertto-securestring
    function with encrypted passwords?
    I used these methods to encrypt the password: Technet article about encryption

    I got it to work!
      <TypeDefinitions>
        <EntityTypes>
          <ClassTypes>
            <ClassType ID="MyClass" Accessibility="Public" Abstract="false" Base="Windows!Microsoft.Windows.LocalApplication" Hosted="true" Singleton="false" Extension="false"
    />
          </ClassTypes>
        </EntityTypes>
        <SecureReferences>
          <SecureReference ID="MyRunAsAccountProfile" Accessibility="Public" Context="System!System.Entity" />
        </SecureReferences>
    <ScriptBody>param (
      [string]$Username,
      [string]$Password
    $API = new-object -comObject "MOM.ScriptAPI" 
    $PropertyBag = $API.CreatePropertyBag()
    $cred = New-Object System.Management.Automation.PSCredential -Argumentlist @($Username,(ConvertTo-SecureString -String $Password -AsPlainText -Force))
    $s = New-PSSession -ComputerName "myserver" -Credential $cred
    Invoke-Command -Session $s -ScriptBlock { $service = Get-Service -Name Spooler}
    $invcom = Invoke-Command -Session $s -ScriptBlock { $service.status}
    Remove-PSSession -Id $s.Id
    if ($invcom.Value -ne "Running") {
    $PropertyBag.AddValue("State","ERROR") 
    $outputLongLine = "Spooler Service is not running on target server!" 
    $PropertyBag.AddValue("Description", $outputLongLine)
    else {
    $PropertyBag.AddValue("State","OK") 
    $outputLongLine = "Spooler is Running on target server."
    $PropertyBag.AddValue("Description", $outputLongLine) 
    $PropertyBag</ScriptBody>
    <Parameters>
    <Parameter>
    <Name>Username</Name>
     <Value>$RunAs[Name="MyRunAsAccountProfile"]/Domain$\$RunAs[Name="MyRunAsAccountProfile"]/UserName$</Value>
    </Parameter>
    <Parameter>
    <Name>Password</Name>
    <Value>$RunAs[Name="MyRunAsAccountProfile"]/Password$</Value>
    </Parameter>

  • Error message while creating database

    Log error
    while creating new database
    Robot-properties
    XML Parsing Error: junk after document element
    Location: http://portalserver/psconsole/faces/search/RobotPropertiesHome.jsp
    Line Number 18, Column 1:<body id="_id3" onload="return _id3_jsObject
    I have created my new search engine .
    and the robot is not running.I getting log error.
    and no directory is created with the search name.
    please help me with the fields..
    creating search server..
    required Port:
    required Configuration Name:
    Required Instance:
    *Web Container Administration*
    Required Administration Host:
    Required Administration Port:
    Required Administrator:
    Required Administration Password:
    *Web Container Directories*
    Required Install Directory:
    Required Instance Directory:
    Required Document Root Directory:

    Kriti Sundar Mazumder wrote:
    Hi
    I am getting an following error message, while creating database connection pool
    in weblogic 7.
    "<Jun 18, 2004 4:52:36 AM CDT> <Error> <JDBC> <001060> <Cannot startup connection
    pool "MyJDBCConnectionPool" java.sql.SQLException: [IBM][JDBC Driver] CLI0647E
    Error allocating DB2 environment handle, rc=-1.>"
    Can anyone help me out in this regard
    Regards
    KritiHi. I am no expert, but it sounds like a problem with the privileges the user
    has... The best thing is to step back to a simpler environment. Can you try
    connecting to DB2 with a simple program like utils.dbping? Please look at our
    driver docs for the DB2 driver, because there are several variations in connect
    properties depending on the type of DB2 you are connecting to...
    Joe

  • How to invoce remote none-java application in Portal Server

    Hi all
    We have a project that try to use SUN portal server to call remote coldfusion application, according to the server guide I just find the remote portlet can be invocate. Any one had the experience on that.
    Thanks
    Rosso

    The iFrame Provider is provided out of the box with the Sun Portal. You can just use psconsole to add a new channel to a tab. Select "Provider" for the type and then select iFrame for the Provider. You can enter a URL property that points to site you want to appear in the iFrame. There are other useful properties that control scrolling behavior and the height/width of the channel.
    - Jim

  • Deployed portlet not seen under New channel drop down

    Hi,
    I need to add a new portlet to my portal so user can select it under her content configuration page.
    I have added the new portlet to a user's profile via the portlet admin console.
    But the new portlet channel is not available in user's content configuration page.
    Any Idea ?
    (i'm working on Sun ONE Identity Server 6.1 and Sun ONE Application Server 7.0.0_01 on Solaris 5.8).
    Thanks in advance.
    Best Regards,
    Iris

    Hi,
    This problem occurs when display profile is not updated with portlet provider for some reasons
    Tips :
    1. Please check if Webcontainer instance is up.
    2. login to psconsole -> portals tab -> click on the portal name -> Click Add dn button and search for the dn to which you deployed the portlet -> Add it -> select
    it from the select DN listbox and then download the display profile(dp)
    If the portlet provider which you deployed is not present in the display profile
    , then please undeploy the portlet and try deploying again.
    3) Before running the the portlet deploy, set the logger to FINEST and see if any errors are thrown, basically if should show dp updated and war file deployed.
    ./psadmin set-logger -u amadmin -f ps_password -m pas -O debug.com.sun.portal -L
    FINEST
    tail -f /var/opt/SUNWportal/logs/admin/portal.0.0.log

Maybe you are looking for