Oracle SOA Suite Online Training

Interested in learning Oracle SOA Suite 12c?
Learn from the author of this blog!
A complete and comprehensive course on the #1 platform on SOA - Oracle SOA Suite

Click here to find the complete course details
Click here to check the first session on Oracle SOA Suite 12c

================================================================================================

Weblogic Server startup problem after password change

When you change the password of weblogic in console and restart, you might endup with the following error - due to the fact that the new password might not sync in all the places

<21-Feb-2014 11:58:22 o'clock GMT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied

at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
...
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
<21-Feb-2014 11:58:22 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<21-Feb-2014 11:58:22 o'clock GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<21-Feb-2014 11:58:22 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<21-Feb-2014 11:58:22 o'clock GMT> <Info> <WebLogicServer> <BEA-000236> <Stopping execute threads.> 


For this,
Navigate to /oracle/fmwhome/user_projects/domains/dev_soa_osb/servers/AdminServer/data
Remove complete ldap folder
Remove boot.properties in /oracle/fmwhome/user_projects/domains/dev_soa_osb/servers/AdminServer/security
Restart

Upload assets to OER from local machine

When you create a new Asset in OER, by default, OER 'Asset Submission' windows gives only 'Attach file by reference' / http url option.
To upload files from local into OER, you first have to enable the local upload option. It can done in the following way

Login to OER console using admin credentials
Go to Admin --> System Settings --> Search for the property 'cmee.server.paths.upload' and provide the path for the uploaded assets to be saved --> Save



Enable Policy tab in Oracle Enterprise Repository

Policies enable asset compliance requirements to be enforced. You can have your custom policies defined based on your enterprise group policy.

By default, Policy tab is not enabled in OER. You can enable it in the following way

Login to OER console using admin credentials
Go to Admin --> System Settings --> Search for the property 'cmee.asset-policy.enable' and set it to true --> Save



Clear MDS Cache

Whenever there is a change in MDS artifacts, and the change do not reflect, or you get a 'duplicate' instance issue, clear MDS cache.

You can clear MDS cache via EM



Open .jnlp files in Linux

when you open the .jnlp files in linux directly, it might not work.
You just have to go to the javaws path in your jdk installation, and issue the following command

javaws /complete/path/of/jnlp

And it runs!

Oracle Service Registry Installation - Schema Requirements

Just like any other fusion product installations, OSR also needs certain schemas to be in Oracle database prior to installation.

Though we don't have any readymade RCU like in SOA, the schemas required for OSR installation are very few, so execute the following commands

Log into Oracle (system or DBA privileges are required).
Create a data tablespace named OSR_TABLESPACE with at least 50M of available space.

CREATE TABLESPACE OSR_TABLESPACE LOGGING
 DATAFILE 'OSR.DBF' SIZE 50M REUSE AUTOEXTEND
 ON NEXT 10M MAXSIZE UNLIMITED
 DEFAULT STORAGE (
  INITIAL 5M
  NEXT 5M
  MINEXTENTS 1
  MAXEXTENTS UNLIMITED
  PCTINCREASE 50);

CREATE USER OSR
 PROFILE DEFAULT
 IDENTIFIED BY welcome1
 DEFAULT TABLESPACE OSR_TABLESPACE
 TEMPORARY TABLESPACE TEMP
 ACCOUNT UNLOCK;

GRANT CONNECT TO OSR;
GRANT RESOURCE TO OSR;
GRANT UNLIMITED TABLESPACE TO OSR;
GRANT CREATE ANY SYNONYM TO OSR;
GRANT DROP ANY SYNONYM TO OSR;

Once the above sql's are executed, run the installer.
Hope this helps.

Oracle Enterprise Repository Installation - Schema Requirements

Just like any other fusion product installations, OER also needs certain schemas to be in Oracle database prior to installation.

Though we don't have any readymade RCU like in SOA, the schemas required for OER installation are very few, so execute the following commands

Log into Oracle (system or DBA privileges are required).
Create a data tablespace named OER_DATA with at least 300M of available space.
Create an index tablespace named OER_INDEX with at least 300M of available space.

CREATE TABLESPACE OER_DATA
 DATAFILE 'oer_data.dbf' SIZE 100M AUTOEXTEND ON
NEXT 10240K MAXSIZE UNLIMITED
 EXTENT MANAGEMENT LOCAL AUTOALLOCATE
 LOGGING
 ONLINE
 SEGMENT SPACE MANAGEMENT AUTO;

CREATE TABLESPACE OER_INDEX
 DATAFILE 'oer_index.dbf' SIZE 100M AUTOEXTEND
ON NEXT 5120K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
 LOGGING
 ONLINE
 SEGMENT SPACE MANAGEMENT AUTO;

CREATE USER OER IDENTIFIED BY welcome1
DEFAULT TABLESPACE OER_DATA
 TEMPORARY TABLESPACE TEMP
 PROFILE DEFAULT
 ACCOUNT UNLOCK;
GRANT "CONNECT" TO OER;
ALTER USER OER DEFAULT ROLE "CONNECT", "RESOURCE";
GRANT CREATE MATERIALIZED VIEW TO OER;
GRANT CREATE SEQUENCE TO OER;
GRANT CREATE SESSION TO OER;
GRANT CREATE SYNONYM TO OER;
GRANT CREATE SNAPSHOT TO OER;
GRANT CREATE TABLE TO OER;
GRANT CREATE TRIGGER TO OER;
GRANT CREATE VIEW TO OER;
GRANT UNLIMITED TABLESPACE TO OER;

Once the above sql's are executed, run the installer.
During installation process, one step is to provide the tablespace names. Use the following names
Data : OER_DATA
Blob : OER_DATA
Index : OER_INDEX
Username : OER
Password : welcome1

Hope this helps.