Monday, 4 August 2014

Oracle SOA Suite 12 C Installation - Step by Step

Hi Folks,

Finally Oracle recently made its long awaited & long-anticipated version with more productivity, performance, sophisticated & easy-to-use version.

Here you go :- 

I would like to share the installation process of most awaited  Oracle SOA suite 12 c.

I have installed this in Windows 7 machine.This time Oracle made the installation procedure pretty easy.
Make sure you have downloaded the SOA software binaries.I have mentioned below.
Make sure you have installed latest JDK and supported DB.

You will get and unzip the folder then you will get the following JAR files to install.

There are 3 steps for the entire installation

1. Weblogic n etc installtion.
2. RCU installation.
3. Extend domain.

Now follow the installation procedure.

1. Unzip the installer and start the installation procedure.
2. This will open up welcome screen of SOA 12 c installation.
 3. Click Next and Set you Oracle Home location of your drive.
4. Click Next for prerequisites.
5. Click Next. Check the installation summary and click Install.
6.Click Finish.

Done.. !! We are done with the Weblogic installtion n etc.
Now time ti install RCU.

RCU Installation

We have to install RCU schemas before domain creation.  In earlier release everything is separate installer but in SOA 12 c everything is packed into one installer.

Goto $FMW_Home/Oracle_Common/bin/rcu.bat   and run as Administrator to bring up the RCU welcome screen.
1. Click Next and choose default options to proceed.
2. Click Next and fill your DB information with credentials as you already installed the DB earlier.
3. Click Next and ignore the warning related to XE as you would be using this for DEVELOPMENT.
4. It will check some prerequisites and click OK . Enter prefix and select  SOA Infrastructure schema this will select all the dependent schemas.
5. Enter prefix and click Next.
6. Click Next and let the default values same.
7. Click Next and enter Password for all the schemas.

7. Confirm the RCU creation by clicking OK. Click Create.
8. Click Finish to compete the RCU creation.

We are done with RCU creation and go with domain creation.

Domain creation

Locate the file  $FMW_Home/Oracle_Common/common/bin/config.cmd and run as Administrator to bring up domain creation screen.

1. Give domain name and click Next. 
2. Select the FMW products which you want to install and click Next.
3. Click next and accept defaults.
4. Give credentials and click Next.
5. Choose domain mode (Dev/Prod) and accept defaults or change the JDK location.
6. Enter STB schema information and click on Get RCU Information if it is success click Next.
7. Click Next.
8. Test the connection details which are provided.
9. Click Next and verify the connection success for all the schemas. If not go back to connection details and give individual schema connection information.
10. Keep the defaults and continue by clicking Next. 
11. Click Create to start the domain creation.
12. Click Next .

13. Note down the server URLs and Finish for completion and also you can start the admin server here itself for the first time.

We are done with the installation of Prestigious Oracle SOA Suite 12 c installation . :-) 

Happy Learning...!!!!!!!!!!!! Fun Sharing.........!!!!!!!!!

Friday, 1 August 2014

Undeploy Composite Manually from Oracle SOA Suite EM

Hi Folks,

If you find any difficulty while deploying / undeploying / redeploying and your EM is not supporting to do the specific tasks you just need to undeploy the composites manually.

This is due to many reasons not only composite not deployed properly / DB reference issue/ MDS issue.

Step 1: Log on to EM right click on SOA_INFRA --> Adminstration-->MDS configuration.
Step 2: Export metada.
Step 3: file will be downloaded. Unzip the folder you will find the folder called deployed-composites and under this deployed-composites.xml.
Step 4: Open the .xml file and remove the entry of which composite / partition is having issue.

ZIP it again and import the MDS from EM.

You just need to restart the server then you can see the particular partition / composite would be undeployed.

If you still find any difficulty in deploying the same composite then you need to remove the entry in MDS as well . To delete the entry in MDS you follow my previous post. Click Here

Happy Learning...!!!!!!!!!!!! Fun Sharing.........!!!!!!!!!

Remove composite/data/files in Oracle SOA MDS - Illegal character in path at index: oramds:/deployed-composites

Hi folks,

I would like to share the strange issue that I have faced recently in our SOA environments.

Mistakenly I have placed a file in the composite folder which has gaps in the file name
eg: oracle_soa  suite.xml.
It has been built successfully and deployed in one environment and when we are trying to deploy the same code onto another Env but its throwing the below error.

Deploying on "/Farm_BPM_domain/BPM_domain/dev_soa_cluster" failed!
There was an error deploying the composite on dev_soa2: Operation failed - Member(Id=3 Timestamp=2014-08-01 03:22:25.068 Address=41.75:8038 MachineId=1177 Location=site: machine:m1-dev process:1755 Role=Weblogic):Error in getting XML input stream: oramds:/deployed-composites/Se/SeProcess_rev1.0/SCA-INF/classes/HSP-21215- Sysadmin_Instructions.docx: Illegal character in path at index 90: oramds:/deployed-composites/Se/SeProcess_rev1.0/SCA-INF/classes/Sysadmin  _Instructions.docx; . Please see the server diagnostic logs on dev_soa2 for details.

Issue:- When we were deployed the composite for the first time unexpectedly it went and sat in MDS location and then we are trying to redeploy the composite again but its throwing the exception as it is having invalid documents in MDS.

Solution:- I just removed the folder in MDS from the back-end and it worked.

MDS:  Composite instance and runtime information are stored in the SOAINFRA schema. Commonly used metadata like WSDLs, XSDs, rules, fault policies, etc. as well as composite deployments are stored within the MDS schema.

With every deployment / import of the metadata artifacts a new document version will be created in the MDS. This means that re-importing an updated WSDL-file into the MDS does not delete the previous version of the document. Furthermore we sometimes need to remove unnecessary and unwanted files from the repository. If this is not considered you might end in problems like below:

OPTION 1: Remove directories and files from MDS using WLST
1) Start WLST from SOA_HOME/common/bin/

[oracle@soabpm-vm ~]$ cd /oracle/fmwhome/Oracle_SOA1/common/bin 
[oracle@soabpm-vm bin]$ ./ 

2) Execute the following command: sca_removeSharedData('http://<soahost>:<soaport>', 'directory', 'user', 'password')

Example (delete folder 'interfaces' and all its subdirectories and files):

wls:/offline> sca_removeSharedData(‘http://localhost:8001’, ‘interfaces’, ‘weblogic’, ‘welcome1’)


Note: With the command above you can just remove directories and files which are stored under "apps".

OPTION 2: Remove directories and files from MDS using ANT

Oracle provides some ANT scripts which can be used to integrate the "remove" command into your central build & deploy proccess. Just search for the "removeSharedData" command in ant-sca-deploy.xml. On the server this file is located under SOA_HOME/bin. You can also find the file in your JDeveloper install folder under MIDDLEWARE_HOME/jdeveloper/bin.

1) Execute the command: ant -f ant-sca-deploy.xml removeSharedData -DserverURL=server.url -Drealm=realm -Duser=user -Dpassword=password -DfailOnError=true/false

Example (delete folder 'interfaces' and all its subdirectories and files):
ant -f ant-sca-deploy.xml removeSharedData -DserverURL=http://localhost:8001 -DfolderName=interfaces"

Note: With the command above you can just remove directories and files which are stored under "apps". See the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite for a detailed description of the parameters.

OPTION 3: Remove files from MDS using WLST
1) Start WLST from SOA_HOME/common/bin/


[oracle@soabpm-vm ~]$ cd /oracle/fmwhome/Oracle_SOA1/common/bin
[oracle@soabpm-vm bin]$ ./


2) Connect to the SOA server: connect('user', 'password', 't3://<soahost>:<soaport>')


wls:/offline> connect('weblogic', 'welcome1', 't3://localhost:8001') 

3) Execute the command: deleteMetadata(application=’application-name', server=’soaserver-name’, docs=’absolutePath’)

Example (delete all files in '/apps/interfaces' as well as the files in its subdirectories): 
wls:/...> deleteMetadata(application='soa-infra',server='soa_server1',docs='/apps/interfaces/**') 

Note: With the command above all files in directory 'apps/interfaces' will be deleted. Please note the double asterisk (**) at the end of the this parameter. The asterisk (*) represents all documents under the current directory. The double asterisk (**) represents all documents under the current directory and also recursively includes all documents in subdirectories. Furthermore see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for a detailed description of the valid arguments.

OPTION 4: Remove files from MDS using MBean Browser

You can call the command "deleteMetadata" also from the Enterprise Manager / MBean Browser.

1) Login to EM (http://host:port/em)
2) Expand SOA
3) Right-click on soa-infra
4) Select Administration -> MDS Configuration
5) Click Runtime MBean Browser
6) Click Operations tab
7) Click deleteMetadata operation
8) Provide parameters:
      docs - list of entries to remove (fully qualified path, eg: /apps/interfaces/**)
      restrictCustTo - default
      excludeAllCust - false
      excludeBaseDocs - false
      excludeExtendedMetadata - false
      cancelOnException - true
9) Click Invoke

For clear understanding the options of this method refer the link 

OPTION 5: Purge Metadata Version History using Fusion Middleware Control

For database-based MDS, you can purge the metadata version history using the Fusion Middleware Control (Enterprise Manager). This operation purges the version history of unlabeled documents from the application's repository partition. The tip version (the latest version) is not purged, even if it is unlabeled.

1) Login to EM (http://host:port/em)
2) Expand SOA
3) Right-click on soa-infra
4) Select Administration -> MDS Configuration
5) Scroll to the “Purge” section: enter a value in the Purge all unlabeled past versions older than field and click on the Purge button
6) In the Confirmation dialog box, click Close
How to view the MDS content

After you removed files and/or directories from the MDS you might want to have a look at the actual content. The easiest way to do this is to create a MDS connection in JDeveloper.

Happy Learning...!!!!!!!!!!!! Fun Sharing.........!!!!!!!!!