Sunday, 16 June 2013

How to Create XSD and WSDL from Scratch using Jdeveloper.

I wanted to find out if there was already documentation on "How to Create XSD and WSDL from Scratch using Jdeveloper".

And guess what, found one at FUSION Blog : Creating a WSDL File From XSD File

Great Article and the author has illustrated the steps clearly and Thoroughly.

Thanks to the Author.

Happy Coding. :)

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.

Tuesday, 30 April 2013

Software Testing Life Cycle - STLC and Different Types of Software Testing

In this blog I would like to cover the different phases of a Testing within SDLC (Software Development Life Cycle)

We are all mostly aware of the SDLC. Within this SDLC Testing is one phase and Testing by itself has its own cycle. I have tried to portray the software Testing Life Cycle (STLC) below:

Software Testing Life Cycle - STLC

-->1. Requirements Analysis
---->2. Test Planning
------>3. Test Case Development
-------->4. Environment Steps
---------->5. Environment Set-up
------------>6. Test Execution
------------->7. Defect Tracking and Bug Fixing
--------------->8. Review and Audit
----------------->9. Acceptance and Baseline
------------------->10. Test Case Closure / Loop back to step 1.                                              

Now within these STLC, Many types of testing can be performed. Below are the different types of testing that I have tried to find for my self.                                              
Source for this below section is: Soft Ware Testing Help                                               
Software Testing Types:

Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.

White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.

Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.

Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Sanity testing - Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.

Regression testing – Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.

Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.

Load testing – Its a performance testing to check system behaviour under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.

Stress testing – System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.

Performance testing – Term often used interchangeably with ‘stress’ and ‘load’ testing. To check whether system meets performance requirements. Used different performance and load tools to do this.                                          
You can also find more information in --> Software_testing                                               
                                                Happy Testing.... ;)