B Troubleshooting

This appendix provides solutions to common issues that occur in WebCenter applications. This includes the following sections:

• Troubleshooting WebCenter Application Configuration Issues

• Troubleshooting WLST Command Issues

• Troubleshooting Discussions Service Issues

• Troubleshooting Instant Messaging and Presence Service Issues

• Troubleshooting Mail Service Issues

• Troubleshooting Portlet Producer Issues

• Troubleshooting Wiki and Blog Issues

• Troubleshooting Worklist Service Issues

• Troubleshooting WebCenter Spaces Import and Export Issues

B.1 Troubleshooting WebCenter Application Configuration Issues

This section includes the following sub sections:

• WebCenter Does Not Display in the Application Deployment Menu in Fusion Middleware Control

• Configuration Options Unavailable

• Configuration Performed in One Application Reflects in Another

B.1.1 WebCenter Does Not Display in the Application Deployment Menu in Fusion Middleware Control

Problem

After logging into Fusion Middleware Control, you cannot find the WebCenter option in the Application Deployment menu.

Solution

Ensure the following:

• Deployed application is an ADF application.

  The WebCenter option does not display for applications that are not developed using ADF.

• Deployed application is up and running.

• Deployed application contains accurate information about MDS repository and partition, and the MDS repository is accessible to the application. To verify this, check the metadata-store-usages section in the adf-config.xml file. For information on MDS, see "Understanding the MDS Repository" in Oracle Fusion Middleware Administrator's Guide.

• Application is packaged with required artifacts to support configuration:

  • adf-jndi-config name space is configured in the application's adf-config.xml file. This is provisioned at design time. The following is an example (the text in bold) of the adf-jndi-config name space:

    <adf-config xmlns="http://xmlns.oracle.com/adf/config"
         xmlns:jndiC="http://xmlns.oracle.com/adf/jndi/config"
         xmlns:ns2="http://xmlns.oracle.com/mds/config"
         xmlns:ns3="http://xmlns.oracle.com/adf/mds/config">
      ...
      ... 
    </adf-config>
    

  • MDSBackingStore is configured in the application's adf-config.xml file. This is provisioned at design time. This section can exist anywhere in the upper adf-config element, for instance, after the end tag of adf-mds-config. For example, see the text in bold in the following snippet:

    <jndiC:adf-jndi-config>
       <jndiC:ConnectionsJndiContext initialContextFactoryClass="oracle.adf.share.jndi.InitialContextFactoryImpl"
            backingStoreURL="META-INF/connections.xml" backingStoreClass="oracle.adf.share.jndi.MDSBackingStore">
       <jndiC:contextEnv value="true" name="cache_application_scope"/>
       </jndiC:ConnectionsJndiContext>
    </jndiC:adf-jndi-config>
    

  • Appropriate listeners exist in the web.xml file to register the MBeans. This is provisioned at design time. For example, see the text in bold in the following snippet of the web.xml file:

    <listener>
       <description>ADF Config MBeans</description>
       <display-name>ADF Config MBeans</display-name>
       <listener-class>oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack</listener-class>
    </listener>
    <listener>
        <description>ADF Connection MBeans</description>
        <display-name>ADF Connection MBeans</display-name>
        <listener-class>oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack</listener-class>
    </listener>
    

• MBeans is registered for the WebCenter application. To verify this:

  1. In Fusion Middleware Control, from the Application Deployment menu, select System MBean Browser.

  2. Locate connection MBeans for your application under Application Defined MBeans > oracle.adf.mbean.share.connection.

  3. Similarly, locate adf-config MBeans for your application under Application Defined MBeans > oracle.adf.mbean.share.config. Figure B-1 shows how the Application Defined MBeans section looks in Fusion Middleware Control.

     If your application consumes producers, then locate the Producer Manager Mbean.

     Figure B-1 Application Defined MBeans

     
     Description of "Figure B-1 Application Defined MBeans"
     
     

• Check the application's diagnostic logs, analyze messages for the modules oracle.adf.mbean.share.connection and oracle.adf.mbean.share.config, and determine what must be done.

B.1.2 Configuration Options Unavailable

Problem

When you try to configure an application in Fusion Middleware Control, the following message displays:

Configuration options currently unavailable. The application application_name might be down, did not start-up properly, or is incorrectly packaged.
Check the log files for further details.

Solution

For information on how to resolve this issue, see Section B.1.1, "WebCenter Does Not Display in the Application Deployment Menu in Fusion Middleware Control."

B.1.3 Configuration Performed in One Application Reflects in Another

Problem

You configured a WebCenter application, but those configurations also show in another application.

Solution

This happens when multiple applications share the MDS partition in the same schema. To resolve this problem, deploy these applications again and ensure that each application uses its own MDS schema and partition combination. For information about creating a MDS repository or configuring an existing WebCenter application to use a different MDS repository or partition, see section "Managing the Oracle Metadata Repository" in Oracle Fusion Middleware Administrator's Guide.

B.2 Troubleshooting WLST Command Issues

This section includes the following sub sections:

• None of the WLST Commands Work

• WLST Commands Do Not Work for a Particular Service

• A Connection with the Name Connection_Name Already Exists

• WLST Shell is Not Connected to the Oracle WebLogic Managed Server Instance

• Application with the Same Name Already Exists in a Domain

• Application with the Same Name Already Exists on a Managed Server

• Already in Domain Runtime Tree Message Displays

B.2.1 None of the WLST Commands Work

Problem

You are unable to run any WLST commands.

Solution

Ensure the following:

• No files other than Python are stored in the WLST source directory: ORACLE_HOME/common/bin/wlst. This directory must contains files with the .py extension only.

  The default set of files in this location contain legal Python files from Oracle. It is possible that a user copied some non-python script to this directory, for example, a backup file or a test python file with syntax errors.

• webcenter-wlst.jar is located at ORACLE_HOME/common/bin/wlst/lib.

• WebCenter WLST files do not have syntax errors. A single file with syntax error can cause problems.

B.2.2 WLST Commands Do Not Work for a Particular Service

Problem

You are unable to run WLST commands for a particular service, and therefore, you cannot configure that service.

Solution

First, run generic non-WebCenter commands, for example, listApplications() and displayMetricTableNames()to verify whether these commands work. If generic commands do not work, then apply the solution described in Section B.2.1, "None of the WLST Commands Work."

If generic commands work, then run test commands to check the sanity of WebCenter-specific commands. In other words, ensure that the WebCenter WLST file for that service has no syntax errors. To verify this, run the appropriate WSLT check command (see Table B-1).

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

Table B-1 File Names and WLST Commands for Web 2.0 Services

Service Name	File Name	WLST Command
Discussions and Announcements	ForumWLST.py	fcpCheck()
Documents	DoclibWLST.py	doclibCheck()
External Applications	ExtAppWLST.py	extCheck()
Group Space Events	CommunityWLST.py	ceCheck()
Instant Messaging and Presence	ImpWLST.py	rtcCheck()
Mail	MailWLST.py	mailCheck()
Producer Help	ProducerHelperWLST.py	producerHelperCheck()
WSRP Producers	WsrpWLST.py	wsrpCheck()
PDK Producers	PdkWLST.py	pdkCheck()
RSS News Feed	RSSWLST.py	rssCheck()
Search	SesWLST.py	sesCheck()
Worklist	BpelWLST.py	bpelCheck()
WebCenter Spaces and SOA	WebCenterSpacesSOAWLST.py	spaceCheck()
Export/Import - WebCenter application	LifecycleWLST.py	lifecycleCheck()
Export/Import - Group Spaces and Template	ExtImpWLST.py	expimpCheck()
WebCenter Help	WebCenterWLSTHelper.py	basicCheck()

B.2.3 A Connection with the Name Connection_Name Already Exists

Problem

You are unable to create a connection with the name connection_name. The following message displays:

A connection with name Connection_Name already exists.

Solution

Connection names are unique across WebCenter applications. This error occurs when you try to create a connection with a name that is already in use. Ensure that you use a unique name for your connection.

B.2.4 WLST Shell is Not Connected to the Oracle WebLogic Managed Server Instance

Problem

The WLST shell is not connected to the managed server on which you want to run WLST commands.

Solution

Run the following command to connect the WLST shell to the managed server:

connect(username, password , serverhost:serverport)

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

B.2.5 Application with the Same Name Already Exists in a Domain

Problem

You are unable to register a producer application. The following message displays:

Another application named "YourApplicationName" exists. Specify the Server on which your application is deployed. Use: server="YourServerName".

Solution

There are multiple applications with the same name in the domain in which you are trying to register your application. This usually happens in a cluster environment, where the same application is deployed to multiple managed servers. If this is the case, specify the name of the server in which you are trying to register this application. For example, run the registerWSRPProducer WLST command with the server argument:

registerWSRPProducer(appName='myApp', name='MyWSRPSamples',url='http://host:port/application_name/portlets/wsrp2?WSDL', server=server_name) 

For command syntax and examples, see "registerWSRPProducer" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

B.2.6 Application with the Same Name Already Exists on a Managed Server

Problem

You are unable to register a producer application. The following message displays:

Another application named "application_name" exists on the server managedServerName.

Solution

There are multiple applications with the same name on the managed server in which you are trying to register your application. This usually happens when applications are assigned different versions. If this is the case, specify the version of the application you want to register. For example, run the registerWSRPProducer WLST command with the arguments server and applicationVersion:

registerWSRPProducer(appName='myApp', name='MyWSRPSamples',url='http://host:port/application_name/portlets/wsrp2?WSDL', 
server=server_name applicationVersion=version of the application) 

For command syntax and examples, see "registerWSRPProducer" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

See also, Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

B.2.7 Already in Domain Runtime Tree Message Displays

Problem

While running a WLST command, the following message displays:

Already in Domain Runtime Tree

Solution

This is a benign message, and therefore, you can ignore it.

B.3 Troubleshooting Discussions Service Issues

This section includes the following sub sections:

• Discussion Forum Cannot Be Enabled in Group Spaces

• Login Does Not Function Properly After Configuring OAM-SSO

B.3.1 Discussion Forum Cannot Be Enabled in Group Spaces

Problem

Discussion services cannot be enabled in any group space, even new group spaces.

Solution

This error may be caused due to various reasons. Check the following:

• Oracle WebCenter Discussions server is up and running and accessible. See, Section 11.1.9, "Testing Discussion Server Connections."

• Administrator User Name (adminUser) property configured for the active discussion connection has administrative privileges on the application root category (the category configured for the WebCenter Spaces). See Section 11.1.3, "Registering Discussion Servers."

  It is not necessary for this user to be a super admin. However, the user must have administrative privileges on the application root category configured for the WebCenter Spaces, that is, the category (on the discussion server) under which all group space discussions and announcement are stored.

• Application root category, where all group space discussions and announcement are stored, exists on the back-end server.

  You can check the application root category ID configured for the WebCenter Spaces application by navigating WebCenter Administration, selecting Services, and then Discussions. See, Section 18.8.1, "Specifying Where Discussions and Announcements are Stored on the Discussions Server."

B.3.2 Login Does Not Function Properly After Configuring OAM-SSO

Problem

When you log into the discussions server after configuring OAM-SSO, a 500 - Internal Server Error occurs.

Solution

This error occurs if the LDAP back-end is already configured for the discussions server and you add a new SSOAuthFactory property to configure SSO instead of editing the existing property.

Go to the Administration page and remove LDAP AuthFactory and SSO AuthFactory properties. If needed, run the following SQL to restore the correct value:

 insert into jiveproperty
 values('AuthFactory.className','oracle.jive.sso.OracleSSOAuthFactory');

Consider the following when configuring OAM-SSO:

• If the discussions server is not configured with the LDAP AuthFactory property already, then you must add a new property to configure SSO:

  AuthFactory.className=Oracle.jive.sso.OracleSSOAuthFactory
  

• If the discussions server is already configured with an LDAP AuthFactory, then you must edit the AuthFactory.className property while configuring SSO and set it to:

  Oracle.jive.sso.OracleSSOAuthFactory
  

B.4 Troubleshooting Instant Messaging and Presence Service Issues

Problem

Buddies are not visible in a custom WebCenter application. Further, the presence status of users is not available.

Solution

Ensure the following:

• IMP connection is configured properly and the base URL and domain values are correct. See, Section 11.2.3, "Registering Instant Messaging and Presence Servers."

• Web Services for the communication server is installed properly and is up and running. For Web Services installation for Oracle WebLogic Communications Server, see the Oracle WebLogic Communication Services Administrator's Guide. For Web Services installation for Microsoft Live Communications Server, see Section 11.2.2.2, "Microsoft Live Communications Server (LCS) Prerequisites."

• Back-end communication server (Oracle WebLogic Communications Server or Microsoft Live Communications Server) is up and running. A quick way to verify this is to ensure that the user can connect to the communication server by using a supported SIP client (Oracle Communicator or Microsoft Communicator).

• User is logged in with valid user credentials and the user exists on the communication server. For Microsoft Live Communications Server, verify that user has provided correct credentials in the external application.

B.5 Troubleshooting Mail Service Issues

This section includes the following sub sections:

• Mail Service is Not Accessible in Secure Mode

• Mail Service is Not Accessible in Non-Secure Mode

• Unable to Create Distribution Lists in the Non-Secure Mode

• Unable to Create Distribution Lists in the Secure Mode

• Unable to Configure the Number of Mails Downloaded

• Unable to Publish and Archive Group Space Mail

B.5.1 Mail Service is Not Accessible in Secure Mode

Problem

You configured the Mail service to function in secure mode, but the service is not accessible.

Solution

Ensure the following:

• IMAP and SMTP ports are specified correctly. See Section 11.3.3, "Registering Mail Servers."

• Properties are set to true in your mail server.

  • mail.imap.Secured = true

  • mail.smtp.Secured = true

B.5.2 Mail Service is Not Accessible in Non-Secure Mode

Problem

You configured the Mail service to function in non-secure mode, but the service is not accessible.

Solution

Ensure the following:

• IMAP and SMTP ports are specified correctly. See, Section 11.3.3, "Registering Mail Servers."

• Properties are set to false in your mail server.

  • mail.imap.Secured = false

  • mail.smtp.Secured = false

B.5.3 Unable to Create Distribution Lists in the Non-Secure Mode

Problem

You are unable to create group space distribution lists in non-secure mode (SSL not configured).

Solution

Check if the mail server has been reinstalled or the user has been deleted. Also ensure that the following parameters are configured accurately in non-secure mode, in the LDAP server:

• ldapHost

• defaultUser

• ldapAdminPassword

• ldapBaseDN

• ldapPort

See, Section 11.3.3, "Registering Mail Servers."

B.5.4 Unable to Create Distribution Lists in the Secure Mode

Problem

You are unable to create group space distribution list in secure mode, that is, SSL is configured on the LDAP server.

Solution

Check if the mail server has been reinstalled or the user has been deleted. Also ensure that the following parameters are configured accurately in secure mode, in the LDAP server:

• ldapHost

• defaultUser

• ldapAdminPassword

• ldapBaseDN

• ldapPort

• ldap.connection.secure, 'true'

See, Section 11.3.3, "Registering Mail Servers."

B.5.5 Unable to Configure the Number of Mails Downloaded

Problem

You cannot configure how many mails are downloaded to each user's Inbox.

Solution

Use the setMailServiceProperty WLST command. For example, to download 100 mails from the e-mail client, specify the mail.messages.fetch.size parameter as 100, as shown in the following example:

setMailServiceProperty(appName='webcenter',  property='mail.messages.fetch.size', value='100')

For command syntax and examples, see "setMailServiceProperty" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

B.5.6 Unable to Publish and Archive Group Space Mail

Problem

You are unable to archive group space mail.

Solution

If the archiving fails, check the following:

• In WebCenter Spaces, open WebCenter Administration pages, navigate to the Services tab, and then choose Discussions. Check whether the required configuration is accurate. See also, Section 18.8.3, "Enabling Discussion Forums to Publish Group Space Mail."

• Check whether the user account configured here is a member of the distribution list.

• For a particular group space, check whether the forum configured is available in the discussion server. See "Publishing Group Space Mail in a Discussion Forum" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

• Check whether the user who sends emails to the distribution list is available in the discussion server and his email address is the same.

B.6 Troubleshooting Portlet Producer Issues

This section includes the following sub sections:

• Producer Registration Fails for a Custom WebCenter Application

• Portlet Unavailable: WSM-00101 Exception

B.6.1 Producer Registration Fails for a Custom WebCenter Application

This section describes producer registration and portlet unavailability issues.

Problem

You are unable to register a WSRP producer.

Solution

Ensure the following:

• Back-end producer is up and running. To test the producer, access the WSDL URL of the producer through a browser window. See, Section 12.3, "Testing WSRP Producer Connections."

• Producer application is packaged accurately. If not, then register the producer at design time (in JDeveloper), as described in the section "Registering Portlet Producers with a WebCenter Application" in the chapter "Consuming Portlets" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter, and redeploy the application, as described in Section 7.1, "Deploying Custom WebCenter Applications." After redeployment, verify that the packaged application includes the MBean, ProducerManager:

  1. In Fusion Middleware Control, from the Application Deployment menu, select System MBean Browser.

  2. In the Navigator, expand Application Defined MBeans > oracle.webcenter.portlet > Application: application_name > Producer Manager > Producer Manager.

• PortletServletContextListener is added to the web.xml file.

  For applications that support post deployment registration of producers, the producer must be registered at least once at design time. This adds PortletServletContextListener to the web.xml file, which registers the appropriate runtime MBeans to enable post deployment registration of producers. For example, see the text in bold in the following web.xml snippet:

  <listener>
     <description>
        WebCenter Portlet Context Listener
     </description>
     <display-name>
        WebCenterPortletContextListener
     </display-name>
     <listener-class>
        oracle.webcenter.portlet.listener.PortletServletContextListener
     </listener-class>
  </listener>
  

B.6.2 Portlet Unavailable: WSM-00101 Exception

Setting up the User Name with Password token profile in a WSRP portlet producer throws the exception WSM-00101.

Problem

If you configure the User Name with Password Token profile for a WSRP producer through Fusion Middleware Control (or WLST) while portlets associated with this producer are in use, the portlets display the following exception in the WebCenter application:

oracle.wsm.common.sdk.WSMException: WSM-00101: 
The specified Keystore file
/keys/user_projects/domains/pv_0309/config/fmwconfig/default-keystore.jks
cannot be found; it either does not exist or its path is not included in the application classpath.

Solution

Ensure that you have configured the default keystore in your portlet producer. For information, see Section 14.8.4.3, "Setting Up the Keystores."

B.7 Troubleshooting Wiki and Blog Issues

This section describes a possible issue that you may face after configuring OAM-SSO on Oracle WebCenter Wiki and Blog Server.

Problem

After configuring OAM-SSO on Oracle WebCenter Wiki and Blog Server when you log out, the server does not redirect to the login page properly.

Solution

Ensure that the logout_url property is set accurately in the application_config.script file located in the MW_HOME/user_projects/domains/fmw_domain/servers/WLS_Services/stage/owc_wiki/11.1.1.1.0/owc_wiki/WEB-INF/ directory.

B.8 Troubleshooting Worklist Service Issues

The Worklist service relies on several middleware components to display worklist items to logged-in users. Therefore, several factors may cause the Worklist service to fail. The issues and solutions discussed in this section relate to common problems that may be encountered.

This section includes the following sub sections:

• Unavailability of the Worklist Service Due to Application Configuration Issues

• Unavailability of the Worklist Service Due to Server Failure

Note: To identify causes of failures, examine log files on the managed servers hosting Worklist service processes and the managed servers for any SOA BPEL servers you have configured.

B.8.1 Unavailability of the Worklist Service Due to Application Configuration Issues

Issues described in this section pertain to the unavailability of the Worklist service—Worklist task flows display the message The Worklist service is unavailable with the following warning:

Either no BPEL connections are configured, or there is an issue with the existing connection configuration. Verify that at least one BPEL Worklist connection is configured for this application, and that no unresolved "ConfigurationExceptions" exceptions are logged.

This section includes the following sub sections:

• adf-config.xml Refers to a Non-Existent BPEL Connection

• adf-config.xml Has No Reference to a BPEL Connection

• No Rows Yet Message Displays

B.8.1.1 adf-config.xml Refers to a Non-Existent BPEL Connection

Problem

The connection listed in the adf-config.xml file does not exist in the application's connections.xml file. The following entries exist in the diagnostic log file for the managed server on which the application is running:

[2009-03-22T13:33:54.140+00:00] [DefaultServer] [WARNING] [WCS-32008] [oracle.webcenter.worklist.config][tid: [ACTIVE].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] userId: user][ ecid: 0000I0iOmdTFk3FLN2o2ye19kTB0000V,0][APP: Worklist#V2.0 arg: Human Resources The BPEL Connection named 'connection_name' was not present in the connections.xml file. This will prevent the Worklist service from being able to interact with the required this BPEL connection.

Solution

Either create a BPEL connection with the name stated in the log, or remove the connection. For more information about how to update the Worklist configuration post deployment, see Section 11.5, "Setting Up Connections for the Worklist Service."

During development, refer to the chapter "Integrating the Worklist Service" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

To find out which connections names are referenced and to validate the Worklist service configuration, run the WLST command, listWorklistConnections(appName='myApp', verbose=true). For more information, see "listWorklistConnections" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

B.8.1.2 adf-config.xml Has No Reference to a BPEL Connection

There is no reference to a Worklist service connection in the application's adf-config.xml, but this connection exists in the connections.xml file.

Problem

In diagnostic log files for the managed server on which the application is running, you see entries such as the following:

[2009-03-23T10:23:56.943+00:00] [DefaultServer] [WARNING] [WCS-32009] [oracle.webcenter.worklist.config] [tid: [ACTIVE].ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: user] [ecid: 0000I0mqx8Fk3FLN2o2ye19lqBV000008,0] [APP: Worklist#V2.0] The Worklist service does not have a ConnectionName configuration entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the Worklist service was not configured for this application.

Solution

Configure a connection to at least one BPEL server so that the Worklist service can query worklist items.

Post deployment, create Worklist connections through WLST or Fusion Middleware Control. For information, see Section 11.5, "Setting Up Connections for the Worklist Service." During development, create Worklist connections through Oracle JDeveloper. For information, see the chapter "Integrating the Worklist Service" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

B.8.1.3 No Rows Yet Message Displays

Problem

The Worklist task flow continues to display the No Rows Yet message.

Solution

The following are possible solutions to address this problem:

• No 'Assigned' worklist items exist for the logged in user:

  If worklist items are assigned to the logged-in user and the state of these items is Assigned, then they always show in the Worklist task flow. The No Rows Yet message indicates that no assigned Worklist items exist for the logged-in user. This is not an issue, but expected behavior.

  To confirm that this message is displaying correct information, open the Oracle SOA Suite BPEL Worklist application, and check whether any worklist items exist. The URL of BPEL Worklist application is: http://host:port/integration/worklistapp. Where host and port are the same as those used in the Worklist connection.

• The ADF page on which the Worklist task flow exists is not ADF-secured:

  The Worklist task flow is not able to query the Worklist repository, because there is no authenticated user associated with the application session to access the Oracle SOA Suite BPEL server. Apply the ADF security on the page. For information, see the section "Setting Security for the Worklist Service in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

B.8.2 Unavailability of the Worklist Service Due to Server Failure

Server failure is the likely cause of an issue if a Worklist service connection exists, and the Worklist task flow shows the The Worklist service is unavailable warning. In case of multiple connections, the More items not currently available message displays. These generic warning messages display when there is an issue with Worklist service interactions with the Oracle SOA Suite BPEL repository.

To identify the root cause of the issue, examine the managed server's diagnostic logs at the time when the service fails. In some cases it is necessary to also examine the log files of the managed server on which Oracle SOA Suite BPEL processes are running. Typically, an entry such as the following exists in diagnostic logs of the Worklist application's managed server:

[2009-03-23T11:35:21.735+00:00] [DefaultServer] [ERROR] [WCS-32100] [oracle.webcenter.worklist.model] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: user] [ecid: 0000I0n7GBZFk3FLN2o2ye19lrBX00000L,0] [APP: Worklist#V2.0] [arg: WebCenter Worklist] The WebCenter Worklist has queried the BPEL Worklist connection named 'WebCenter Worklist', and encountered a WebCenter Executor error. Please see related exception for details. If the WebCenter Worklist is running in an Application Server, check to see if the wsm-pm application is up and running.

This states that there is an issue with the wsm-pm application. There can also be some other causes related to the exception. It is recommended that you examine the logged exceptions when these issues occur.

This section includes the following sub sections:

• Users Mismatch in Identity Stores

• Shared User Directory Does Not Include the weblogic User

• Issues with the wsm-pm Application

• Clocks are Out of Sync for More Than Five Minutes

• Worklist Service Timed Out or is Disabled

B.8.2.1 Users Mismatch in Identity Stores

Mismatch in identity stores used by the managed server on which the Worklist service task flow is running and that of the Oracle SOA Suite BPEL server.

Problem

If a user exists in the Worklist managed server's identity store but not in the Oracle SOA Suite's identity store, then the following messages display:

In the diagnostic logs of the Worklist service's managed server:

[2009-03-23T11:35:21.407+00:00] [DefaultServer] [ERROR] []
[oracle.webcenter.worklist.config] [tid: pool-1-daemon-thread-12] [userId: Luke]
[ecid: 0000I0n7GBZFk3FLN2o2ye19lrBX00000L,0:1:3] [APP: Worklist#V2.0] Error in
workflow service Web service operation invocation.[[
Error in workflow service Web service operation invocation. The error is .
Verify that the SOAP connection information for the server is correct.
 ORABPEL-30044
Error in workflow service Web service operation invocation.
Error in workflow service Web service operation invocation. The error is .
Verify that the SOAP connection information for the server is correct.
    at
oracle.bpel.services.workflow.query.client.TaskQueryServiceSOAPClient.convertSOAPF
aultException(TaskQueryServiceSOAPClient.java:242)
    at
oracle.bpel.services.workflow.query.client.TaskQueryServiceSOAPClient.invoke(TaskQ
ueryServiceSOAPClient.java:203)
    at
oracle.bpel.services.workflow.query.client.TaskQueryServiceSOAPClient.authenticate
(TaskQueryServiceSOAPClient.java:253)
    at
oracle.bpel.services.workflow.query.client.AbstractDOMTaskQueryServiceClient.authe
nticate(AbstractDOMTaskQueryServiceClient.java:164)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.webcenter.concurrent.MethodTask.call(MethodTask.java:34)
    at oracle.webcenter.concurrent.Submission$2.run(Submission.java:492)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.webcenter.concurrent.Submission.runAsPrivileged(Submission.java:499)
    at oracle.webcenter.concurrent.Submission.run(Submission.java:433)
    at
oracle.webcenter.concurrent.Submission$SubmissionFutureTask.run(Submission.java:779)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at
oracle.webcenter.concurrent.ModifiedThreadPoolExecutor$Worker.runTask(ModifiedThre
adPoolExecutor.java:657)
    at
oracle.webcenter.concurrent.ModifiedThreadPoolExecutor$Worker.run(ModifiedThreadPo
olExecutor.java:682)
    at java.lang.Thread.run(Thread.java:619)
]]
[2009-03-23T11:35:21.735+00:00] [DefaultServer] [NOTIFICATION] []
[oracle.webcenter.worklist.config] [tid: pool-1-daemon-thread-15] [userId: Luke]
[ecid: 0000I0n7GBZFk3FLN2o2ye19lrBX00000L,0:1:6] [APP: Worklist#V2.0]
TaskServiceSOAPClient: soapFault:[[
<env:Fault
xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece
xt-1.0.xsd"xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <faultcode>ns0:FailedAuthentication</faultcode>
   <faultstring>FailedAuthentication : The security token cannot be authenticated
or authorized.</faultstring>
   <faultactor/>
</env:Fault>
]]

In the diagnostic logs of the Oracle SOA Suite's managed server:

[2009-03-23T04:52:07.909-07:00] [soa_server1] [ERROR] [WSM-00008] [oracle.wsm.resources.security] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000I0nB64fFk3FLN2o2ye19lrBX00000O,0:1:3:1] [WEBSERVICE_PORT.name: TaskQueryServicePortSAML] [APP: soa-infra] [J2EE_MODULE.name: /integration/services/TaskQueryService] [WEBSERVICE.name: TaskQueryService] [J2EE_APP.name: soa-infra] Web service authentication failed.

Solution

The same users must exist in identity stores of both managed servers. For information, see the section "Setting Security for the Worklist Service in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

This can be easily accomplished through the use of a common LDAP identity store. A useful sanity check is to validate that you can log into the Oracle SOA Suite's BPEL Worklist application with the user ID for which the Worklist service is unavailable. That is, try accessing the integration Worklist application at: http://host:port/integration/worklistapp. Where the host and port are the same as those used in the Worklist connection for the task flow application.

B.8.2.2 Shared User Directory Does Not Include the weblogic User

Problem

BPEL Web services cannot respond to requests received from the Worklist service because the shared user directory does not include the weblogic user.

Solution

Ensure that you have tried the solution provided in Users Mismatch in Identity Stores. If that solution did not resolve the issue, then try the solution described in this section.

If Oracle SOA Suite is connected to a shared user directory (LDAP), and the user weblogic does not exist in the identity store, then the following step assigns the BPMWorkflowAdmin role to a valid user in the identity store. Use WLST to revoke an application role from SOAAdmin and grant it to a member of the external identity store. This can be done by running the following WLST command from the SOA ORACLE_HOME. For example:

cd ORACLE_HOME/common/bin/
wlst.sh
connect('weblogic','weblogic', '## soa host ##:## soa administration port ##')
revokeAppRole(appStripe="soa-infra", appRoleName="BPMWorkflowAdmin",
     principalClass="oracle.security.jps.service.policystore.ApplicationRole", principalName="SOAAdmin")
grantAppRole(appStripe="soa-infra", appRoleName="BPMWorkflowAdmin",
     principalClass="weblogic.security.principal.WLSUserImpl", principalName="user")

In this example, the LDAP identity store has a user named user. If the user to which you want to grant the BPMWorkflowAdmin role does not exist in the LDAP identity store, then you must restart the Oracle SOA Suite's managed server to make this change effective.

B.8.2.3 Issues with the wsm-pm Application

Problem

Issue with the wsm-pm application on either the Worklist service's managed server, or the Oracle SOA Suite's managed server, or on both.

Solution

The wsm-pm application manages the Web service security policies that control the SAML authentication in the Worklist service. To validate this, log into the wsm-pm application's validation page as a user with administrative rights. Use this format for validation: http://host:port/wsm-pm/validator. If there are no issues with this application, then accessible policies must display. If policies do not display, then investigate the related logged information on the server whose wsm-pm application is failing.

B.8.2.4 Clocks are Out of Sync for More Than Five Minutes

Due to security reasons, the Web service security interaction between the Worklist service's managed server and that of the Oracle SOA Suite BPEL must take place with a time difference of less than five minutes. That is, the clocks on both host machines must have a time difference of less than five minutes, otherwise authentication fails. The SAML assertion uses the NotBefore condition to verify this.

Problem

Clocks of the Worklist service's managed server and the Oracle SOA Suite BPEL's managed server are out of sync for more than five minutes.

Solution

Ensure that the current time is not set to earlier than the SAML assertion's clockskew, which is 300 seconds by default.

Either match the time on the client and service machines, or configure the agent.clock.skew property (in seconds) in the policy-accessor-config.xml file. This file is located in the DOMAIN_HOME/config/fmwconfig directory.

B.8.2.5 Worklist Service Timed Out or is Disabled

Problem

The Worklist service is unable to obtain a query result from the Oracle SOA Suite BPEL server within a defined period of time.

The Worklist service issues queries to the Oracle SOA Suite BPEL server using concurrent threads. These threads are allotted a certain amount of time in which to respond. If these threads do not respond in the allotted time, for example 15 seconds, then the Worklist service times out the call, and it allows the task flow to display the unavailability message. In such a case, log files include related exceptions such as the following:

[2009-03-03T12:09:34.769-08:00] [WLS_Spaces] [ERROR] [WCS-32103]
[oracle.webcenter.worklist.model] [tid: [ACTIVE].ExecuteThread: '3' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: user] [ecid:
0000HzDx68KC0zT6uBbAEH19fOWs00002q,0] [APP: webcenter] Unable to query BPEL repository.[[
oracle.webcenter.concurrent.TimeoutException: Execution timedout
      queued :     1 ms
   suspended :     0 ms
     running : 15389 ms
     timeout : 15000 ms
     service : Worklist
    resource : ir
      source : oracle.webcenter.concurrent.CallableTask@bf3952
(oracle.webcenter.concurrent.CallableTask)
  submission : 150
        at
oracle.webcenter.concurrent.Submission.transitionTo(Submission.java:595)
        at oracle.webcenter.concurrent.Submission.timeout(Submission.java:634)
        at
oracle.webcenter.concurrent.InternalExecutorService.checkForTimeouts(InternalExecutorService.java:566)
        at
oracle.webcenter.concurrent.InternalExecutorService.access$300(InternalExecutorService.java:18)
        at
oracle.webcenter.concurrent.InternalExecutorService$1.run(InternalExecutorService.java:352)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)]]

Solution

If errors such as this occur consistently, then there may be fundamental issues with the resources available to the managed servers running the Worklist service and the Oracle SOA Suite BPEL server.

Validate that the volume of users and resources provided is adequate to run these servers in the infrastructure provided.

Note: continuous occurrence of TimeoutExceptions can also disable the Worklist service. Due to which this service cannot connect to the BPEL instance that is failing to respond in a timely manner. In such a case, the logs contain oracle.webcenter.concurrent.DisabledException exceptions. These exceptions are related to the Worklist service failure.

B.9 Troubleshooting WebCenter Spaces Import and Export Issues

This section contains the following subsections:

• ResourceLimitException Issue

• Page or Group Space Not Found Message After Import

B.9.1 ResourceLimitException Issue

This section provides the solution to resolve the ResourceLimitException issue which occurs during export.

Problem

In WebCenter Spaces, you try to export all group spaces or entire application and the following error displays:

Weblogic.common.resourcepool.ResourceLimitException

Solution

You must increase the maximum capacity in the JDBC connection pool. To do this, log into the WLS Administration Console. From Services, select Data Sources, JDBC, and then the Connection Pool tab.

B.9.2 Page or Group Space Not Found Message After Import

When users first login to WebCenter Spaces after an import operation they will see a "Page not found" or "Group space not found" if the page or group space they last visited no longer exists. Last accessed page information is retained during import operations which is why the message displays in such instances.

B.9.3 Group Space Import Exceed Maximum Upload File Size

There is a file size limitation uploading content to WebCenter Spaces. If your export archive exceeds the maximum upload size then the import operation through WebCenter Spaces administration will fail.

Import the group space archive using WLST. See Section 16.1.9.2, "Importing Group Spaces Using WLST".

Alternatively, modify the content repository upload parameters in web.xml. See Editing web.xml.