Oracle WebCenter Suite Technical Training Troubleshooting and Analysis

1
Oracle WebCenter Suite Technical
TrainingTroubleshooting and Analysis
2
Diagnosing WebCenter Apps

• WebCenter Logging based on JDK logging API and
  the Oracle Diagnostic Logging (ODL) Framework
• JDK Logging API for configuring Logging
• ODL Framework controls the messages that appear
  and their format
• Loggers Some examples

3
Logging Scope
4
Enable Logging

• Enabled in j2ee-logging.xml
• Available in ORACLE_HOME/j2ee/oc4j_instance/home/c
  onfig
• lthomegt is the name of the OC4J
• XML or Plain Text Format
• For Plain use
• ltproperty name'format' value'ODL-Text'/gt
• ODL Log Level needs to be set for every Logger
• Enable Logging in JDeveloper
• JDEV_HOME/jdev/bin/jdev.conf
• Add OJDL jars in the classpathAddJavaLibFile
  ../../BC4J/lib/ oracle.core.ojdl.logging.LoggingCo
  nfiguration AddVMOPtion -Doracel.core.ojdl.loggin
  g.config.file ltJDEV_HOMEgt/j2ee/home/config/j2ee-l
  ogging.xml
• Restart AS / JDeveloper

5
Enable Logging - Example

• ltlogging_configurationgt
• ltlog_handlersgt
• ..
• ltlog_handler name'ptlLoggingHandler'
  class'oracle.core.ojdl.logging.ODLHandlerFactory'
  gt
• ltproperty name'path' value'C/TEMP/log/diag.log
  '/gt
• ltproperty name'maxFileSize' value'104857600'/gt
  
• ltproperty name'maxLogSize' value'1048576000'/gt
  
• lt/log_handlergt
• lt/log_handlersgt
• ltloggersgt
• ...
• ltlogger name'oracle.adfinternal.model.portlet'
  level'FINER' useParentHandlers'false'gt lthandler
  name'ptlLoggingHandler'/gt
• lt/loggergt
• ltlogger name'oracle.adfdtinternal.model.portlet'
  level'FINER' useParentHandlers'false'gt lthandler
  name'ptlLoggingHandler'/gt
• lt/loggergt
• ltlogger name'oracle.portlet.client' level'FINE'
  useParentHandlers'false'gt lthandler
  name'ptlLoggingHandler'/gt
• lt/loggergt
• lt/loggersgt
• lt/logging_configurationgt

6
Registering SSL Portlet Producers

• By default an exception is thrown
• Certificate needs to be registered
• Open HTTPS URL in Internet Explorer
• Trust Certificate Dialog pops up
• Select View Certificate
• Click on the Certification Path Tab
• Select the Root certificate
• Click on View Certificate again
• Click on Details and choose Copy to File
• Save under ltjdev_homegt\jdk\jre\lib\security\root.c
  er
• Open a Dos box and run Keytool
• keytool -import -file root.cer -keystore cacerts
  -storepass changeit

7
Content DC fails with invalid Path

• When running a JSF page with a Content Data
  Control the following error occursDCA-INCORRECT
  _PATH_PARAMETER Path parameter is incorrect
• Check the Page definition ltNamedData
  NDName"path" NDValue"/tmp/abc"
  NDType"java.lang.String"/gt
• Path needs to start with a /
• Path starts relative to the Base Path defined in
  the Data Control Definition and must exist

8
Unable to deploy to generic EAR

• Error during export in the console
• One of the Portlet Producers is down
• Make sure all portlet producers are up that
  contain portlets which are used in the
  Application
• Portlet Meta-data pointing to a producer although
  Portlet is not used in Application
• Remove any invalid PortletMDS entries

9
MDS Error in Pre-deployment Tool

• When running the Pre-deployment Tool you see the
  following errorUnable to find MDS Repository
  for Portlet Producers
• Check if the generic EAR file has been created
  using the WebCenter Application WAR Deployment
  Profile
• If not, add this deployment profile and generate
  the EAR file again

10
Error in Pre-deployment Tool - 2

• When running the Pre-deployment Tool you see the
  following error"Unexpected PortletException"
  or "Error during import"
• Check if the Target Producer/Provider is up and
  running

11
Deployed CI Application fails

• Deployed Content Integration Application fails
  with error DCA-CONNECTION_LOOKUP_FAILED
  Failure looking up the repository connection
• The Deployment Profile does not contain/contains
  a wrong target platform
• Create connection to target AS and assign it in
  the WebCenter Application WAR deployment profile

12
All portlets in deployed App fail

• All portlets on a deployed application show the
  same error"No object with ID
  /oracle/adf/portlet/..."
• No errors running the pre-deployment tool
  indicate this problem
• The Deployment Profile does not contain/contains
  a wrong target platform
• Create connection totarget AS and assignit in
  the WebCenterApplication WARdeployment
  profile

13
WinXP SP2 prevents running page

• Run Page in JDeveloper and get the following
  error "Cannot find class java\lang\StackOverflow
  Error"
• WinXP SP2 introduces a feature called Data
  Execution Prevention (DEP)
• Configure DEP to allow JDeveloper execute pages
• Control Panel -gt System -gt Advanced -gt
  Performance
• Add jdev.exe and jdevw.exe
• Restart computer

14
Portal Adapter Deployment

• Data Source needs to be deployed
• Implicitly created when creating a DB connection
  for the Portal Adapter
• Automatically deployed from JDeveloper when
  Deployment Profile is configured correctly with
  AS connection
• Can be manually created using EM

15
Portal Adapter Deployment

• Connection Pool is mandatory to be set-up for
  performance reasons
• Min/max connections gt 1
• Best performance with Application in same Subnet
  as Portal Meta-data repository database
• Can be done in JDeveloper
• Embedded OC4J Preferences
• Needs to be done Post-deployment in EM

16
Portal Adapter Deployment

• Change Portal repository connection post
  deployment in EM
• Create a new connection pool
• Delete the existing Portal Repository Data Source
  (remember the JNDI Name)
• Create a Data Source using the same JNDI name and
  the new connection pool
• Restart OC4J