Wednesday, 29 May 2013

Oracle ODI - Unable to View Data from Models - Logical Schema not set for current context

Today I stumbled to view data from a ODI Model.

The Problem Statement:

I had created a Model from simple Employee schema with a context name called Development. FYI: I used Oracle Technology.

After performing ODI reverse engineering, I wanted to view the data from one of the tables within the model that I created. You can view the data from the model by 

Right click the Table under the Model --> View Data

On performing the above steps you will get this Error:

"Logical Schema not set for current context"


"ODI-17523: There is no connection for this logical schema / context pair: lg1 / GLOBAL."

The Solution:

After doing a bit of reading found that this was a know Design issue.

Document Reference: 
Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86-64
Part Number E14770-44

<Document Snippet>

40.2.1 For File Datastores, the View Data operation always looks for global context

Within ODI Studio, when viewing data from within a data store, there must be a global context defined for the datastore.
com.sunopsis.core.SnpsInexistantSchemaException: ODI-17523: There is no connection for this logical schema / context pair: lg1 / GLOBAL.
As a workaround, define a global context for the datastore.

<Document Snippet>

After reading the above, it clearly makes sense why I was getting the error. The view Data command always referred to the "Global" context which I had not set to any thing.

Please perform the following steps to rectify the problem:

1. Go to the Topology Tab in ODI studio.
2. Select the Logical Schema to which the Model is associated to.
3. Under the Definition tab of the Logical Schema assign the same physical schema, as same as the development context (In my case I used Development Context during Reverse engineering of the Model), to the Global Context.
4. Save all.
5. Now try viewing the data and this will work.

Hope it helped you. Happy Code -ing .... :)

Thursday, 9 May 2013

How To secure your OSB services (Propagate SAML Token)

To day I would like to share my knowledge, Reading and Finding about

How To Secure a OSB service using SAML Token or What are the Steps to Secure a OSB service using a SAML Token (Also the below steps can be used for SAML token Propagation) :

Now in order to find how to secure OSB  there is a sites / videos that can help us:

  • Watch this video for easy understand of how to secure OSB service. This an oracle produced Video. The link provided here is only part 1 out of 3 Parts. As always, youtube provides the links to the relevant videos once you watch the first part. 
  • The same can be found in this slide pack.

Before reading this blog further please view / review the above reference artefacts so that you have the basic Knowledge / context.

In order to achieve our goal there are few bits missing in the above referenced artefacts.

In order to secure a OSB service, you will need two product / parts:

1. OWSM  policies. -- this is clearly articulated in the referenced artefacts above.
2. Configuration of the Weblogic Server (For the identity Provider) - This is missed out in the above reference artefact.

Note: This blog is not to pinpoint any documentation defects in the reference artefacts, please consider this blog as an additional reference material.

In order to configure the security provider or authentication provider in weblogic server, please follow this documentation:

Document: Oracle® Fusion Middleware Securing Oracle WebLogic Server 11g Release 1 (10.3.6)
Section Relevant to us would be: Configuring LDAP Authentication Providers

And one last thing that would vary for us from the reference artefacts is that the following OWSM policies need to be used instead of the policies stated in the above referenced artefacts:

oracle/wss10_saml_token_service_policy – Proxy Service
oracle/wss10_saml_token_client_policy – Business Service.

Hope all the above references were of help. Please feel free to leave you comments.