SOA Suite 12c: Deploying shared artifacts to Run Time MDS – the official approach and the quick short-cut
Reageer
Tagarchief: mds
SOA Suite 12c: Inspect and Leverage the contents of the Run Time MDS in the Integrated WLS
SOA Suite 12c provides the option to use the Integrated WebLogicServer in JDeveloper as the development run time environment. It comes prepackaged, installs very easily and gets a developer up and running in less than 20-30 minutes. As part of this light(er) weight SOA Suite run time, there is an MDS Repository (file based). Deployment to this run time MDS is done in the usual way. The contents of this MDS instance can be inspected in JDeveloper and resources can be transferred to the local design time MDS instance or exported to a JAR file for further distribution. All you have to do is create a connection to this run time MDS instance.
SOA Suite 12c: Using Domain Value Map (DVM) in Service Bus projects
Domain Value Maps are still DVMs in SOA Suite 12c. Create them in JDeveloper, use them in Transformations and Assignments in Mediator and BPEL. Inspect them and edit them at run time using SOA Composer. Nothing really new there.
What is new:
- In 12c, we can use XQuery in BPEL and Mediator – and in these XQuery functions we can use Domain Value Map as well.
- In 12c, we can use both XQuery and XSL Map in Service Bus – and here we can use Domain Value Maps as well
- In 12c, we can inspect and edit Domain Value Maps also at runtime in the Service Bus Design Composer/Console
- In 12c, we can create Domain Value Maps in Service Bus projects, publish them to the MDS Design Time Repository as well as import them into Service Bus projects from that repository
So as of now, in SOA Suite 12c we can leverage Domain Value Map from Service Bus components.
SOA Suite 12c: Sharing resources between development environments: Export from and Import to Design Time SOA MDS repository
The MDS repository is an important mechanism for SOA Suite 12c, both at design time during development as well as at run time. At design time, MDS is used to host shared resources such as WSDL and XSD documents that are referenced in many different places. Instead of copying these resources between applications and projects, or creating central shared folders that are managed manually and at file system level, MDS is concept that is native to JDeveloper and therefore much easier to use with these shared resources.
In SOA Suite 12c, a design time, file based MDS repository is part of the development environment – out of the box. You can create your own file based MDS repositories in addition to this out-of-the-box instance.
When you open the Resource window, under IDE Connections | SOA-MDS, you will find the connection to this local, file based repository – that is initially empty.
Resources can be added to the MDS, for example by transferring them from SOA composite or Service Bus projects. Resources can also be transferred from the MDS to Service Bus projects. I am not sure yet how to transfer resources from MDS to a SOA composite application.
However, as stated before, this out of the box file based design time MDS repository is local. Resources added to it, are not shared with MDS repositories in some other location. SOA composites that contain references that start with oramds: cannot be shared unless the sharing partners all have the referenced resources in their local MDS repositories. That’s why it is very convenient to be able to export selected resources from a design time file based MDS environment – to a jar-file – and import resources from this jar-file to MDS repositories in other environments. I just used this mechanism to bring resources across from one VM to another.
