Scribd
Upload
293 views10 pages

Setting Up Database Based MDS Repository in Weblogic 12c

This document provides steps to set up a database-based MDS repository in WebLogic 12c including: 1. Creating an MDS schema in the database using RCU. 2. De-registering the existing file-based MDS repository and registering the new database-based repository in the WebLogic console. 3. Deploying MDS artifacts from a file-based repository to the new database-based repository by creating a deployment profile in JDeveloper.

Uploaded by

Priya Jayaraman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
293 views10 pages

Setting Up Database Based MDS Repository in Weblogic 12c

This document provides steps to set up a database-based MDS repository in WebLogic 12c including: 1. Creating an MDS schema in the database using RCU. 2. De-registering the existing file-based MDS repository and registering the new database-based repository in the WebLogic console. 3. Deploying MDS artifacts from a file-based repository to the new database-based repository by creating a deployment profile in JDeveloper.

Uploaded by

Priya Jayaraman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Setting Up Database Based MDS

Repository in Weblogic 12c

Below are the detailed step by step instructions to setup DB Based Metadata
Repository in Weblogic Server and steps to deploy the MDS Artifacts to the server

Setup DB Based Repository in Weblogic EM Console

1. Check your database if it already contains MDS schema (<prefix>_mds). If not create
new MDS schema using RCU.
2. Shutdown soa-infra via weblogic console

 Deployments -> Control Tab ->Check soa_infra -> Stop -> Force Stop

3. De-register file based MDS

 Log into em console


 Click Weblogic Domain in right hand corner -> Other Services ->
Metadata Repositories
 Select mds-soa under “File-Based Repositories” and click on De-
register
4. Register a new DB-based Repository

 First, Delete existing mds-soa datasource from WLS Console . Login


to Console-> Services -> Data Sources -> Check mds-soa -> Delete
 Then Log into em console
 Click Weblogic Domain in right hand corner -> Other Services -
>Metadata Repositories
 Click Register under 'Database-Based Repositories'
 Enter MDS Database connection information and click 'Query'
 Select Query return row 'MDS' and enter repository name as 'mds-
soa' and schema password for <prefix>_mds and then click 'Ok'

 Click 'mds-soa' repository and check 'soa-infra' partition visible


under 'Repository Partition'
 Restart AdminServer and double check 'soa-infra' application up and
running using weblogic console.

Now we are ready to create DB MDS connection in Jdeveloper


Create FileBased MDS Artifacts in local system

1. Create a folder called “seed” under the <JDev_Home>\integration\seed

2. Create custom folder called “apps” under seed to hold the artifacts that are common

Now that we have successfully referenced the SOA project to refer the file based
MDS it is barely enough only during design time. For deploy time & run time, these
artifacts must be made available in the DB based MDS.

Deploy MDS artifacts to Weblogic Server

For a simple JDeveloper based SOA deployment follow the steps below

1. Create a new application (Generic Application)


2. Name the application (eg.,ProcessMDSApp) and click 'Next'
3. Provide a name to the project (eg., ProcessMDSProj) and click 'Finish'

4. Now, right click on the ProcessMDSProj and choose 'Project Properties'. In the
'Project Properties' dialog, choose 'Deployment' and create a new deployment profile
by clicking on 'New...' button
5. In the 'Create Deployment Profile' dialog, leave the default 'Archive Type' to 'JAR
File' and name the deployment profile (eg., soamdsarchive) and click 'OK'

6. This will open up the 'Edit JAR Deployment Profile Properties' dialog. Click on the
'Contributors' section under 'File Groups -> Project Output'.
7. Click on the 'Add..' button and choose the folder where the 'content to be deployed' is
present. Here the '/apps' namespace under the file based MDS can be chosen where
the content is already placed & available
8. Now, click on the 'Filters' section and choose the artifacts under the '/apps' that you
would like to deploy or upload to MDS database repository
9. Click on OK to complete the deployment profile creation process. Now, we have
created a project JAR deployment profile which contains the artifacts to be deployed
on to the SOA MDS. Now, we will have to create a application deployment profile of
'soa bundle' type which will be deployed to the soa-infra.
10. From the 'Application Menu', choose 'Deploy' -> 'New Deployment Profile..' option
11. Under the 'New Gallery' go to 'Deployment Profiles' choose 'SOA Bundle' and click
OK

12. Under the 'Create Deployment Profile', provide a name to the application deployment
profile (eg., soabundle1) and click OK.
13. In the 'SOA Bundle Deployment Profile Properties' go to 'Dependencies' and choose
the JAR archive that we created earlier eg., soamdsarchive and click OK
14. Finally, deploy the application to the soa server.
Goto Application->Deploy-> soabundle1

This will ensure that the artifacts under the '/apps' metadata namespace is deployed
on to the SOA MDS database repository.

Create SOA-MDS Connection in Jdev and Modify adf-config.xml

In Jdeveloper , create SOA-MDS DB Connection under the 'Resource Palette' using the
MDS Credentials

This should now reflect the 'apps' folder at the same level as 'soa' metadata store.
Adf-config.xml

Make the highlighted entry in your adf-config.xml to point to the localhost mds repository.
Modify jdbc-userid and jdbc-password accordingly…

<?xml version="1.0" encoding="windows-1252" ?>


<adf-config xmlns="http://xmlns.oracle.com/adf/config"
xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
xmlns:sec="http://xmlns.oracle.com/adf/security/config">
<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
<adf-property name="adfAppUID" value="SOAApplication-2382"/>
</adf:adf-properties-child>
<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext
credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
</sec:adf-security-child>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config">
<persistence-config>
<metadata-namespaces>
<namespace path="/soa/shared" metadata-store-usage="mstore-usage_1"/>
<namespace path="/apps" metadata-store-usage="mstore-usage_2"/>
</metadata-namespaces>
<metadata-store-usages>
<metadata-store-usage id="mstore-usage_1">
<metadata-store class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
<property name="metadata-path" value="${oracle.home}/integration"/>
<property name="partition-name" value="seed"/>
</metadata-store>
</metadata-store-usage>
<metadata-store-usage id="mstore-usage_2">
<metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
<property value="DEV_MDS" name="jdbc-userid"/>
<property value="welcome1" name="jdbc-password"/>
<property value="jdbc:oracle:thin:@localhost:1521:XE"
name="jdbc-url"/>
<property value="soa-infra" name="partition-name"/>
</metadata-store>
</metadata-store-usage>
</metadata-store-usages>
</persistence-config>
</mds-config>
</adf-mds-config>
</adf-config>

This completes our configuration !!

You might also like