OWSM Default UserId/Password:
After installing the 10.1.3.1 SOA Suite, the default userid/password for OWSM is: admin/oracle
Thursday, April 12, 2007
Monday, April 09, 2007
When Using XE with SOADemo you must bump up the default Processes Parameter:
To do that issue the following command and restart XE.
alter system set processes = 100 scope=spfile;
To check the current value of the parameter, use:
show parameters processes;
Also for 11.1.1.4 if you want to use XE you can set the RCU_JDBC_TRIM_BLOCKS environment variable to TRUE prior to running RCU. As a reminder as to support level, when running RCU against XE you will receive a warning stating that the database version is not supported by Oracle.
To do that issue the following command and restart XE.
alter system set processes = 100 scope=spfile;
To check the current value of the parameter, use:
show parameters processes;
Also for 11.1.1.4 if you want to use XE you can set the RCU_JDBC_TRIM_BLOCKS environment variable to TRUE prior to running RCU. As a reminder as to support level, when running RCU against XE you will receive a warning stating that the database version is not supported by Oracle.
Tuesday, March 20, 2007
Advanced SOA Suite 10.1.3.1 Install Issues:
When SOA Suite is installed with Advanced installation option, OWSM console does not use the 'oc4jadmin' user. Instead, OWSM uses its own container for authentication, hence use the username/password of 'admin/oracle' to log into OWSM.
JSSO is not automatically deployed in an advanced installation. Hence JSSO will not work until manual deployment is done. After a manual redeployment of JSSO the 'oc4jadmin' username will work for OWSM login.
Solutions:
Use the username/password combination of 'admin/oracle' to login into OWSM console before deploying JSSO.
To Deploy JSSO
1) In the install.properties file change the value of install.sso.support parameter from false to true.
2) Run the command "$OAS\owsm\bin\wsmadmin deploy all.
3) Login to EM console, start javasso, and then select all the WSM applications to participate in the java SSO.
4) Restart WSM by running wsmadmin stop/start.
5) Restart opmn
Where To Put BPEL XSDs So That OWSM Can See Them:
BPEL by default creates an xsd to go with your BPEL process. Don't forget to copy this .xsd to:
/j2ee/oc4j_soa/applications/gateway/gateway/services
Where 'gateway' is the name you chose for your gateway.
If you don't do this, you'll get an exception stating that the schema contains HTML tags (this happens because the schema file cannot be found and as a result, the server returns a 404 page instead of the schema definition).
When SOA Suite is installed with Advanced installation option, OWSM console does not use the 'oc4jadmin' user. Instead, OWSM uses its own container for authentication, hence use the username/password of 'admin/oracle' to log into OWSM.
JSSO is not automatically deployed in an advanced installation. Hence JSSO will not work until manual deployment is done. After a manual redeployment of JSSO the 'oc4jadmin' username will work for OWSM login.
Solutions:
Use the username/password combination of 'admin/oracle' to login into OWSM console before deploying JSSO.
To Deploy JSSO
1) In the install.properties file change the value of install.sso.support parameter from false to true.
2) Run the command "$OAS\owsm\bin\wsmadmin deploy
3) Login to EM console, start javasso, and then select all the WSM applications to participate in the java SSO.
4) Restart WSM by running wsmadmin stop/start.
5) Restart opmn
Where To Put BPEL XSDs So That OWSM Can See Them:
Where 'gateway' is the name you chose for your gateway.
If you don't do this, you'll get an exception stating that the schema contains HTML tags (this happens because the schema file cannot be found and as a result, the server returns a 404 page instead of the schema definition).