Posts Tagged 'MDS'

SOA 12c – Deploying MDS

In this post, you will learn a quick way to deploy File based MDS to database.

Assume you are using default SOA_DesignTimeRepository as shown below.


Right click SOA_DesignTimeRepository and select Transfer as shown below.


Select the Resources/Folders that you want to deploy to DB MDS.


Click + for Target Connection to bring up Create SOA-MDS Connection window. Enter Connection Name and select Connection Type, Connection and MDS partition as shown below. Typically, you would select a connection having MDS schema credentials. You can also verify the database connectivity using Test Connection.


Click OK and verify Target Connection is updated as shown below.


Click Transfer and verify that success message is shown up as below.


Click OK. In Resource Palette, verify that resources have been transferred and shown up as below.


This approach enables developer to deploy file based MDS quickly and improve the productivity and definitely one of my favorite features in 12c.

Service Bus 12c – MDS Support

In OSB 11g, sharing of resources (WSDL, XSD, XSLT etc…) typically happens using a common OSB project i.e. you create all common resources in single project and refer it from other OSB projects wherever required. In Service Bus 12c also, you would be following the same approach for sharing resources but now you can access resources from MDS. This is very much helpful when you have SOA implementation with MDS and trying to create virtualization layer on top of these services using those WSDLs.

In this post, you will learn to export your resources to MDS and refer resources (wsdl) from MDS to create Business and Proxy Services.

By default, your 12 JDeveloper has a default file based MDS repository and a MDS connection  is configured in IDE Connections to access that. The default MDS connection is called SOA_DesignTimeRepository and is shown below. You can use this connection to publish and access the resources.

Navigate to Window -> Resources -> IDE Connections -> SOA-MDS to view the configured MDS connection.


You can observe the properties on right click of SOA_DesignTimeRepository and can see actual location of MDS repository in File System. If required, you can modify this to point to some other location.


JDeveloper supports different operations like Create Folder, Export, Import and Delete of these resources from MDS. And you can also transfer MDS contents to other MDS repository. It’s highly recommended to have some standard folder structure in MDS enabling consumers to quickly locate and access the resources. We will create the following folder structure in MDS:

apps -> ServiceBus -> <<ProjectName>> -> wsdl/xsd/dvm/xslt

Right click on SOA_DesignTimeRepository, select Create Folder and give ServiceBus as folder name.


Similarly, create folders representing your project and wsdl directory as shown below.


Publishing Resources to MDS:

Right click on any resource like WSDL, XSD, XSLT, XQuery and DVM in your Service Bus project and select Service Bus -> Publish To SOA Designtime Repository as shown below.


Choose the appropriate folder as shown below. You also have the option of creating new folders in this wizard.


Click Next. Select overwrite property as per your requirements to override any existing resource with the same name. Here you can observe the resource Target URL which can be used to refer in your SOA Composites. Click Finish to complete the publish.


Note: if you are unable to view resources in MDS repository after publish, do Refresh by selecting SOA_DesignTimeRepository on right click.

Creating Business Service using WSDL from MDS:

Right click on your Service Bus project and select New –> Business Service.


Enter a meaningful name for business service and click Browse WSDLs icon.


Click SOA-MDS tab as shown below and select the WSDL.


Click OK and observer that Import Service Bus Resources wizard appears as shown below.


You can accept default location or can select different location for WSDL in your Service Bus project. Click search icon for Import Location.


Select the required folder and click Select to go back to Import Service Bus Resources wizard.


Verify the Import Location is shown as the folder you selected and click Next.


Click Next.


Click Finish and verify that binding has been selected in Create Business Service wizard as shown below.


Click Next and enter the Endpoint URI of your actual service.


Click Finish and observe that selected wsdl is imported into Service Bus project and a new business service is created.


Similarly, you can create Proxy Services using WSDL from MDS repository and refer resources like XQuery, XSLT and DVMs from SOA-MDS tab in Resource Chooser in message flow.

Observe that there is still no direct way to refer resources from MDS repository in Service Bus 12c and resources always gets imported into project as shown above.

Using Repository Creation Utility (RCU)

This post is in continuation to the previous post that talked out the OSB installation and setup of Dev environment  in Eclipse IDE. In this post, we will see the database dependency of OSB.

Much of the functionality provided with Oracle Service Bus (OSB) does not have any database dependency. Refer to the oracle blog post here that talks about the same. But there are 2 reasons why we need to look into database as well:

  • OSB Reporting functionality which is provided as one of the service monitoring features, needs database tables to store reporting data. By default, derby internal database is used for this purpose or we can configure to use any other schema during WLS domain creation.
  • And one of the major features included in OSB11g is integration with the Oracle Web Services Manager (OWSM). OWSM provides policy based security solution to secure the proxy services. These out of the box OWSM policies are provided in the metadata store (MDS) that requires a database. Refer to this link for more information on OWSM and FAQs at this link.

These required schemas can be installed into database using repository creation utility provided by oracle. Since we are using OSB11g ( download the RCU from think link. Different schemas that can be created using RCU can be found here. Since we are planning to use OWSM with our OSB installation, we will see  how to install this MDS using RCU.

If we want to use Oracle XE as a database, then we should update the database parameters once after the installation. Set the processes parameter to >=200 using the following instructions.
sqlplus sys/<your password>@XE as sysdba

SQL> show parameter session
SQL> show parameter processes
SQL> alter system reset sessions scope=spfile sid=’*’;
SQL> alter system set processes=200 scope=spfile;
SQL> shutdown immediate
SQL> startup
SQL> show parameter session
SQL> show parameter processes

Unzip the downloaded RCU zip file to any folder in the file system and call this as $RCUHOME. Run the file $RCUHOME/rcuHome/rcu.bat that brings up the below screen with options Create and Drop. We can use same utility to drop the existing schemas as well.


Click on Next to bring up the next screen and give the installed database details.


Click on Next. At this stage the database compatibility check will happen and the following error will be shown if the database is incompatible. As we can the database version should be equal to or higher than in 10g or in 11g.


If the compatibility check is successful, we will get the following screen with successful message after checking the prerequisites.


Click OK on check prerequisites and proceed to next screen where different schema components can be selected. Give the new prefix as DEV (or some other value you are comfortable with) and select metadata services if we just want OWSM. And select SOA Infrastructure component if you are planning to install SOA Suite as well. So select all these and observe the schema owner column.


Click Next and click on OK, once another prerequisites step is also over. Proceed to the next screen where we can mention the password for each schema that we want to create. Based on preference, we can give the same password to all the schemas or different password for each different schema.


Click on Next and where we can create the required tablespaces for all the schemas that we selected including default and temporary table spaces. We can click on Manage tablespaces if we want to modify any of the default properties.


Click on Next and click on OK in the popup that comes up to create all the tablesapces as mentioned in the previous step. Click on Create in this screen to create all the table spaces.


Once everything is successfully completed, we can see the following screen with completion details.


To verify the successful schema installation, we can go to sql plus screen and login with the respective schema user name and password. For example, the following screen shows the login is successful to DEV_MDS schema and also able to see all the tables.



Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 380 other subscribers

Enter your email address to follow this blog and receive notifications of new posts by email.

%d bloggers like this: