Light weight custom portal server install to run webcenter blogs

Hi,
We are running PS6 UCM, we just leverage blog service provided by webcenter for blog functionality to be implemented.
Is there lighter version of webcenter custom portal server, that we could you just to run blog service and associated (document service) components.
Any pointers in this direction would be helpful.
Thanks,
Seshan K.

"Light weight custom portal". In terms of hard drive space or CPU and Memory?.
I don't know which license do you have for WebCenter (Portal, Content etc...).
In case of having a WebCenter Portal license (for document services components) Install WebCenter (extended for WCPortal Framework Applications) and just enable the Services or components that you are going to use (like CustomPortal and UCM servers only).
Regards.

Similar Messages

  • BPM worklist in custom portal server

    Hello
    I have extended a domain containing soa, ucm and webcenter with the custom portal template to create a custom portal server. I am trying to integrate the bpm worklist taskflows on a page here. I have managed to get the bpm taskflows in a adf app deployed on a soa server. Most of the soa libraries are targeted to the custom portal server. The page the worklist is displayed on is only displayed to an authenticated user. the page still shows up blank. No errors.
    Has anyone here managed to get this working on a custom server?
    thanks

    We found a solution this problem in Tamer Qumhiehs blog here
    https://blogs.oracle.com/webcenterportal/entry/oracle_bpm_suite_oracle_webcenter

  • Failed configuring Portal Server. can't run cacaoadm.bat

    Hi,
    I am trying to install Sun Java ES5 (2006Q4) on window XP. The configuration for portal server was failed. When I checked the logs, it complains cacao default instance was disabled and couldn't started. I went to the the directory and tried to manually run cacaoadm command. It returns:
    C:\Sun\JavaES5\share\cacao_2\bin>cacaoadm.bat enable
    This action cannot be performed by a non privileged user.
    I logged on to the windows as a user who is in the administrators group. Any other components installations were fine. I really have no idea how to solve this problem as there is no user account as administrator. Can someone please help?
    The portal config error from the log are as following:
    [#|2007-06-26T15:22:14.821+1000|INFO|SJS Portal Server|debug.com.sun.portal.fabric.config|ThreadID=10; ClassName=com.sun.portal.fabric.config.PortalConfigurator; MethodName=configureHost; |PSFB_CSPFC0021:Waiting for Cacao Server to Startup|#]
    [#|2007-06-26T15:22:15.696+1000|FINEST|SJS Portal Server|debug.com.sun.portal.fabric.util|ThreadID=37; ClassName=com.sun.portal.fabric.util.StreamLogger; MethodName=run; |PSFB_CSPFU0004: C:/Sun/JavaES5/share/cacao_2/bin/cacaoadm(Output)=default instance is DISABLED at system startup.|#]
    [#|2007-06-26T15:22:15.712+1000|FINEST|SJS Portal Server|debug.com.sun.portal.fabric.util|ThreadID=37; ClassName=com.sun.portal.fabric.util.StreamLogger; MethodName=run; |PSFB_CSPFU0004: C:/Sun/JavaES5/share/cacao_2/bin/cacaoadm(Output)=default instance is not running.|#]
    [#|2007-06-26T15:22:15.790+1000|INFO|SJS Portal Server|debug.com.sun.portal.fabric.tasks|ThreadID=10; ClassName=com.sun.portal.fabric.tasks.Cacao; MethodName=execCommand; |PSFB_CSPFT0342:<C:/Sun/JavaES5/share/cacao_2/bin/cacaoadm status> Returned <default instance is DISABLED at system startup.
    default instance is not running.
    |#][#|2007-06-26T15:23:45.790+1000|SEVERE|SJS Portal Server|debug.com.sun.portal.fabric.config|ThreadID=10; ClassName=com.sun.portal.fabric.config.PortalConfigurator; MethodName=configureHost; |PSFB_CSPFC0020:Cacao Server startup failed|#]
    [#|2007-06-26T15:23:45.790+1000|SEVERE|SJS Portal Server|debug.com.sun.portal.fabric.config|ThreadID=10; ClassName=com.sun.portal.fabric.config.PortalConfigurator; MethodName=configureHost; |PSFB_CSPFC0024:Failed to configure the Host
    com.sun.portal.fabric.tasks.ConfigurationException
         at com.sun.portal.fabric.config.PortalConfigurator.configureHost(PortalConfigurator.java:635)
         at com.sun.portal.fabric.config.ConfigurePortal.main(ConfigurePortal.java:166)
    |#]
    [#|2007-06-26T15:23:45.790+1000|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
         at com.sun.portal.fabric.config.PortalConfigurator.configureHost(PortalConfigurator.java:749)
         at com.sun.portal.fabric.config.ConfigurePortal.main(ConfigurePortal.java:166)
    Thank you very much
    Regards,
    Tara

    Hi Deepak,
    Thanks for the post.
    Use cacaoadm restar gives me the same error.
    I found out that is a limitation for the windows version I am using. Basically, the account for installation and configuration has to be an local administrator not in network.
    Cheers,
    Tara

  • Unexpected server error while running Webcenter portal application

    Hi
    My JDeveloper 11.1.1.5.0 giving the following error when I try to run Webcenter portal application and it is fine for other applications. I also tried to ignore it but in vain......
    Please see this snap.....
    http://2.bp.blogspot.com/-wRwYHmLsYSo/UFF_ZHSaJaI/AAAAAAAAATM/J2SM-PpUUCE/s1600/serverCrashed.PNG
    Thank you,
    Muhammad Nasir

    Hi Erdo thanks for reply.
    Now my UCM connection is fine and I think it is not creating this problem because I make a simple portal application and try to run and getting the same problem without connection.
    Error Details is
    Performing action Run[ from oracle.ide.navigator.ProjectNavigatorWindow ]
    Invoking command: Modify XML[ from oracle.ide.navigator.ProjectNavigatorWindow ]
    Invoking command: Initial Reformat
    Invoking command: XML Edit
    Invoking command: Update <listen-port> in config.xml
    Performing action Run[ from oracle.ide.navigator.ProjectNavigatorWindow ]
    oracle.jps.common:Sep 13, 2012 1:56:48 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
    WARNING: Failed to validate the xml content. cvc-complex-type.2.4.b: The content of element 'propertySets' is not complete. One of '{"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd":propertySet}' is expected. Location: unavailable.
    Uncaught exception
    java.lang.NoSuchMethodError: oracle.mds.internal.config.jaxb.PersistenceConfigType.getMetadataNamespaces()Loracle/mds/internal/config/jaxb/PersistenceConfigType$MetadataNamespaces;
    o.mds.internal.dt.config.NamespaceConfigBuilder.populateExistingNSList(NamespaceConfigBuilder.java:397)
    o.mds.internal.dt.config.NamespaceConfigBuilder.doesNamespaceExists(NamespaceConfigBuilder.java:204)
    o.mds.internal.dt.packaging.EarPackagingListener.generateNamespaceMappings(EarPackagingListener.java:299)
    o.mds.internal.dt.packaging.EarPackagingListener.prepared(EarPackagingListener.java:150)
    o.ji.deploy.fwk.ListenerSupport.firePrepared(ListenerSupport.java:178)
    o.j.deploy.common.AbstractDeployer.prepare(AbstractDeployer.java:78)
    o.ji.deploy.fwk.WrappedDeployer.prepareImpl(WrappedDeployer.java:32)
    o.j.deploy.common.AbstractDeployer.prepare(AbstractDeployer.java:69)
    o.ji.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:451)
    o.j.deploy.DeploymentManager.deploy(DeploymentManager.java:217)
    o.ji.deploy.common.ModulePackagerImpl.deployProfiles(ModulePackagerImpl.java:86)
    o.j.deploy.common.ModulePackager.deployProfiles(ModulePackager.java:63)
    o.j.deploy.common.ModulePackager.deployImpl(ModulePackager.java:52)
    o.j.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
    o.ji.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
    o.j.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
    o.j.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
    o.j.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
    o.ji.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
    o.j.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
    o.j.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
    o.j.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
    o.ji.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
    o.j.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
    o.ji.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:457)
    o.j.deploy.DeploymentManager.deploy(DeploymentManager.java:217)
    o.ji.runner.adrs.AdrsStarter$7$1.run(AdrsStarter.java:1774)
    And web logic server log file is
    [Running application Application1 on Server Instance IntegratedWebLogicServer...]
    [01:57:58 PM] ---- Deployment started. ----
    [01:57:58 PM] Target platform is (Weblogic 10.3).
    [01:57:58 PM] Retrieving existing application information
    [01:57:58 PM] Running dependency analysis...
    [01:57:58 PM] Deploying 3 profiles...
    [01:57:58 PM] Wrote MAR file to C:\Users\Admin\AppData\Roaming\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\Application1\AutoGeneratedMar
    [01:57:58 PM] Warning: ADF View integration with MDS not configured for 'Portal.jpr', JSPX, JSFF files or their Customizations in MAR will be ignored at runtime. Enable Seeded Customizations setting under ADF View option in Project properties to configure MDS integration.
    [01:57:59 PM] Wrote Web Application Module to C:\Users\Admin\AppData\Roaming\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\Application1\PortalWebApp.war
    [01:57:59 PM] #### Deployment incomplete. ####
    [Application Application1 stopped and undeployed from Server Instance IntegratedWebLogicServer]
    Thank you,
    Muhammad Nasir

  • Documenting a Portal Server Install

    As a consultant I have installed iPS and the client, rightly, wants the
    configuration settings documented. The client thinks that the only way
    to do this would be to take screen shots of the screens in the console.
    This is too much of a kludge for me. Is there a way extract the settings
    in a human readable format to include with the "as built" documentation?
    Kent

    I know of two.
    1) Use ipsadmin export to an xml file. This has been problematic because
    you can't get "everything" in one xml.
    2) Use an LDAP Browser (http://www.iit.edu/~gawojar/ldap/) and connect to
    the iPortal ldap. Then, simply export the LDAP system to an LDIF file. You
    can use this reinstate the system to a known state.
    Any more options?
    "Kent Perrier" <[email protected]> wrote in message
    news:[email protected]..
    As a consultant I have installed iPS and the client, rightly, wants the
    configuration settings documented. The client thinks that the only way
    to do this would be to take screen shots of the screens in the console.
    This is too much of a kludge for me. Is there a way extract the settings
    in a human readable format to include with the "as built" documentation?
    Kent

  • Custom portal service not running ni NW 04

    Hello!
    We are about to migrate from EP6 SP2 to NW04 and I'm currently testing the results of the first test run.
    One special problem I encountered is one of my custom portal services no longer running. It did without flaws back in EP6, so something seems to have changed.
    My Service interface:
    [code]
    package com.rag.ekportal.bginfocenter.kmservice;
    @author Juergen Wahlmann
    public interface IBGFetcher extends IService {
    [/code]
    And the implementation:
    [code]
    package com.rag.ekportal.bginfocenter.kmservice;
    public class BGFetcher implements IBGFetcher, Runnable {
    [/code]
    portalapp.xml
    [code]
    <?xml version="1.0"  encoding="UTF-8"?>
         <application>
              <application-config>
              </application-config>
              <components>
                   <component name="BGViewer">
                        <component-config>
                             <property name="ClassName" value="com.rag.ekportal.bginfocenter.bgview.control.BGViewer">
                             </property>
                             <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/components/bgviewer">
                             </property>
                             <property name="ResourceBundleName" value="bginfocenter">
                             </property>
                             <property name="ServicesReference" value="usermanagement,knowledgemanagement,com.rag.ekportal.bginfocenter.kmservice.BGFetcher,com.sap.portal.ivs.connectorservice,landscape">
                             </property>
                        </component-config>
                        <component-profile>
                             <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld">
                                  <property name="personalization" value="none">
                                  </property>
                             </property>
                             <property name="templatesfolderName" value="Vorlagen">
                             </property>
                             <property name="guidelinesfolderName" value="Richtlinien">
                             </property>
                             <property name="bgContactsfolderName" value="BG-Ansprechpartner">
                             </property>
                             <property name="ksb2folderName" value="KSB 2">
                             </property>
                             <property name="bgControllingfolderName" value="BG-Controlling">
                             </property>
                             <property name="rvURL" value="/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.fo.admin!2fcom.admin.fo.iview!2fcom.admin.iview.fo.ri!2fcom.admin.iview.ri.fo.rag!2fcom.admin.iview.ri.rag.iv.begis_0_0?numberBG=">
                             </property>
                             <property name="KmServiceUser" value="KM Service User">
                             </property>
                             <property name="systemAlias" value="BeGIS_RV_DB">
                             <property name="personalization" value="admin"/>
                             <property name="plainDescription" value="JDBC System object for DB access"/>                         
                        </property>
                        <property name="table" value="janus_contract_bg_v">
                             <property name="personalization" value="admin"/>
                             <property name="plainDescription" value="Database View for reading contracts"/>                         
                        </property>
                        <property name="table1" value="user_roles_v">
                             <property name="personalization" value="admin"/>
                             <property name="plainDescription" value="Database Table for checking user role in RV DB"/>                         
                        </property>
                        </component-profile>
                   </component>
              </components>
              <services>
                   <service name="BGFetcher">
                        <service-config>
                             <property name="className" value="com.rag.ekportal.bginfocenter.kmservice.BGFetcher">
                             </property>
                             <property name="startup" value="true">
                             </property>
                             <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/services/bgfetcher">
                             </property>
                        </service-config>
                        <service-profile>
                             <property name="interval" value="300000">
                             </property>
                             <property name="enable" value="false">
                                  <property name="type" value="boolean">
                                  </property>
                             </property>
                             <property name="numberofruns" value="1">
                             </property>
                             <property name="repository" value="/rag_bgm_test/Beschaffungsgruppen">
                             </property>
                             <property name="KmServiceUser" value="KM Service User">
                             </property>
                             <property name="dbServer" value="xxx">
                             </property>
                             <property name="dbUser" value="xxx">
                             </property>
                             <property name="dbPassword" value="xxx">
                             </property>
                             <property name="dbName" value="xxx">
                             </property>
                             <property name="workfolderName" value="Arbeitsordner">
                             </property>
                             <property name="teamfolderName" value="Teamordner">
                             </property>
                             <property name="contactfolderName" value="Ansprechpartner">
                             </property>
                             <property name="publicfolderName" value="u00D6ffentlicher Ordner">
                             </property>
                             <property name="deletedfolderName" value="/rag_bgm_test/Gelu00F6scht/">
                             </property>
                        </service-profile>
                   </service>
              </services>
         </application>
    [/code]
    The service didn't work after the migration, so I tried to deploy it again. This is the result:
    [code]
    Date : 01/12/2006
    Time : 13:31:37:880
    Message : [PortalServiceItem.startServices] service initialisation failed:com.rag.ekportal.bginfocenter.kmservice|BGFetcher
    [EXCEPTION]
    java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
         at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
         at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Severity : Error
    Category : /System/Server
    Location : com.sap.portal.prt.runtime.broker
    Application : sap.com/irj
    Thread : SAPEngine_Application_Thread[impl:3]_15
    Datasource : 2390950:E:\usr\sap\PMT\JC00\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 000C29A5B62A00400000001300000A4000040A2887A939D9
    Source Name : com.sap.portal.prt.runtime.broker
    Argument Objs : java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
         at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
         at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Arguments : java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
         at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
         at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Dsr Component :
    Dsr Transaction : 5f940fe0836711da887d000c29a5b62a
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : /System/Server
    Resource Bundlename :
    Session : 2391
    Source : com.sap.portal.prt.runtime.broker
    ThreadObject : SAPEngine_Application_Thread[impl:3]_15
    Transaction :
    User : xxx
    [/code]
    Looks like something is wrong in the service definition (portalapp.xml) but I have no clue. Class names are spelled right, settings the same as in EP6 SP2, yet the portal engine is not able to find the implementation class of the service.
    Any ideas?
    Cheers,
      Juergen

    Hi Detlev!
    The ServiceReference definition previously was located in the application config under SP2, but didn't work either.
    Now I found the solution. A sharing reference of all non-custom services in the application config and an additional sharing reference to my custom service in the portal application's config like this:
              <application-config>
                   <property name="SharingReference" value="usermanagement,knowledgemanagement,com.sap.portal.ivs.connectorservice,landscape">
                   </property>
              </application-config>
              <components>
                   <component name="BGViewer">
                        <component-config>
                             <property name="ClassName" value="com.rag.ekportal.bginfocenter.bgview.control.BGViewer">
                             </property>
                             <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/components/bgviewer">
                             </property>
                             <property name="ResourceBundleName" value="bginfocenter">
                             </property>
                             <property name="SharingReference" value="com.rag.ekportal.bginfocenter.KMService.BGFetcher">
                             </property>
                        </component-config>
    Case closed, thx for you hint. I awarded points.
    Cheers,
      Jürgen
    Message was edited by: Juergen Wahlmann, solution included

  • Basic Portal Server 6.0 install questions

    Background:
    I am currently running iPlanet Portal Server 3.0 SP4. The gateway and portal server are running on the same host. I am also using a seperate Sun One Directory Server 5.1 for portal authentication.
    I am going to wipe out the current portal server and install the Sun One Portal Server 6.0. The new gateway will be installed on a seperate host. We are going to keep our existing Directory Server 5.1.
    Here are my questions:
    1) I don't know where to put the Netlet Proxy and Rewriter Proxy. I can put it on the gateway host or the portal host. Both boxes are comparable in horsepower but the portal host has four times the disk space. Don't know which config is more efficient.
    2) I don't understand what the iDS/AME piece is or where it goes. Is this something that gets installed on the existing Directory Server host? Or does it get installed on the Portal host?
    3) The install docs say that you need to install patch 113177-01 on your directory server if the install was not done using the Portal Server install procedure. We are using an existing Sun One Dir Server 5.1 so I tried to install the patch and it says I don't have the required packages installed. It looks like it's missing SUNWamds. What is this package?
    Thanks for any information you can provide.

    A Sun engineer contacted me with the answers

  • Sun Java System Portal Server 6.0 FAQs

    Sun Java System Portal Server 6.0 FAQs.
    Author: Sanjeev Agarwal
    Q. How to connect to external URLs from Sun ONE Portal Server? I want to use URL Scrapper for some of external sites/URLs.
    Ans:
    You can connect to external URLs if you have a Proxy Server running.
    If you are using Web Server addition of Sun ONE the Portal Server then
    go to /opt/SUNWam/servers/https-hostname.domainname/config/ dir
    In the jvm12.conf file, enter the followings:
    http.proxyHost=proxyservername.domainname
    http.proxyPort=80 (or the appropriate proxy server port number)
    https.proxyHost=proxyservername.domainname
    https.proxyPort=80 (or the appropriate proxy server port number)
    If you are using Sun ONE AppServer addition of Sun ONE Portal Server then
    go to /var/opt/SUNWappserver/domains/domain1/<server-instance>/config dir
    In the server.xml file, enter the followings:
    <jvm-options>-Dhttp.proxyHost=proxyservername.domainname </jvm-options>
    <jvm-options>-Dhttp.proxyPort=80 (or the appropriate proxy server port number) </jvm-options>
    <jvm-options>-Dhttps.proxyHost=proxyservername.domainname </jvm-options>
    <jvm-options>-Dhttps.proxyPort=80 (or the appropriate proxy server port number) </jvm-options>
    After this modification restart the server.
    Q. Explain all the processes (solaris 8 and S1 Portal Server 6.0) which runs when I start the Sun ONE Portal Server.
    Ans.
    These are the processes that a running Portal Server installation (Sun ONE WebServer addition, without SRAP) generally has by default.
    1. Directory server processes:
    - ns-slapd (LDAP server instance)
    - uxwdog (admin server process) (parent process)
    --- ns-httpd
    ----- ns-httpd
    2. Auth Helper processes:
    - doUnix
    3. Web-Server/Identity-Server/Portal-Server processes:
    As the Portal Server and Identity Server runs as web application on the Web Server, so they share the same JVM and processes.
    - uxwdog (web server admin server process) (parent process)
    --- ns-httpd
    ----- ns-httpd
    (for each web server instance)
    - uxwdog (parent process)
    - ns-httpd
    - ns-httpd
    or (in case of MaxProc=n )
    - uxwdog (parent process)
    --- ns-httpd
    ----- ns-httpd
    ----- ns-httpd
    ----- n
    Q. I have created a custom Provider but getting this error when I access the desktop, what do I do?
    > error in the desktop.debug file:
    > ERROR: DesktopServlet.handleException()
    > java.util.MissingResourceException: Can't find bundle for base name CustomTabContainerProvider,
    Ans:
    It needs a resource bundle for the custom provider. You need to create a file CustomTabContainerProvider.properties (as mentioned in the error message) and put it into the /etc/opt/desktop/classes directory. If you are not using any properties defined in this resource file then it can be a empty file. Have a look on the properties files that bundled containerProviders uses in dir <portal-install-dir>/SUNWps/web-apps/https-<host.domain>/portal/WEB-INF/classes.
    As you are extending JSPTabContainerProvider class, you can just copy the file JSPTabContainerProvider.properties from the above directory after renaming it to the <defined-provider-name>.properties (in your case CustomTabContainerProvider.properties) and move it into /etc/opt/desktop/classes directory.
    Q. what is actually multiple instances of Portal Server means?
    Ans:
    Multiple instance of Portal Server means, you will have more http listeners for the same desktop contents and the same identity profiles stored in a single Directory Server which all the instances share.
    In simple words you can have your Portal Server listening on different http ports, but uses same configuration, desktop and identities.
    It can help you to share the load for Portal Server http requests. The alternate methods are to create more web server virtual server processes (maxProc=n, but in this case the listening port will be 1 only) or use some hardware load balancer.
    You can achieve more from multiple instances if you have a multi level organization, you can change the look and feel of all the instances, images, services, components and can assign each instance to different organization or sub-organization.
    Q. How do I check the availability of the Sun ONE Portal Server/Identity Server services.
    Ans:
    You can check the availability of Sun ONE Identity Server services from following urls.
    http://<host.domainname>:<port>/amserver/sessionservice
    http://<host.domainname>:<port>/amserver/loggingservice
    To know the availability of components of Sun ONE Portal Server like Desktop/providers/Rewriter/Netmail you have to login into desktop. These are not services, but just the programming identities which will work if your Web Server and Identity Server is running.
    Just go to URL http://<server>:<port>/portal/dt , if it shows up that means your portal server is fine, and these entities will work for sure.
    Q. I am able to add the yahoo channels to existing users. But I am getting the weather for London not for local New Jersey. My language pref is to en|en_US and also the server is the default U.S server and not europe. How do I add the cities I want to see on weather channel?
    Ans:
    A Portal user himself (after login) can select what cities he want to see in weather channel.
    Steps:
    - click the edit button of weather channel
    - click on the area you belong to from Available Sections
    - select the cities from Available Cities select box and add them to Your Choices.
    - click finished from select city page and then again click finished from select area page.
    It will come back to the Portal Desktop and you will see all the cities you have selected in the weather channel.
    Q. How to use getContent() method to use in custom jsp providers (developed by ourselves) so that it can be used to retrieve a jsp page. I have already placed the JSP file in the directory structure /etc/opt/SUNWps/desktop/default/channel_dir. But still the jsp is not being displayed.
    Ans:
    You don't have to do anything in the custom JSPProvider's getContent method except the call { return super.getContent(request,response); } . If all you want is just to show your jsp, then create a channel from the default JSPProvider, and edit the property contentPage of that channel from samplecontent.jsp to your jsp name, save the changes and login again. You should see your JSP.
    Q. I want to remove all the buttons (help/edit etc.) from all the channels/one particular channel in my desktop?
    Ans:
    You can hide any buttons you want from any channel.
    These steps show how to hide all the buttons.
    1. Create a channel say "myNetlet" from netlet provider.
    2. Set the channel title to "myNetlet"
    3. Go to the dir /etc/opt/SUNWps/desktop/default/JSPTableContainerProvider and edit the file providerCommands.jsp, and modify the last line :
    from :
    <%=minMaximizeCommand%><%=helpCommand%><%=editCommand%><%=detachAtachCommand%><%=removeCommand%>
    to:
    <% if ( !(title.equals("myNetlet"))){ %><%=minMaximizeCommand%><%=helpCommand%><%=editCommand%><%=detachAtachCommand%><%=removeCommand%><% } %>
    4. Clean the dir mentioned below which contains compiled JSPs. /var/opt/SUNWps/https-<host>.<domain>/portal/tmp/_jsps/_etc/_opt/_SUNWps/_desktop/_default_en/_JSPTableContainerProvider/_html and reload the page.
    Relogin, and you would not see any buttons on "myNetlet" channel. You can customize this logic as per your needs.
    Q. How to change the title of SampleJSP Channel. I tried to change the channel properties title value via iplanet directory Server Access Management GUI. But it is not getting reflected.
    Ans:
    Through Admin console you can change the channel property "title", and as soon as you refresh the page (Shift reload) of relogin in the portal it get's reflected.
    The reason to this problem may be due to the channel property "title" is having "propagate" value as false and you are setting the channel title in the org level display profile not in the user level display profile.
    So better you change the channel name in user's display profile also.
    For this login into admin console and go to :
    - View: "User Management" -> click on organization -> Show: Users
    - click on the blue arrow of that user
    - click on Edit in section Desktop (this will open a window)
    - then change the channel properties same way you do for Organization display profile.
    Q. Login Problem with SunOne Portal 6.0.
    I was able to download and install sun one portal 6 on Solaris 8. The sample portal page came up after installation. However whenever I try to login to the Login channel with "amadmin" and the passphrase I used during installation, it takes me to another page - iPlanet/LDAP authentication page. Here I tried using the same login, but fails every time (the same login page appears). The url that shows is "http://<hostname>/amserver/login?module=dproadmin&goto=/amconsole/base/AMAdminFrame"
    I tried registering myself as a new user as well. This too fails.
    Ans:
    Make sure you are giving fully qualifying the hostname in the url which invoked the desktop. This in fact is documented in the administration documentation. If the hostname is not fully-qualified, the login page goes into an endless mode. Again, the correct url is "http://<fully-qualified-hostname>/portal". Once you get to the desktop, the login and the new user registration works.
    Q. How to send variables/parameters from 1 app to another app deployed on Sun ONE Portal Server? It may be the apps or different JSPs of JSP provider channel.
    How to achieve inter channel communication in Sun ONE Portal Server?
    Ans:
    You can use servlet context object or session, or may be the request object itself to store the information from one channel and use that in another channel. The use of either of these 3 approaches may depend on your requirements. Using session, the information will be available to that user's channels only, using request, the information will be available for that user and that request only and by using ServletContext you can share the information across users and sessions. You can obtain DesktopServlet's ServletContext object inside JSP/JSPProvider.
    Q. I am trying to modify the default desktop JSPs in TableContainerProvider and TabCotntainerProvider dirs, but it is not picking my modified JSPs ? what do I do?
    Ans:
    One easiest way to 100% ensure that it updates all your new jsp pages is to remove all the compiled jsps so that with next request the Sun ONE Portal Server compiles all the jsps and will make sure that your modification will be taken care of in next request.
    Go to /var/opt/SUNWps/https-<instance_name>/portal/tmp/_jsp/_etc/_opt/_SUNWps/_desktop/_default_<locale>/ and remove everything. and access the Portal server, it will be little slow as it has to compile all the JSPs again. Here you will find directories in the name of Containers and Channels, so if you are modifying any particular Container/Channel you can just delete that only. This approach can help a lot during development time.
    Q. What is the location of compiled JSPs in Sun ONE portal Server and what servlet spec does it supports?
    Ans: The Portal server 6.0 runs on Sun ONE Web Server 6.0 sp2, which supports only jdk 1.3 and servlet spec 2.2 only. The Sun ONE Portal Server keeps the compiled jsps of desktop and channels in : /var/opt/SUNWps/https-<instance_name>/portal/tmp/_jsp/_etc/_opt/_SUNWps/_desktop/_default_<locale>/ dir as per the channels/container names.
    Servlet 2.3 is supported if you run the Portal Server edition that runs on Sun ONE Application Server 7.0.
    Q. How do I change jdk for Sun ONE Portal Server to another jdk? I want to change the JDK of only one of my Portal Server instances, is it possible? how?
    Ans:
    Yes you can achieve both.
    A. To change the JDK for all the server instances:
    Open <portal-install-dir>/SUNWam/servers/https-admserv/start-jvm file and modify the first line
    NSES_JDK=/usr/java_1.3.1_04; export NSES_JDK
    to
    NSES_JDK=<your-jdk-location> ; export NSES_JDK
    then open <portal-install-dir>/SUNWam/servers/https-<instance-name>/config/jvm12.conf file of all the server instances and add a line
    jvm.option=-server after the first line
    B. To change the JDK for a particular server instances:
    Make a another copy of the start-jvm file rename it and modify the jdk location in it as mentioned above.
    Open the start script from <portal-install-dir>/SUNWam/servers/https-<instance-name> dir and modify these lines :
    if test -r {SERVER_ROOT}/https-admserv/start-*
    then
    for STARTSCRIPT in {SERVER_ROOT}/https-admserv/start-*
    modify this to
    if test -r {SERVER_ROOT}/https-admserv/<changed_name_of_start-jvm-file>
    then
    for STARTSCRIPT in {SERVER_ROOT}/https-admserv/<changed_name_of_start-jvm-file>
    Note: As Portal Server 6.0 uses Web server 6.0 sp2, jdk 1.4 is not supported.
    Q. How do I create a custom login page or a link, which will just log me into the portal server.
    Ans:
    You can create a custom page in your jsp page, just add this portion of html into your web page :
    <FORM action="http://<server>:<port>/amserver/login?module=<login-module>&page=1" method=post name=login_form2 target=_top>
    Login page using <login-module><br>
    <P>Enter UserId<BR><INPUT name=TOKEN0 size=22></P>
    <P>Enter Password<BR><INPUT name=TOKEN1 size=22 type=password></P>
    <P><INPUT name=Submit type=submit value=Submit> </P>
    </FORM>
    The <login-module> can be LDAP or Unix or Membership which ever you have enabled. Or instead of this you can create a link. For example for LDAP auth module :
    "<a href="http://<server>:<port>/amserver/login?module=LDAP&page=1&TOKEN0=user&TOKEN1=password" target=_top> Login into Portal </a>"
    where user and password are the user credential for the portal server.
    Q. Can I install a portal server pointing to another Identity server? I want to install few postal servers (on different machines) pointing to same identity server, is it possible?
    Ans:
    No, right now the Sun ONE Portal Server is tightly integrated with Sun ONE Identity Server so you can't just install only Sun ONE Portal Server and point it to another Sun ONE Identity Server. You can have a common Directory server if you want.
    Q. I have an application which takes input in from anonymous user and then to complete the request the user than has to login. I am having problem in passing the taken input from anonymous page to logged in user. all the request parameters are lost when I log in. How do i get the request parameters after I log in
    Ans:
    You can create a custom login page and submit the form to "/amserver/login" with a hidden parameter "goto" through which you basically specify which url to go after you log in. So you can use this mechanism to create a query string with all your request parameters you want to pass after login. For example:
    You can create a jsp which take few inputs from user and to complete the request you have to login so it posts the input form to a login jsp and stores the parameters taken from user in a hidden field (goto) :
    <FORM action="/amserver/login?module=LDAP&page=1" method=post name=login_form2 target=_top>
    Login page using LDAP<br>
    <P>Enter UserId<BR><INPUT name=TOKEN0 size=22></P>
    <P>Enter Password<BR><INPUT name=TOKEN1 size=22 type=password></P>
    <INPUT TYPE=HIDDEN NAME="goto" VALUE="/portal/dt?param1=<%=request.getParameter("param1")%>&param2=<%=request.getParameter("param2")%>">
    <P><INPUT name=Submit type=submit value=Submit> </P>
    </FORM>
    After you login through this page both the param1 and param 2 will be available in the request object after you login and you can retrieve them in your application or jsp.
    Q. I have few System.out.println in my jsp which i am using in my JSP provider channel, but when I look at the portal server's /var/opt/SUNWam/debug/desktop.debug file, none are there. I looked at the web server's access and error logs too, but it is not there also. Can somebody tell me how do it get those ? Do we have any other mechanism to put debug logs ?
    Ans
    By default the binary which web server runs is uxwdog which eats up System.out.println output. If you want to see the System.out.println then you need to change the product binary from the start script of the portal server instance.
    - Go to <portal-install-dir>/SUNWam/servers/https-<instance-name> and open the start script
    - Change the PRODUCT_BIN=uxwdog to PRODUCT_BIN=ns-httpd , save the file
    - Run the script ./start to start the portal server
    Note : with ns-httpd ON the server will not leave that shell, and in the same window/shell you will be able to see all your System.out.println statements. To close the server you have to kill the server process with "kill -9 pids" command
    Alternate way is to use api inside your application or jsp:
    <%@page import="com.sun.portal.providers.jsp.JSPProvider, com.sun.portal.providers.*, com.sun.portal.providers.containers.*, com.sun.portal.providers.context.*" %>
    <% JSPProvider p=(JSPProvider)pageContext.getAttribute("JSPProvider");
    ProviderContext pc = p.getProviderContext(); %>
    <%-- after that you can use these lines any where in your jsp --%>
    <%
    pc.debugError("your error msg");
    pc.debugMessage("your msg");
    pc.debugWarning("your warning msg");
    %>
    The particular mgs will be shwon in /var/opt/SUNWam/debug/desktop.debug file as per your "debugLevel" parameter setting in /etc/opt/SUNWps/desktop/desktopconfig.properties file. By default the debugLevel is set to error so only pc.debugError("error msg") will be shown.
    Q. Multipart form (file upload) processing in providers? Is it supported
    Ans:
    The Sun ONE Portal Server's DesktopServlet does not have the ability to process a request with the content encoding type of multipart/form-data. DesktopServlet does not pass the input stream for the request on to the Provider.
    To accomplish handling of multipart/form-data type requests, it is necessary to create a companion servlet or JSP that process the multipart/form-data. This servlet can then pass control back to the Portal channel. The data from the file can be shared between the servlet and the provider by using static Java members or by storing the data in a back-end database and then passing a reference to the data over to the provider.
    Q. After installing the Portal Server I am trying to login as admin, but it is failing and coming back to login page every time. How do I login?
    Ans:
    The Default Admin user is 'amadmin' and the password is the PASSPHRASE you give during Portal Server installation. Try login using these credentials.
    Also in the browser give the complete URL for the Portal Server like : Http://<myhost>.<mydomain>:<port>/amserver/login or Http://<myhost>.<mydomain>:<port>/amconsole. You can't login into portal server's IDSAME console by giving IP Address or just the hostname, also your machine should be listed in the DNS server so that it can resolve the name.
    Q. I installed Sun ONE Portal Server 6.0 some time back, and now I want to know all the installation parameters and user/passwords for whole portal installation. How do I do that?
    Ans:
    The Default Admin user is 'amadmin' and the password is the PASSPHRASE you give during Portal Server installation. Also in the browser give the complete URL for the Portal Server like : Http://<myhost>.<mydomain>:<port>/amserver/login or Http://<myhost>.<mydomain>:<port>/amconsole. You can't login into portal server's IDSAME console by giving IP Address or just the hostname, also your machine should be listed in the DNS server so that it can resolve the name.
    In case you have forgotten the port numbers and PASSPHRASE that you give during installation, you still can see all the information for each component of your Portal Server Installation. The Portal server and it's components like Directory Server, Web Server and IDSAME are installed as Solaris package so the system has all the information for these packages.
    Portal Server : See file /var/sadm/pkg/SUNWps/pkginfo
    Directory Server : See files /var/sadm/pkg/SUNWamds/pkginfo and /var/sadm/pkg/SUNWamdsc/pkginfo
    Web Server : See file /var/sadm/pkg/SUNWamws/pkginfo
    Identity Server : See file /var/sadm/pkg/SUNWamsam/pkginfo
    Note: In any case you should never edit/modify these files.
    Q. Controlling the display of the help (?) button.
    Where are the links/image elements defined for the help/edit/minimize buttons? the leafWrapper.jsp pulls the hashtable out of the HttpRequest, and that hashtable is being used by providerCommands.jsp:
    Hashtable commands = (Hashtable)request.getAttribute("provider_cmds");
    Any idea where this is being set?
    Ans:
    - You can remove the help/edit button of any channel by adding the line into the Channel's properties by editing the Xml of display profile in the admin console.
    <String name="helpURL" value="" advanced="false" merge="replace" lock="false" propagate="true"/>
    <Boolean name="isEditable" value="false" advanced="false" merge="replace" lock="false" propagate="true"/>
    The Attribute 'provider_cmds' is set into /etc/opt/SUNWps/desktop/default/JSPTableContainerProvider/tablecolumn.jsp :
    <dttable:getProviderCommand id="provider_cmds" scope="request" />, and after that only the leafwrapper.jsp is included, but the Hashtable is generated by a class com.sun.portal.providers.util.ProviderCommands.java and made available through taglib classes. So you can't change the generated contents/string in the Hashtable.
    But you can change the default 'alt' text displayed and the images linked to the help/edit icons. As this modification is at Provider level, it will change the icons for all the channels in the desktop.
    Please see the file:
    /opt/SUNWps/web-apps/https-<host>.<domain>/portal/WEB-INF/classes/JSPTABLEContainerProvider.properties.
    Here you will find the mapping. The image location are given from the context root of portal server which is by default : /opt/SUNWps/web-apps/https-<host>.<domain>/portal.
    Q. I have a number of web applications needed to integrate to portal server. Any pointers or tips of what my option is?
    Ans:
    You can very well integrate all your web application with Portal server. Portal Server 6.0 has web container same as Sun ONE web server 6.0 Sp2, which runs on Jdk-1.3.
    If your web applications are just Servlets/Jsps then you can very well port them on Portal server's webserver which supports war module deployment. (infect for Web server the Portal server and Identity server is like a war module.)
    There can be two possibilities in this case, either you put the whole of your application on portal server and make the link available into the desktop via 'Application Provider Channels' or you can create a client to your web application into portal server.
    If your web application is on Sun ONE Application server 7.0 and needs authentication, you can also have SSO. If you just want to show the link of your web application into desktop then you can either use URL Scrapper to show the first page of your web application or use Bookmark channel to provide just the url.
    The easiest way to make a client of your web application is to use JSP Channel using JSPProvider and put your logic into the samplecontents.jsp file or you can create your own custom Provider extending JSPProvider. There can be a lot of different configurations, depending on the web application you want to integrate and your needs
    Q. I removed few channels from the org level display profile but still they are coming to the desktop of users, I had accessed the desktop before. why?
    Ans:
    If you still see any channel after you remove it from the display profile at organization lever, that means you have to edit the user's display profile. So go to admin console and select User from Show: menu and click on the blue arrow near the user. In the right frame under the 'Desktop' category click on the Edit link (right side). This will open user's display profile in a window. Now edit it as per your requirements.

    Unfortunately Web Server 6.0SP2 is no longer available for download.
    If you must use Web Server 6.0, you should use the most current Service Pack. It is backward compatible and contains many performance and security fixes.

  • Portal Server 7 on Solaris 10 x86 VM???

    Hi all, has anyone managed to successfully install portal server 7 into a Solaris 10 x86 VM? A VMWare VM that is.
    Stewart

    I'm a colleague of mcleans's, so hopefully i can shed a little light on the situation.
    The exact error we're experiencing occurs during the Portal Server install (in configure now, although this occurs with configure later using the psconfig utility too). The error in our log file is ..
    [#|2007-11-28T15:44:40.697+0800|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: javax.management.remote.JMXProviderException: sun.security.validator.ValidatorException: No trusted certificate found
            at com.sun.portal.fabric.config.PortalConfigurator.getMbeanServerConnection(PortalConfigurator.java:773)
            at com.sun.portal.fabric.config.ConfigurePortal.main(ConfigurePortal.java:175)
    Caused by: javax.management.remote.JMXProviderException: sun.security.validator.ValidatorException: No trusted certificate found
            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.fabric.config.PortalConfigurator.getMbeanServerConnection(PortalConfigurator.java:761)
            ... 1 more
    Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
            at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1518)
            at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
            at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
            at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848)
            at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106)
            at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
            at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:818)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041)
            at com.sun.jmx.remote.opt.security.TLSClientHandler.activate(TLSClientHandler.java:189)
            at com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:150)
            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:904)
            at com.sun.cacao.agent.impl.CacaoJmxConnectorProvider.newJMXConnector(CacaoJmxConnectorProvider.java:362)
            ... 7 more
    Caused by: sun.security.validator.ValidatorException: No trusted certificate found
            at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:304)
            at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:107)
            at sun.security.validator.Validator.validate(Validator.java:203)
            at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172)
            at com.sun.portal.admin.common.util.PSX509TrustManager.checkServerTrusted(PSX509TrustManager.java:108)
            at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320)
            at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841)
            ... 22 moreAnother user of this forum had the same problem it seems - http://forum.java.sun.com/thread.jspa?threadID=5234926 - and reported ..
    BTW, I recreate the key by using your suggestions. and now portal server was configured, up and runningAs suggested we've also recreated the cacao keys:
    cacaoadm create-keys -f The VM we're using was from a template Solaris 10 VM, so we had to change the hostname. As suggested, we also performed a sysuncofig, and also recreated the cacao keys (as above), then installed Application Server, AM SDK (remote) then Portal Server.
    We have been in contact with Sun support, and they have told us to put the machine in DNS (rather than just the hosts file), which we have also done.
    Any ideas?
    FYI
    # hostname
    ps1
    # domainname
    curtin.edu.au
    Edited by: travio on Dec 3, 2007 11:49 PM

  • Portal server with WLS 6.1 SP2

    Hi,
    Has anybody installed Portal server 4.0 with WLS 6.1 with service pack 2. I got
    the following problem:
    I changed my WLS6.0 to 6.1 sp2 on WinNT.
    Starting install Portal 4.0, it went through well. However, I couldnot
    start Portal server. Hereis the massege after start Portal server (WLS is
    running) :
    # Note: Server initialization may take several minutes.
    # Please be patient.
    <Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from
    user.
    >
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method
    weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Press any key to continue . . .
    Could you help me to finger out what's wrong.

    Rahul, just wanted to thank you for the info. I was having the same
    problem, and changing the classpath and capacityincrement worked.
    Thanks again,
    John
    [email protected] (Rahul Prabhu) wrote in message news:<[email protected]>...
    Hi,
    Modify the 'Set Classpath' in your startPortal.bat as follows:
    SET CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic_sp.jar;%WEBLOGIC_HOME%\lib\weblogic.jar;
    ..all the existing stuff..etc.
    You might also need to change the 'capacityIncrement' in your
    config.xml to > 0
    let me know if it goes thru.
    hth,
    Rahul
    "Tao Huang" <[email protected]> wrote in message news:<3c362c9a$[email protected]>...
    Hi,
    Has anybody installed Portal server 4.0 with WLS 6.1 with service pack 2. I got
    the following problem:
    I changed my WLS6.0 to 6.1 sp2 on WinNT.
    Starting install Portal 4.0, it went through well. However, I couldnot
    start Portal server. Hereis the massege after start Portal server (WLS is
    running) :
    # Note: Server initialization may take several minutes.
    # Please be patient.
    <Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from
    user.
    >
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method
    weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Press any key to continue . . .
    Could you help me to finger out what's wrong.

  • Portlet error (portal server 6.3)

    I created a portlet, it is deployed using pdeploy, then I created a channel and put it under JSPTabcontainer using Access Manager. I keep getting this error in the portal server :
    ERROR: ProviderCaller.run(): exception thrown from TestPortlet
    com.sun.portal.desktop.context.ContextError: couldn't fetch content
         at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusableProviderCaller.java:180)
    Thanks a lot.

    To deploy the portlet, I put the .war file under sun/portalserver/tmp/portlet (the folder where portletsamples.war located), then run the pdeploy utility to deploy it and it was successful.
    The thing puzzles me is, my portlet has couple of .jsp pages and some jar files that I referenced, I am assuming they shoud be installed somewhere under portalserver but I could not find anything by doing a search. Is this normal?
    Thanks
    Mike

  • Getting portal server name using webdynpro deployed in different server.

    Hi All,
      I have a question on accessing the servername where my portal is running which has an iview created for a webdynpro which is deployed in other server.I have J2ee server1 on which portal is installed and running, now i have developed webdynpro with authentication and deployed to another J2ee server2. In server1 i want to create the iview through which i can access the webdynpro deployed in server2, now in my webdynpro i used NavigationTarget with LinkToURL element where user can navigate to the one of portal page which requires the servername of portal, so how can i get the servername where portal is running(server1) if my webdynpro is deployed in server2.please provide what are the steps rerquired to get this scenario running and also for i used the target propery of linktourl to _self  and _top but its opening in new browser, i want link to open  in same window.Please give your valuable suggestions.
    Thanks,
    Pkv.

    Hi..
    try {
         InetAddress ina = InetAddress.getLocalHost();
          wdComponentAPI.getMessageManager().reportSuccess("Host name is "ina.getHostName()"..Host address "ina.getHostAddress()"...CanonicalHostName   "ina.getCanonicalHostName()"...by name    "+ina.getByName(ina.getHostName()));
         } catch (UnknownHostException e) {
         // TODO Auto-generated catch block
         wdComponentAPI.getMessageManager().reportSuccess(""+e);
    this is the small peice of to know  and tell me ur requirment is on Development Server or Production,for development above code is enough if not than need to do more
    Regards
    Rajesh

  • Start Portal server

    Hi,
    I changed my WLS6.0 to 6.1 sp2 on WinNT. Starting install Portal 4.0, it went
    through well. However, I couldnot start Portal server. Hereis the massege after
    start Portal server (WLS is running) :
    # Note: Server initialization may take several minutes.
    # Please be patient.
    <Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from user.
    >
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Press any key to continue . . .
    my WSL log file see attached file
    Could you help me to finger out what's wrong.
    thanks
    tao
    [weblogic.log]

    I had the same problem on Solaris 2.8, the only way I could fix it was to backtrack
    to WebLogic Server 6.1 w/ sp1 instead of sp2
    Brian
    "Stéphane Gamondes" <[email protected]> wrote:
    >
    >
    Hi,
    I don't have the answer to this error, but we had the same problem...
    Switching back to WLS6.1 sp1 solved it though.
    Stéphane
    "Tao Huang" <[email protected]> wrote:
    Hi,
    I changed my WLS6.0 to 6.1 sp2 on WinNT. Starting install Portal 4.0,
    it went
    through well. However, I couldnot start Portal server. Hereis the massege
    after
    start Portal server (WLS is running) :
    # Note: Server initialization may take several minutes.
    # Please be patient.
    <Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password
    from user.
    >
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Press any key to continue . . .
    my WSL log file see attached file
    Could you help me to finger out what's wrong.
    thanks
    tao

  • Wsrp producer in weblogic app server not portal server

    I am following the instructions given in [url http://edocs.bea.com/wlp/docs92/federation/Chap-Working_With_Producers.html]
    to create wsrp producers on weblogic server without the portal server.
    However in Figure 8-7 (Select Project Facets) of the article, the facets being selected belong to weblogic portal which means weblogic portal server will need to be installed. In my case, this defeats the purpose of being being able to create wsrp producers on weblogic server alone (i.e without the portal server installed).
    Is there a way we could achieve this without installing weblogic portal? Any help would be appreciated.

    No, the 8.1 instruction will not work with 9.2.
    In 9.2 you do need to install WLP in order to get the correct templates
    and jars.
    Nate
    Ranjan Saikia wrote:
    You mean to say that the instructions for 8.1 will work for 9.2 too? I tried them out but could not find some of the jars(javelin.jar, knex.jar) in the 9.2 installation.
    I was initially following the [url http://edocs.bea.com/wlp/docs92/federation/Chap-Working_With_Producers.html]instructions in the 9.2 docs but couldnt get the required facets until I installed the portal server.

  • URL to public_html docs on the app server version of Portal Server 6.0

    I recently switched from Portal Server 6.0 to the Portal Server version that runs under Sun's Application Server 7.
    I want to create a bookmark that references a URL that is already located on the portal server itself.
    I did this in the previous version by placing my files in a subdirectory under /opt/SUNWam/public_html/go/index.html
    I could access the URL by creating the bookmark with the relative URL /go/index.html
    This no longer works under the application server version of portal server 6.0. I tried placing my file in /opt/SUNWappserver7/SUNWam/public_html/go/index.html and referencing the file as /go/index.html
    Anybody know what the new relative URL would be to access this document?

    By golly, I figured it out.
    In order to use the URL /go/index.html as the bookmark, the file needs to be placed in the "go" subdirectory off the default document root of the application server at /var/opt/SUNWappserver7/domains/domain1/server1/docroot/go/index.html

Maybe you are looking for