Tuesday, October 5, 2010

Invalid xsi:type qname: wsrp:wsrp-identity-asserterType – Weblogic Portal


While starting Admin server using WLST in a domain which supports Weblogic Portal, the admin server does not starts and errors out with the following errors in the WLST console:

Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer': java.io.IOException: Server failed to start up. See server output log for more details.

The output log file says this:

BEA-141244 Schema validation errors while parsing /admin_server/admin/domains/portal_domain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://www.bea.com/ns/weblogic/920/domain
Error Management BEA-141244 Schema validation errors while parsing /admin_server/admin/domains/portal_domain/config/config.xml - /admin_server/admin/domains/portal_domain/unknown:13:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp
Critical WebLogicServer BEA-000362 Server failed. Reason: [Management:141245]Schema Validation Error in /admin_server/admin/domains/portal_domain/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false

Cause.
The domain which we created requires portal libraries to be loaded when any of the servers starts. This can be verified from the config.xml file in which all libraries are targeted to the Admin server and the cluster. When any server is started using WLST the node manager does not reads the setDomain.env file associated with that domain and hence the server is unaware of the path of the library files.

Fix.
Start the Admin server using the startWeblogic.sh script. Navigate to “Servers è Admin Server è Server Start” tab and add the following parameters for “Arguments” section.
-d64 -Dweblogic.ext.dirs=/opt/oracle/product/middleware/patch_wlw1030/profiles/default/sysext_manifest_classpath:/opt/oracle/product/middleware/patch_wls1030/profiles/default/sysext_manifest_classpath:/opt/oracle/product/middleware/patch_wlp1030/profiles/default/sysext_manifest_classpath:/opt/oracle/product/middleware/patch_cie670/profiles/default/sysext_manifest_classpath:/opt/oracle/product/middleware/wlportal_10.3/p13n/lib/system:/opt/oracle/product/middleware/wlportal_10.3/light-portal/lib/system:/opt/oracle/product/middleware/wlportal_10.3/portal/lib/system:/opt/oracle/product/middleware/wlportal_10.3/info-mgmt/lib/system:/opt/oracle/product/middleware/wlportal_10.3/analytics/lib/system:/opt/oracle/product/middleware/wlportal_10.3/apps/lib/system:/opt/oracle/product/middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/oracle/product/middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/oracle/product/middleware/wlportal_10.3/portal/lib/security

*considering that the WL_HOME is /opt/oracle/product/middleware

1 comment:

  1. Hi,

    I'm trying some different scenario.. I'm using WTC in my Weblogic. I want to seperate WTC related config in seperate xml file like same what we have for jdbc/datasource.xml and jms/jmsconfig.xml. Is it possible to do?

    ReplyDelete