Portal 7.0 Cluster

Hello,
Has anyone successfully deployed a Portal 7.0 Cluster?
I cannot configure the datasync web application properly to synchronize portal data across all nodes of a cluster.
The Portal 7 documentation does not describe how this should be done and the Portal 4 documentation seems obsolete.
Any help would be greatly appreciated.
Many thanks,
Paul

Paul,
Yes, I have... :-)
Seriously: we made some enhancements to DataSync for 7.0 so that it now
supports a new "server discover" option - the documentation is lagging
behind I am sad to say, so I will try to help you as much as I can here.
In essence if you create a domain using the config wizard and leave all the
default alone DataSync should automatically discover the other machines in
your domain running the same instance of your application and create the
proxies. It is no longer neccessay to edit at Servlet context params or
deploy seperate instances of the DataSync WebApp to the managed nodes and
the admin node.
Note that the 4.0 way of manually creating proxies still works however, and
allows you to add explicit proxies to machines that may be outside your WLS
domain.
For example: if I have three machines Admin, M1 and M2 (where Admin is the
WLS admin machine) and the same application deployed on all three machines
then server discovery should be able to find the instances of the
DataSyncServlet on M1 and M2.
If the URL on the Admin is http://admin:7501/myApp/DataSyncServlet
then it will attempt to contact:
http://m1:7501/myApp/DataSyncServlet and
http://m2:7501/myApp/DataSyncServlet
This requires that your entry point into your cluster is your WLS admin
machine (this will be auto-configured for read/write JDBC persistence on the
Master DataRepository and will perform server discovery). The managed
machines will use read-only JDBC persistence and will not run server
discovery. The persistence defaults can be overriden using System properties
while server discovery can be disabled by setting a DataSyncServlet context
property.
Please let me know if you have any more questions.
Sincerely,
Daniel Selman
"Paul Banh" <[email protected]> wrote in message
news:[email protected]...
Hello,
Has anyone successfully deployed a Portal 7.0 Cluster?
I cannot configure the datasync web application properly to synchronizeportal data across all nodes of a cluster.
>
The Portal 7 documentation does not describe how this should be done andthe Portal 4 documentation seems obsolete.
>
Any help would be greatly appreciated.
Many thanks,
Paul

Similar Messages

  • How to deply Portal to a cluster

    Hi,
    I am trying to deploy a portal application on a cluster (3 win2000 servers).
    I followed the BEA documentation to the letter.
    When deploying document.jar to the cluster, each server in a cluster
    produces the following exception:
    ####<Jun 7, 2002 10:47:08 PM MDT> <Warning> <EJB> <opp-raps02dev>
    <InvestPortalServer02> <ExecuteThread: '0' for queue:
    '__weblogic_admin_rmi_queue'> <system> <> <010063> <The EJB: DocumentManager
    had an <initial-beans-in-free-pool> setting in its weblogic-ejb-jar.xml. An
    error occurred while creating these initial bean instances. The error was:
    Unable to find DocumentConnectionPool 'default' configuration
    MBeanjavax.ejb.CreateException: Unable to find DocumentConnectionPool
    'default' configuration MBean
    at
    com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl.ejbCreate(
    SPIFastDocumentManagerImpl.java:324)
    at
    com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl_lw366m_Imp
    l.ejbCreate(SPIFastDocumentManagerImpl_lw366m_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.jav
    a:153)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:198)
    at weblogic.ejb20.pool.Pool.onAfterDeploy(Pool.java:177)
    at
    weblogic.ejb20.deployer.Deployer.runAfterDeploymentListeners(Deployer.java:1
    325)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1013)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    The DocumentConnectionPool is defined in the "Service Configuration/Document
    Connection Pool Service" for the portal application. However, I can not find
    any information on how to pass this information to the managed servers.
    Has anybody experiensed anything like this?
    Thanks
    Mike

    Problem SOLVED.
    In order to deploy portal in a cluster it is not enough to deploy individual components
    (as described in the Deployment guide). The config.xml needs to be edited manualy
    since the console application does not provide the way of defining the target for
    "application-config.xml". The portal services configuration is defined in this file,
    and, tharefore it needs to be deployed to the cluster as well in order for portal
    services to function properly.
    This is how to do this: open the config.xml in your text editor, search for the word
    "application-config.xml", in the target option specify the name of your cluster.
    Restart the managed servers.
    Regards,
    Michael Goldverg
    "Michael Goldverg" <[email protected]> wrote:
    Hi,
    I am trying to deploy a portal application on a cluster (3 win2000 servers).
    I followed the BEA documentation to the letter.
    When deploying document.jar to the cluster, each server in a cluster
    produces the following exception:
    ####<Jun 7, 2002 10:47:08 PM MDT> <Warning> <EJB> <opp-raps02dev>
    <InvestPortalServer02> <ExecuteThread: '0' for queue:
    '__weblogic_admin_rmi_queue'> <system> <> <010063> <The EJB: DocumentManager
    had an <initial-beans-in-free-pool> setting in its weblogic-ejb-jar.xml.
    An
    error occurred while creating these initial bean instances. The error was:
    Unable to find DocumentConnectionPool 'default' configuration
    MBeanjavax.ejb.CreateException: Unable to find DocumentConnectionPool
    'default' configuration MBean
    at
    com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl.ejbCreate(
    SPIFastDocumentManagerImpl.java:324)
    at
    com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl_lw366m_Imp
    l.ejbCreate(SPIFastDocumentManagerImpl_lw366m_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.jav
    a:153)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:198)
    at weblogic.ejb20.pool.Pool.onAfterDeploy(Pool.java:177)
    at
    weblogic.ejb20.deployer.Deployer.runAfterDeploymentListeners(Deployer.java:1
    325)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1013)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    ..java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    The DocumentConnectionPool is defined in the "Service Configuration/Document
    Connection Pool Service" for the portal application. However, I can not
    find
    any information on how to pass this information to the managed servers.
    Has anybody experiensed anything like this?
    Thanks
    Mike

  • Portal Drive and Cluster

    Hi all,
    We received recommendation to start using portal drive instead of web browser in
    order to access KM folders via WebDAV.
    I have installed and configured Portal drive as described in SAP help.
    Since we have a cluster installation, the server URL is the dispatcher URL.
    When providing the dispatcher URL, portal drive fails to connect.
    When providing one of the cluster servers url, connection is successful.
    Does anyone know if it is possible to work with Portal Drive in a cluster installation
    and if so, what configuration should be made in order for this to work?
    Thanks,
    Moti.

    Well, this is supposed to work. If it doesn't, I would recommend to open a support message so the problem gets investigated.
    Best regards, Julian

  • How do you deploy a portal to a weblogic cluster?

    We're using WLServer 6.1 SP2 and WLPortal 4.0 SP2. Has anybody got any experience
    clustering a portal instance? We can see how to target EJB and WAR components to
    the cluster server (those components have "Target" tabs when we display them in the
    console), but how do you target an EAR (such as the portal) to a cluster? It seems
    awfully tedious to sit and deploy each individual ejb/war to the cluster to get started.
    Thanks!

    Joshua,
    You have to deply components individualy. Also, make sure you define a proper target
    for application-config.xml. You can only do this by editing config.xml.
    Also do not forget to deply all necessary J2EE services (JDBC etc) as well as startup
    classes.
    Regards,
    Michael Goldverg
    "Joshua Davies" <[email protected]> wrote:
    >
    We're using WLServer 6.1 SP2 and WLPortal 4.0 SP2. Has anybody got any
    experience
    clustering a portal instance? We can see how to target EJB and WAR components
    to
    the cluster server (those components have "Target" tabs when we display
    them in the
    console), but how do you target an EAR (such as the portal) to a cluster?
    It seems
    awfully tedious to sit and deploy each individual ejb/war to the cluster
    to get started.
    Thanks!

  • Portal Server on SUN Application Server 8.1 cluster

    Hi,
    I hope can you help me..
    I have a cluster of two instances of application server 8.1.: instance 1 and instance 2.
    Instance 1 is available on machine 1, instance 2 is available on machine 2.
    I have installed PS7 on machine 1 and machine 2 using Configure Later method.
    I have configured a portal with a portal instance on application server instance 1 and that's ok (see sample/psconfig/example14.xml, I have used WebContainerInstanceName=cluster-name ).
    Then I have synchronized SUNWcacao servers on each machine.
    Portal Server is available on application server instance 1, but not on application server instance 2 (but instance1 and instance 2 are in cluster!!!).
    How can I made available Portal Server instance on application server instance 2?
    Thank you...

    That URL you have posted is SUN internal, can you past that information about portal on AS Cluster to public? I'm interested in this too.
    Thanks a lot.
    Petr

  • How to configure datasync proxy for a cluster

    Hi,
    I am in the process of configuring Portal on a cluster and can not get the sync server
    to syncronize the data with the managed server's repositories.
    I configured "SyncServer" as a managed server and deployed a separate webapp "datasyncproxy",
    which is a copy of the datasync webapp. I configured the DataSyncServlet parameters
    to communicate with the managed servers' datasync applications.
    For some reason the master repository running on "SyncServer" does not recognize
    that it needs to syncronize with managed servers. My master repository on the "SyncServer"
    indicates that it is using read-only JDBC persistence store. The deployment guide
    document states that I should set java.lang.System property: data.sync.jdbc.master.dr=true,
    but I do not know where to do it.
    Could anyone help?
    Thanks
    Mike

    Thanks for the news Daniel,
    I've heard these news from your colleagues at CO office. They are keeping me
    in the loop.
    It would be nice however if somebody at BEA could update the portal
    deployment guide. There are too many inconsistencies related to deployment
    on a cluster.
    Thanks again
    Michael Goldverg
    "Daniel Selman" <[email protected]> wrote in message
    news:[email protected]...
    Mike,
    You may be pleased to know that we've spent some time on this for the 7.0
    release.
    In WLP 7.0 the DataSyncServlet running on an admin machine in a clustercan
    auto-discover DataSyncServlets running on managed nodes. This allows youto
    just deploy the out-of-the-box datasync.war to all your cluster nodes - no
    need to set any system properties or WebApp properties. We still supportthe
    explicit registration (as in 4.0) for backwards compatability and to allow
    customers to set up sync networks that cross clusters or for more advanced
    configurations.
    Sincerely,
    Daniel Selman
    "Michael Goldverg" <[email protected]> wrote in message
    news:[email protected]...
    Good news, issue is RESOLVED.
    Several things need to be done:
    1. Copy p13n_util.jar to the WEB-INF/lib directory under the datasyncwebapp, which
    is used as a proxy. This needed to be done because of the problems withthe class
    loader.
    2. The BEA Deployment guide has several discrepancies, so the parametersfo synchronization
    with managed servers should be defined for the webapp itself, not for
    the
    servlet.
    This could be done using the deployment descriptor edit from the
    console.
    Also, the
    document states the name for URL parameter as "notifiedURL" (incorrect),should be
    "notifiedUrl".
    3. In the startup parameters for the WLPortal server, running the proxydatasync
    application the following parameter should be added:"-Ddata.sync.jdbc.master.dr=true".
    4. Finaly, the datasync connection pool and TX datasource should bedeployed on all
    servers (sync server and managed servers).
    It took us 2 days to figure this out, but it works well now.
    Regards, Michael Goldverg
    "Michael Godlverg" <[email protected]> wrote:
    Hi,
    I am in the process of configuring Portal on a cluster and can not get
    the
    sync server
    to syncronize the data with the managed server's repositories.
    I configured "SyncServer" as a managed server and deployed a separatewebapp
    "datasyncproxy",
    which is a copy of the datasync webapp. I configured the
    DataSyncServlet
    parameters
    to communicate with the managed servers' datasync applications.
    For some reason the master repository running on "SyncServer" does notrecognize
    that it needs to syncronize with managed servers. My master repository
    on
    the "SyncServer"
    indicates that it is using read-only JDBC persistence store. Thedeployment
    guide
    document states that I should set java.lang.System property:data.sync.jdbc.master.dr=true,
    but I do not know where to do it.
    Could anyone help?
    Thanks
    Mike

  • Weblogic Portal Console Administration and SSO

    Hello!
    I have integrated Oracle Weblogic Server(10.3.2) with Oracle Identity Manager to achive Single Sign On. In IDM is set form login.
    My base_domain configuration is : AdminServer and a Cluster_0 with two managed servers : Server_1 and Server_0.
    I have as proxy server : Oracle HTTP Server (OHS) for each server : Admin-Server, Server-0, Server-1.
    I targeted my portal app to cluster. My portal application contains Portal Administration Console, avaibled at /myAppAdmin.
    Security Providers are (in this order):
    1. OAMIDAsserter - Oracle Access Manager Identity Asserter( Control Flag : REQUIRED, Active Types : ObSSOCookie)
    2. OIDAuthentificator - Provider that performs LDAP authentication (Control Flag: SUFFICIENT )
    3. DefaultAuthenticator - Weblogic Authentication Provider ( Control Flag : SUFFICIENT
    4. DefaultIdentityAsserter - Weblogic Identity Assertion provider.
    When I access Portal Administration Console from /myAppAdmin (admin-tools.war)
    1. I login first in IDM with the user from LDAP : weblogic_ldap. The login is ok and the ObSSOCookie is set.
    2. I am redirected to login from Portal Administration Console (this thing is wrong and I want to jump this step. I want to go directly in Portal Administration Console after the first login).
    3. I login in the second login page from Portal Administration Console with the same user : weblogic_ldap. The login has succeed.
    4. I am logged in Portal Administration Console and I can add content ( for exemple)
    What I have to do to have only the login form from IDM. To have the only two steps:
    1. Login in Portal Administration Console using login form from IDM and a LDAP user
    2. Access the Portal Administration Console
    I have tried :
    I have changed domain security Default Model : "Advanced" , set Combined Role Mapping Enabled to "FALSE", set Check Roles and Policies to
    "ALL Web applications and EJBs" and selected for When Deploying Web Applications or EJBs: "Ignore roles and policies to DD".
    After this changes I deployed myApp which contains /myAppAdmin Console with Security policies set to Advanced.
    I have only the IDM login, the correct one, and after that I am able to see first page of the Portal Administration Console and whatever I click I receive the error:
    ####<Mar 29, 2011 11:20:55 AM EEST> <Error> <netuix> <server0-dns> <Server-0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <1301386855474> <BEA-423142> <The control com.bea.netuix.servlets.controls.page.SingleLevelMenu could not be rendered properly due to the following error:
    com.bea.p13n.entitlements.common.PolicyMgmtAccessException: Attempt to access Entitlement Policy Mgmt API by user in invalid role. Entitlement Policy operation attempted by disallowed user ["principals=[]"].
    at com.bea.p13n.entitlements.management.internal.SecurityHelper.isWLPAdminRole(SecurityHelper.java:937)
    at com.bea.p13n.entitlements.management.internal.RolePolicyDelegate.roleExists(RolePolicyDelegate.java:346)
    at com.bea.p13n.delegation.DelegationService.getParentInheritanceFlag(DelegationService.java:189)
    at com.bea.p13n.delegation.DelegationService.getAdminPolicies(DelegationService.java:753)
    at com.bea.p13n.delegation.DelegationService.isAdminPolicyOnResourceRoot(DelegationService.java:450)
    at com.bea.p13n.delegation.DelegationService.isAdminPolicyOnResourceRoot(DelegationService.java:430)
    at com.bea.jsptools.common.ToolsMenuTag.hasMenuAccess(ToolsMenuTag.java:354)
    at com.bea.jsptools.common.ToolsMenuTag.doStartTag(ToolsMenuTag.java:130)
    I have to modified admin-tools.war or something in domain's security or myApp's descriptors to be able to login in Portal Administration Console
    using only SSO and not both SSO and default login?
    Thank you for helping me.

    Thank you user11089180, this bit me too. The new password of Passw0rd for the system account is really buried in the documentation.

  • Clustering weblogic portal 10.3 with apache plugin

    Hi,
    we have configured a weblogic portal 10.3 cluster with two managed servers. We are using the apache 2.2 plugin module for dispatching.
    It seems for us that the plugin is not working correctly. It dispatches all request only to one server (we have tested it from different client machines). When we kill one of the managed servers the plugin dispatches to the other server which is correct.
    In our test case we have produced a lot of load with two jmeter instances from two machines. All requests are dispachted to one managed server. After the first server runs in an out of memory, the plugin dispachted to the second managed server until this runs also in an out of memory. Therefor we have no real load balancing.
    Here is our httpd.conf configuration:
    <VirtualHost 149.191.201.135:80>
    ServerName localhost
    # ServerAlias adportal adportal.eu.xxx.com
    RewriteEngine on
    RewriteRule ^/$ /adp_war/appmanager/ad01/ad01 [R]
    LimitRequestBody 12582912
    CustomLog "|d:/apache/bin/rotatelogs.exe d:/apache/logs/adportal_access.log 864000" common
    <IfModule mod_weblogic.c>
    WeblogicCluster sis26.eu.xxx.com:8031,sis27.eu.xxx.com:8031     
    MatchExpression *.jsp
    MatchExpression *.do
    MatchExpression *.portal
    MatchExpression *.htm
    MatchExpression *.html
    MatchExpression *.jpg
    MatchExpression *.gif
    ConnectTimeoutSecs 300
    ConnectRetrySecs 1
    MaxPostSize 12582912
    SecureProxy Off
    Debug ON
    WLLogFile d:/apache/debug/global_proxy.log
    WLTempDir "d:/apache/debug\temp"
    DebugConfigInfo On
    </IfModule>
    <Location ~ "/adp_war/(appmanager|portals|portlets|resources|showImage|ShowBinary|framework)">
    SetHandler weblogic-handler
    </Location>
    </VirtualHost>
    Has anyone an idea?
    By the way we have also tested it with the apache 2.0 plugin which also isn't working.

    Hi,
    Were do we set the listen address.
    Even we have the same problem. I have one physical that has the admin server and manager server and other server with just the manager server.
    We have the apache proxy server infront of these clustered server. Our server goes down very frequently even without activity.
    Some time we get the following error but some time there is no exception in the logs.
    ####<Nov 6, 2009 10:05:57 PM CST> <Error> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257566757265> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "634" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@2c88d39[
    POST /spmlws/OIMProvisioning HTTP/1.1
    SOAPAction: http://xmlns.oracle.com/OIM/provisioning/processRequest
    Content-Type: text/xml; charset="UTF-8"
    User-Agent: OIM AD Pwd Sync/1.0
    Content-Length: 1313
    Connection: Keep-Alive
    ]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
    Thread-18 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
    java.io.FileOutputStream.writeBytes(FileOutputStream.java:???)
    java.io.FileOutputStream.write(FileOutputStream.java:260)
    java.io.BufferedOutputStream.write(BufferedOutputStream.java:100)
    ^-- Holding lock: java.io.BufferedOutputStream@214ef14[thin lock]
    java.io.PrintStream.write(PrintStream.java:428)
    ^-- Holding lock: java.io.PrintStream@214ed9e[thin lock]
    sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:191)
    sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:271)
    sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
    sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:120)
    ^-- Holding lock: java.io.OutputStreamWriter@19de784[thin lock]
    java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
    org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:49)
    org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
    org.apache.log4j.WriterAppender.append(WriterAppender.java:147)
    org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:201)
    ^-- Holding lock: org.apache.log4j.ConsoleAppender@19de688[thin lock]
    org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:50)
    org.apache.log4j.Category.callAppenders(Category.java:181)
    ^-- Holding lock: org.apache.log4j.spi.RootCategory@19de3c9[fat lock]
    org.apache.log4j.Category.forcedLog(Category.java:372)
    org.apache.log4j.Category.error(Category.java:300)
    com.thortech.util.logging.Logger.error(Unknown Source)
    com.oracle.xl.spmlws.framework.logger.OraLogger.log(Unknown Source)
    com.oracle.xl.spmlws.ws.server.weblogic.OIMProvisioningImpl.processRequest(Unknown Source)
    sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:???)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:27)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    java.lang.reflect.Method.invoke(Method.java:575)
    weblogic.webservice.component.javaclass.JavaClassInvocationHandler.invoke(JavaClassInvocationHandler.java:127)
    weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:75)
    weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:141)
    weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:542)
    weblogic.webservice.server.Dispatcher.process(Dispatcher.java:200)
    weblogic.webservice.server.Dispatcher.doDispatch(Dispatcher.java:140)
    weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:53)
    weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:100)
    weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:299)
    weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:417)
    weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:286)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:700)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
    weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
    weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3468)
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
    weblogic.security.service.SecurityManager.runAs(Unknown Source)
    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2116)
    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2038)
    weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1372)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
    >
    <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:11:48 PM CST> <Info> <ServletContext-/xlWebApp> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257567108507> <BEA-000000> <action: LogonAction: User 'XELSYSADM' logged on in session jJ2bK0zdx4LPTScXWRMG3jznSQgQsJKqC4YSpMlJ3Q4KCRrGYM9l!-1225252524!NONE!1257567101565>
    ####<Nov 6, 2009 10:11:01 PM CST> <Info> <ServletContext-/xlWebApp> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257567061835> <BEA-000000> <action: LogonAction: User 'XELSYSADM' logged on in session T23kK0ncSs60YfLnZRhpdZDvmL8sq1QQlc7vMLQJSpVQFyvSMvD6!-1225252524!NONE!1257565852875>
    ####<Nov 6, 2009 10:11:14 PM CST> <Info> <ServletContext-/xlWebApp> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257567074087> <BEA-000000> <action: LogonAction: User 'XELSYSADM' logged on in session T23kK0ncSs60YfLnZRhpdZDvmL8sq1QQlc7vMLQJSpVQFyvSMvD6!-1225252524!NONE!1257565852875>
    ####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167000> <BEA-000339> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167003> <BEA-000339> <[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167009> <BEA-000339> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167019> <BEA-000339> <[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167022> <BEA-000339> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167033> <BEA-000339> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
    ####<Nov 6, 2009 10:12:47 PM CST> <Notice> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <Thread-1> <<WLS Kernel>> <> <> <1257567167043> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    ####<Nov 6, 2009 10:12:47 PM CST> <Alert> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <Thread-1> <<WLS Kernel>> <> <> <1257567167048> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    ####<Nov 6, 2009 10:12:47 PM CST> <Notice> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <Thread-1> <<WLS Kernel>> <> <> <1257567167058> <BEA-000365> <Server state changed to FORCE_SUSPENDING>

  • AM zip installer and Portal package installer

    Hello,
    I have installed Sun Application Server 8.2 ( using JES update 1). Now I need to install AM and Portal to a cluster to enable HA. My question is could I use AM zip installer for the installation but use the JES (package) installer for Portal. These are on Solaris 10 boxes.
    Thank you.
    Regards,
    Slak

    I'm not sure but I think you need at least Application Server 9.1 for Portal Server 7.2 (http://docs.sun.com/app/docs/doc/820-2053/gedjt?l=en&a=view&q=portal+server+7.2+requirements). In my setup I had to use Application Server 9.1 but I don't rembmber the exact reason.
    Vincent

  • Problems with Pcd Content after restore EP Portal with online Backup

    Dear Colleagues,
    We have problems to show Pcd Content (Browse and Search) of the Content Administration tab of the EP Portal after restore with a online Backup during Disaster Recovery Test.
    Restore has become on a mirror system of Production environment. Ours EP Portal is a cluster system with the following configuration:
    Production landscape:
    Node 1
    Disk K:\ SAP SCS directory. (Clustered)
    Disk E:\ SAP Central Instance directory (Local)
    Node 2
    Disk E:\ SAP Dialogue Instance directory (Local)
    Disk M:\ SQL Datafiles. (Clustered)
    Disk L:\ SQL Logfiles. (Clustered)
    Disaster Recovery landscape:
    Only a Node
    Disk K:\ SAP SCS directory. (Clustered)
    Disk E:\ SAP Central Instance directory (Local)
    Disk M:\ SQL Datafiles
    Disk L:\ SQL Logfiles
    Portal Version
    J2EE Engine = 6.40 PatchLevel 105424.313
    Portal = 6.0.18.0.0
    After restore, the data base as the SAP application starts
    correctly but when logon in the Portal, the Pcd Content of Content Administration tab
    and to other tabs with similar information is not shown.
    After restore it can be necessary to reactivate some type of configuration, links, etc?, for this type of restore is better to make a backup offline instead of online one?
    We are thankful for any information on the matter.
    Thanks,
    Regards.
    Rafa R.R.

    The issue was solved with a offline backup.

  • How to implement OracleAS Portal Clustering ?

    Dear all,
    Can anybody pls point me to the docs about how to implement OracleAS Portal Cluster (version 10.1.4) ?
    Also, about deploying Portal from development server to production server (using Export Import) , do we have to deploy it to all nodes , or can we just deploy it once to the cluster ?
    Thank you,
    xtanto

    Hello Xtanto,
    The Oracle documentation provides instructions for setting up Oracle Portal in a 'cluster'. For 10.1.2.0.2 and 10.1.4 :
    [5.3|http://download.oracle.com/docs/cd/B14099_19/portal.1014/b19305/cg_advnc.htm#i1046354] Configuring Multiple Middle Tiers with a Load Balancing Router
    Oracle® Application Server Portal Configuration Guide
    10g Release 2 (10.1.4)
    B19305-03
    Alternatively you can also check the enterprise deployment guide :
    [7|http://download.oracle.com/docs/cd/B14099_19/core.1012/b13998/portal.htm#CACHEECD] Installing and Configuring the myPortalCompany Application Infrastructure
    Oracle® Application Server Enterprise Deployment Guide
    10g Release 2 (10.1.2)
    B13998-07
    For deployment from development to production, transport sets can be used :
    [10|http://download.oracle.com/docs/cd/B14099_19/portal.1014/b19305/cg_imex.htm#i1030999] Exporting and Importing Content
    Oracle® Application Server Portal Configuration Guide
    10g Release 2 (10.1.4)
    B19305-03
    Thanks,
    EJ

  • Portal Administration Console Login

    Hello!
    I have integrated Oracle Weblogic Server with Oracle Identity Manager to achive Single Sign On. In IDM is set form login.
    My base_domain configuration is : AdminServer and a Cluster_0 with two managed servers : Server_1 and Server_0.
    I have as proxy server : Oracle HTTP Server (OHS) for each server : Admin-Server, Server-0, Server-1.
    I targeted my portal app to cluster. My portal application contains Portal Administration Console, avaibled at /myAppAdmin.
    Security Providers are (in this order):
    1. OAMIDAsserter - Oracle Access Manager Identity Asserter( Control Flag : REQUIRED, Active Types : ObSSOCookie)
    2. OIDAuthentificator - Provider that performs LDAP authentication (Control Flag: SUFFICIENT )
    3. DefaultAuthenticator - Weblogic Authentication Provider ( Control Flag : SUFFICIENT
    4. DefaultIdentityAsserter - Weblogic Identity Assertion provider.
    When I access Portal Administration Console from /myAppAdmin (admin-tools.war)
         1. I login first in IDM with the user from LDAP : weblogic_ldap. The login is ok and the ObSSOCookie is set.
         2. I am redirected to login from Portal Administration Console (this thing is wrong and I want to jump this step. I want to go directly in Portal Administration Console after the first login).
         3. I login in the second login page from Portal Administration Console with the same user : weblogic_ldap. The login has succeed.
         4. I am logged in Portal Administration Console and I can add content ( for exemple)
    What I have to do to have only the login form from IDM. To have the only two steps:
    1. Login in Portal Administration Console using login form from IDM and a LDAP user
    2. Access the Portal Administration Console
    I have tried :
    I have changed domain security Default Model : "Advanced" , set Combined Role Mapping Enabled to "FALSE", set Check Roles and Policies to
    "ALL Web applications and EJBs" and selected for When Deploying Web Applications or EJBs: "Ignore roles and policies to DD".
    After this changes I deployed myApp which contains /myAppAdmin Console with Security policies set to Advanced.
    I have only the IDM login, the correct one, and after that I am able to see first page of the Portal Administration Console and whatever I click I receive the error:
    ####<Mar 29, 2011 11:20:55 AM EEST> <Error> <netuix> <server0-dns> <Server-0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1301386855474> <BEA-423142> <The control com.bea.netuix.servlets.controls.page.SingleLevelMenu could not be rendered properly due to the following error:
    com.bea.p13n.entitlements.common.PolicyMgmtAccessException: Attempt to access Entitlement Policy Mgmt API by user in invalid role. Entitlement Policy operation attempted by disallowed user ["principals=[]"].
         at com.bea.p13n.entitlements.management.internal.SecurityHelper.isWLPAdminRole(SecurityHelper.java:937)
         at com.bea.p13n.entitlements.management.internal.RolePolicyDelegate.roleExists(RolePolicyDelegate.java:346)
         at com.bea.p13n.delegation.DelegationService.getParentInheritanceFlag(DelegationService.java:189)
         at com.bea.p13n.delegation.DelegationService.getAdminPolicies(DelegationService.java:753)
         at com.bea.p13n.delegation.DelegationService.isAdminPolicyOnResourceRoot(DelegationService.java:450)
         at com.bea.p13n.delegation.DelegationService.isAdminPolicyOnResourceRoot(DelegationService.java:430)
         at com.bea.jsptools.common.ToolsMenuTag.hasMenuAccess(ToolsMenuTag.java:354)
         at com.bea.jsptools.common.ToolsMenuTag.doStartTag(ToolsMenuTag.java:130)
    I have to modified admin-tools.war or something in domain's security or myApp's descriptors to be able to login in Portal Administration Console
    using only SSO and not both SSO and default login?
    Thank you for helping me.
    Edited by: bluerainbow on Mar 29, 2011 2:06 AM

    no idea? :(

  • CTS + error during deployment There is no cluster control instance running on host

    We are running our QA portal in a cluster (3 hosts..one for MS, 1 for ERS, 1 for JC).  The alias for the JC is <jcalias> and the real name of the host is <clustername1).  So depending on which component is one which of the 3 cluster hosts wil dictate which host <jcalias>.
    But when trying to deploy a portal archive via CTS+, we get error:
    Jul 24, 2014 11:18:12... Error: An error occured while starting a cluster instance.
    Jul 24, 2014 11:18:12... Error: There is no clutser control instance running on host sapepqci which is described in SecureStorage .
    The instances, returned by MessageServer [MS host: <msalias>; MS port: 3912], are :
    Name:JM_T1405698721103_0_<clusterhost1>.viacom.com Host:<clusterhost1>                                                        HostAddr: aaa.bbb.ccc.ddd State:5
    Name:JC_<jcalias>_EPQ_14                       Host:_<clusterhost1>.                                                        HostAddr: aaa.bbb.ccc.ddd
    State:5
    Name:JC_<appsrvr1>_EPQ_00                     Host:<appsrvr1_IP>                                                   HostAddr: <appsrvr1_IP>
    State:5
    Name:JC_<appsrvr2>_EPQ_00                     Host:<appsrvr2_IP>                                                    HostAddr: <appsrvr2_IP>
    State:5
    Please check if there is an appropriate running cluster instances. For more inforation check CSN Note 1276366
    Jul 24, 2014 11:18:12... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    I have checked the referenced not.  The profiles all use the JCALIAS as the host name, and in the configtool secure store it's also specified in admin/host/<SID>
    If I change it in the secure store to the real name (clusterhost1) that the message server is giving, it will probably work.  But what happens in the future when, after a cluster resart, <jcalias> gets assigned to <clusterhost2> instead?  I'd rather be able to use the alias in secure store and for the message server to pick that name up and use it.

    Hi David
    Jul 24, 2014 11:18:12... Error: An error occured while starting a cluster instance.
    Jul 24, 2014 11:18:12... Error: There is no clutser control instance running on host sapepqci which is described in SecureStorage .
    You cluster resources are online?
    BR
    SS

  • Unable to integrate file server into KM......

    Hello all,
    I have performed all the steps required to integrate file server with portal(EP6 SP9-cluster installation) on UNIX.
    Under component monitor->repository managers->file server's name I'm unable to see mountinfo running.
    As specified by SAP, "File System Mount Service" gets started automatically.
    Can anybody help me out with this.
    Regards,
    Amol.
    Note:i have performed the same steps on our development server resulting in successful integration.

    Hi Shaun
    Tried both of your suggestions, however neither strategy worked.
    Strategy 1
    Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"   
    Feature un-installed itself during the restart.
    Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services".  However
    this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
    PACKAGE SERVICING COMMANDS:
      /Add-Package            - Adds packages to the image.
      /Remove-Package         - Removes packages from the image.
      /Enable-Feature         - Enables a specific feature in the image.
      /Disable-Feature        - Disables a specific feature in the image.
      /Get-Packages           - Displays information about all packages in the image.
      /Get-PackageInfo        - Displays information about a specific package.
      /Get-Features           - Displays information about all features in a package.
      /Get-FeatureInfo        - Displays information about a specific feature.
      /Cleanup-Image          - Performs cleanup and recovery operations on the image.
    Strategy 2
    Tried installing via powershell, using the following command DISM
    /online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
    All up back to where I started?

  • WSRP in Clustered Environment

    Hi
    I have a complex producer running on weblogic portal 9.2 cluster having 2 managed servers. And i have a load balancer in front of the managed servers. Currently If i consume the application running on these servers through WSRP request are always going to one managed server only, even though I consumed the application through the admin console of my consumer application using the load balancer's ip address.
    PRODUCER WSDL is still having the host name of my 1st managed server so all the requests are going to Managed server 1, load balancing and failover is not happening.
    Could you please help in this how I can make the consumer to hit the load balancer instead of hitting the managed server 1.
    I tried this option but still i am getting the same behaviour. Not sure whether this one is supported when we consume a application through admin console.
    http://e-docs.bea.com/wlp/docs92/federation/Chap-Best_Practices.html#wp1013891
    Thanks
    rajesh ar

    Hi
    I registered the producer using the URL http://*<loadbalancer>*:<port>/<producerWebapp>/producer?WSDL only but the requests are going to http://*<managedserver1>*:<port> when i see the SOAP request in the Wsrp monitor
    Request (Mon Aug 03 16:35:43 EEST 2009) from/to: http://*managedserver-1:8111*/rmweb/producer/wsrp-wlp-ext-1.0/markup
    SOAPAction           "urn:bea:wsrp:ext:v1:getMarkup"
    User-Agent           BEA WebLogic Portal, 9.2 (1096261)
    Content-Type           text/xml; charset=UTF-8
    Cookie           JSESSIONID=ZLTYK2nK34y1QxtpS62B95WGG12Hvk51rm22rqxkxS3QfGw1fm71!-1917481227;Path=/
    Accept-Charset           UTF-8, UTF-8;q=0.8
    Accept           text/xml, application/xml, multipart/related, */*
    I guess I need to edit the wsrp-wsdl-template.wsdl file, but not sure whether I can hardcode the values there instead of referring to the url templates ..
    <wsdl:service name="WSRPService">
    <wsdl:port name="WSRPBaseService" binding="bind:WSRP_v1_Markup_Binding_SOAP">
    <soap:address location="*WSRPBaseService-url-template*"/>
    </wsdl:port>
    <wsdl:port name="WSRPServiceDescriptionService" binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP">
    <soap:address location=*"WSRPServiceDescriptionService-url-template*"/>
    </wsdl:port>
    <wsdl:port name="WSRPRegistrationService" binding="bind:WSRP_v1_Registration_Binding_SOAP">
    <soap:address location="WSRPRegistrationService-url-template"/>
    </wsdl:port>
    <wsdl:port name="WSRPPortletManagementService" binding="bind:WSRP_v1_PortletManagement_Binding_SOAP">
    <soap:address location="*WSRPPortletManagementService-url-template*"/>
    </wsdl:port>
    <wsdl:port name="WLP_WSRP_Ext_Service" binding="wlp-bind:WLP_WSRP_v1_Markup_Ext_Binding_SOAP">
    <soap:address location="*WLP_WSRP_Ext_Service-url-template*"/>
    </wsdl:port>
    </wsdl:service>
    Thanks
    rajesh

Maybe you are looking for