OmniPortlet Migration Issue (10g to 11g - 11.1.1.2)

After migrating from 10g to 11g the out of the box OmniPortlet Provider will use the database as its preference store by default. Therefore, if you did not use the database as a preference store in 10g you will be unable to add the OmniPortlet to a page in your upgraded environment. You will receive the ORA-00942: table or view does not exist. Either change the provider.xml file in the portalTools ear file to use a file-based preference store or run the following script as the PORTAL user in the database.


CREATE TABLE JPDK_PREFERENCE_STORE2 (
  PATH_TYPE       VARCHAR2 (60)  NOT NULL,
  REFERENCE_PATH  VARCHAR2 (250)  NOT NULL,
  SEARCH_PATH     VARCHAR2 (250)  NOT NULL,
  DATA_CLASS      VARCHAR2 (250),
  LONG_VALUE      LONG RAW,
  CONSTRAINT JPS2_PK
  PRIMARY KEY ( REFERENCE_PATH, PATH_TYPE ) ) ;

CREATE INDEX JPDK_PATH_TYPES2 ON
  JPDK_PREFERENCE_STORE2(PATH_TYPE)
;
CREATE INDEX JPDK_SEARCH_PREFS2 ON
  JPDK_PREFERENCE_STORE2(SEARCH_PATH)
;


Here is the error that you will receive when attempting to add the OmniPortlet to a page.

Internal error (WWC-00006)
Unexpected error - User-Defined Exception (WWC-35000)
An unexpected error has occurred in pages: User-Defined Exception (WWC-44847)
Unexpected error - User-Defined Exception (WWC-35000)
The provider URL specified may be wrong or the provider is not running. (WWC-43176)
The following error occurred during the call to Web provider: ORA-00942: table or view does not exist
(WWC-43147)

esb runtime and bpel in separate containers

If esb runtime and bpel are in separate containers, several issues may be encountered.

If opmnctl startall is used, esb container will most likely start before bpel container. If an External Service was created in esb which calls a BPEL process, the External Service will not show up under Web Services in em and the SOAP Endpoint URI will return 'No WebService Provider Found at this URL'. To resolve this, start BPEL fully before starting ESB runtime container.

In HA, if you start Node 1 completely and then start Node 2, you will notice that the Web Service is found in the ESB runtime container on node 2 but not on node 1 unless your HTTP Server is configured to not attempt to go over to the other container on node 1 to grab the wsdl from the BPEL container on node 1.

This can be done by making changes in opmn.xml which I will cover in a later post.