Oracle MCS: Storing values in Application Policies by Rubén Rodríguez Santiago


Oracle MCS offers different levels of lifecycle management and in this post I am going to focus on the lifecycle management (versioning) of the different artifacts such as Mobile Backends, Custom APIs and their implementations, etc. These artifacts can have two different states: draft and published. When you publish an API it is frozen becasuse it is not safe to modify it, if you modify it you can cause problems in the different components that are using it.
This is why versioning is one of the key points that you have to keep in mind when developing APIs.
In this example we are going to suppose that we have a mobile app that consumes Twitter API from Oracle MCS. As you might know, in order to consume twitter API you need tokens that you can get when you create your application in Twitter Platform.
One option we have is to have, for example, a JSON file, or even a json with the different values inside our API implementation file. Read the complete article here.


WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.