Showing posts with label MDS. Show all posts
Showing posts with label MDS. Show all posts

Monday, April 14, 2014

Backing up the MDS Repository Artifacts - Oracle SOA Suite 11g

Backing up the MDS Repository Artifacts - Oracle SOA Suite

In Oracle SOA Suite 11g and Oracle SOA Suite 12c , all the common artifacts , the deployed composites and the common configurations are stored in the MDS database schema. Sometimes there is a possibility of MDS schema getting corrupted (the best example is the composites getting corrupted frequently)those scenario we will not be able to bring up the soa-infra and also we may loose all the deployments.

Backing up the MDS artifacts is the the solution for these kind of issues.

In this post i will be explaining some of the different options to back up the MDS artifacts.

The best approach is do a full back up of MDS repository schema using database backup utilities(dbexp).The backup can be restored if there is any issue with the MDS schema.

EM console - MDS configuration Page :

Right click on soa-infra and click on Administration and MDS Configuration.
Click Export on MDS Configuration page.


This will export the MDS artifacts to local machine as zip file.


Wednesday, March 26, 2014

Recovering the composites to JDeveloper from MDS - Oracle SOA Suite

Recovering the composites to JDeveloper from MDS - Oracle SOA Suite

Sometimes there is a possibility the latest code changes of the deployed composite in JDeveloper might have lost in other hand some cases we will not be having the implementation code for the deployed composites.

These scenarios the Oracle SOA Suite composite artifacts can be exported from MDS through em console and the same can be converted to design time artifact in JDeveloper.

This post will explain the steps to recover the composite to JDeveloper from MDS.

Steps to recover the composite from MDS

Login to Em console, right click on the particular composite and click on Export


Select the appropriate options as shown and click on Export

Sunday, November 13, 2011

Oracle SOA Suite 11g - Purging Metadata Version History for SOA-INFRA


Oracle SOA Suite 11g - Purging Metadata Version History for SOA-INFRA:

For database-based MDS repositories, you can purge the metadata version history from a partition. (File-based MDS repositories do not maintain version history.) This operation purges 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.

To purge labeled documents, you must first delete the label.

Consider purging metadata version history on a regular basis as part of MDS Repository maintenance, when you suspect that the database is running out of space or performance is becoming slower. This operation may be performance intensive, so plan to do it in a maintenance window or when the system is not busy.
To use WLST to purge metadata version history, use the purgeMetadata command. You specify the documents to be purged by using the older than parameter, specifying the number of seconds.

The following example purges all documents older than 100 seconds:


wls:/offline> connect ()
Please enter your username: weblogic
Please enter your password:
Please enter your server URL [t3://localhost:7001] :t3://soahost:soaport
Connecting to t3://nft-soa-vip1:8004 with userid weblogic...
Successfully connected to managed Server 'SOA1' that belongs to domain 'SOACoreDomain'.
wls:/SOACoreDomain/serverConfig> purgeMetadata(application='soa-infra', server='SOA1', olderThan=100)
Executing operation: purgeMetadata.
Metadata purged:Total number of versions: 3925.
Number of versions purged: 0.

wls:/SOACoreDomain/serverConfig>

To use Fusion Middleware Control to purge the metadata version history:

  1. From the navigation pane, expand the farm, expand SOA and then right click on soa-infra.
  2. From the menu, choose Administration then choose MDS Configuration.


Oracle SOA Suite 11g - Metadata Labels in the MDS Repository


Oracle SOA Suite 11g - Metadata Labels in the MDS Repository:

A metadata label is a means of selecting a particular version of each object from a metadata repository partition. Document versions belonging to a label are not deleted by automatic purging, unless the label is explicitly deleted. In this way, creating a label guarantees that a view of the metadata as it was at the time the label was created remains available until the label is deleted.

You can use a label to view the metadata as it was at the point in time when the label was created. You can use the commands to support logical backup and recovery of an application's metadata contained in the partition.

Labels are supported only in database-based repositories.

The following topics describe how to manage labels:


· Creating Metadata Labels
· Deleting Metadata Labels
· Listing Metadata Labels
· Promoting Metadata Labels

  1. Creating Metadata Labels


To create a label for a particular version of objects in a partition in an MDS Repository, you use the WLST command createMetadataLabel. For example, to create a label named prod1 for the application soa-infra, use the following command:

wls:/offline> connect ()
Please enter your username: weblogic
Please enter your password:
Please enter your server URL [t3://localhost:7001] :t3://soahost:soaport
Connecting to t3://nft-soa-vip1:8004 with userid weblogic...
Successfully connected to managed Server 'SOA1' that belongs to domain 'SOACoreDomain'.
wls:/SOACoreDomain/serverConfig> createMetadataLabel (application='soa-infra', server='SOA1', name='prod1')
Executing operation: createMetadataLabel.
Created metadata label "prod1".
wls:/SOACoreDomain/serverConfig>
If the application has more than one version, you must use the applicationVersion parameter to specify the version.

  1. Deleting Metadata Labels

To delete a metadata label, you use the WLST command deleteMetadataLabel. For example, to delete a label named prod1 for the application soa-infra use the following command:
deleteMetadataLabel (application='soa-infra', server='SOA1', name='prod1')
If the application has more than one version, you must use the applicationVersion parameter to specify the version.

  1. Listing Metadata Labels

You can list the metadata labels for a particular application. To do so, use the WLST command listMetadataLabel. For example, to list the labels for the application soa-infra, use the following command:
listMetadataLabels(application='soa-infra', server='SOA1')
If the application has more than one version, you must use the applicationVersion parameter to specify the version.

  1. Promoting Metadata Labels

You can promote documents associated with a metadata label so that they are now the last version. That is, you can promote them to the tip. Promote a label if you want to roll back to an earlier version of all of the documents captured by the label.
To promote a label to the tip, use the WLST command promoteMetadataLabel. For example to promote the label prod1, use the following command:
promoteMetadataLabel(application='soa-infra', server='SOA1', name='prod1')
If the application has more than one version, you must use the applicationVersion parameter to specify the version.