Powered By Blogger

Wednesday, May 16, 2012

Team Climate Survey




Take the following team climate survey, to see where your process simplification team stands firm as a group.

Purpose

Do members share a sense of why the team exists and are invested in accomplishing the mission?
In a successful team: Members proudly share a sense of why the team exists and are invested in accomplishing its mission and goals.

Priorities

Do members know what needs to be done next, by whom, and by when to achieve team goals?
In a successful team: Members know what needs to be done next, by whom, and by when to achieve team goals.

Roles

Do members know their roles in getting tasks done and when to allow a more skillful member to do a contain task?
Members know their roles in getting tasks done and when to allow more skillful members to do a certain task.

Decisions

Are authority and decision-making lines clearly understood?
In a successful team: Authority and decision-making lines are clearly understood.

Conflict

Is conflict dealt with openly and considered important to decision-making and personal growth?
In a successful team: Conflict is dealt with openly and is considered important to decision-making and personal growth.

Personal Traits

Do members feel their unique personalities are appreciated and well utilized?
In a successful team: Members feel their unique personalities are appreciated and well utilized.

Norms

Are group norms set for working together and are they seen as standards for everyone in the group?
In a successful team: Group norms for working together are set and seen as standards for every one in the groups.

Effectiveness

Do members find team meetings efficient and productive and look forward to this time together?
In a successful team: Members find team meetings efficient and productive and look forward to this time together.

Success

Do members clearly know when the team has met with success and share in this equally and proudly?
In a successful team: Members know clearly when the team has met with success and share in this equally and proudly.

Training

Are opportunities for feedback and updating skills provided and taken advantage of by team members?
In a successful team: Opportunities for feedback and updating skills are provided and taken advantage of by team members.



The five dysfunctions of the Team are

1)Inattention to RESULTS
2)Avoidance of Accountability
3)Lack of Commitment
4)Fear of Conflict
5)Absence of Trust

Tuckmans Team Development Model


Dr Bruce Tuckman published his Forming Storming Norming Performing model in 1965. He added a fifth stage, Adjourning, in the 1970s. The Forming Storming Norming Performing theory is an elegant and helpful explanation of team development and behaviour

Tuckman's model explains that as the team develops maturity and ability, relationships establish, and the leader changes leadership style. Beginning with a directing style, moving through coaching, then participating, finishing delegating and almost detached. At this point the team may produce a successor leader and the previous leader can move on to develop a new team.

tuckman's forming storming norming performing four-stage model

The progression is:
  1. forming
  2. storming
  3. norming
  4. performing
Here are the features of each phase:

forming - stage 1

High dependence on leader for guidance and direction. Little agreement on team aims other than received from leader. Individual roles and responsibilities are unclear. Leader must be prepared to answer lots of questions about the team's purpose, objectives and external relationships. Processes are often ignored. Members test tolerance of system and leader. Leader directs (similar to Situational Leadership® 'Telling' mode).

storming - stage 2

Decisions don't come easily within group. Team members vie for position as they attempt to establish themselves in relation to other team members and the leader, who might receive challenges from team members. Clarity of purpose increases but plenty of uncertainties persist. Cliques and factions form and there may be power struggles. The team needs to be focused on its goals to avoid becoming distracted by relationships and emotional issues. Compromises may be required to enable progress. Leader coaches (similar to Situational Leadership® 'Selling' mode).

norming - stage 3

Agreement and consensus is largely forms among team, who respond well to facilitation by leader. Roles and responsibilities are clear and accepted. Big decisions are made by group agreement. Smaller decisions may be delegated to individuals or small teams within group. Commitment and unity is strong. The team may engage in fun and social activities. The team discusses and develops its processes and working style. There is general respect for the leader and some of leadership is more shared by the team. Leader facilitates and enables (similar to the Situational Leadership® 'Participating' mode).

performing - stage 4

The team is more strategically aware; the team knows clearly why it is doing what it is doing. The team has a shared vision and is able to stand on its own feet with no interference or participation from the leader. There is a focus on over-achieving goals, and the team makes most of the decisions against criteria agreed with the leader. The team has a high degree of autonomy. Disagreements occur but now they are resolved within the team positively and necessary changes to processes and structure are made by the team. The team is able to work towards achieving the goal, and also to attend to relationship, style and process issues along the way. team members look after each other. The team requires delegated tasks and projects from the leader. The team does not need to be instructed or assisted. Team members might ask for assistance from the leader with personal and interpersonal development. Leader delegates and oversees (similar to the Situational Leadership® 'Delegating' mode).

tuckman's forming storming norming performing model

tuckman forming storming performing norming




Better quality diagrams are available as separate files:
Tuckman 'forming storming' diagram (doc format)
Tuckman 'forming storming' diagram (pdf format)
(Thanks S Doran for suggestion. And thanks also C Lloyd for pointing out the error in these diagrams, duly corrected Aug 2008 - storming and norming were inverted.)

Tuckman's fifth stage - Adjourning

Bruce Tuckman refined his theory around 1975 and added a fifth stage to the Forming Storming Norming Performing model - he called it Adjourning, which is also referred to as Deforming and Mourning. Adjourning is arguably more of an adjunct to the original four stage model rather than an extension - it views the group from a perspective beyond the purpose of the first four stages. The Adjourning phase is certainly very relevant to the people in the group and their well-being, but not to the main task of managing and developing a team, which is clearly central to the original four stages.

adjourning - stage 5

Tuckman's fifth stage, Adjourning, is the break-up of the group, hopefully when the task is completed successfully, its purpose fulfilled; everyone can move on to new things, feeling good about what's been achieved. From an organizational perspective, recognition of and sensitivity to people's vulnerabilities in Tuckman's fifth stage is helpful, particularly if members of the group have been closely bonded and feel a sense of insecurity or threat from this change. Feelings of insecurity would be natural for people with high 'steadiness' attributes (as regards the 'four temperaments' or DISC model) and with strong routine and empathy style (as regards the Benziger thinking styles model, right and left basal brain dominance).

Friday, May 11, 2012

Different console links in ORACLE SOA world

1)weblogic console
http://host:port/console
example: http://localhost:7001/console

2)Oracle Enterprise Manager console
http://host:port/em
example: http://localhost:7001/em

3) Oracle Service Bus console
http://host:port/sbconsole
example: http://localhost:7001/sbconsole

4)Oracle BPM Worklist Application
http://host_name:port/integration/worklistapp/
where host_name is the name of the host on which the Worklist
application is installed and port is the port number of the SOA-managed server
(the default is 8001).

5) Oracle BPM Workspace web application
http://host_name:port/bpm/workspace/
default port is :8001

Note:Notice that a Oracle BPM Workspace application looks very similar
to a Oracle BPM Worklist, which we are already familiar with.
However, BPM Workspace provides some additional functionality,
like monitoring process performance using the Dashboard.

6)Oracle Service Registry
http://host_name:port/application_name/uddi/web, where
host_name is the name of the host on which OSR is installed, application_name is
name of the application (default name is registry), and port is a number that is set
during the installation process.

Note: Oracle Service Registry (OSR) is a fully V3-compliant implementation of UDDI
(Universal Description, Discovery and Integration), and one of the key components
of Oracle SOA Suite 11g. It allows us to publish and discover services and service
providers, and manage metadata about services (security, transport, or quality
service) using taxonomies. Therefore, it plays an important role when trying to
improve visibility and promote service reuse. It is also important in the scope of SOA
governance.

7)Business Activity Monitoring(BAM)
http://localhost:9001/OracleBAM 

8)Oracle SOA Composer
http://localhost:port/soa/composer
 
The SOA Composer enables you to work with deployed DVMs.  
 
9)WSIL Connection
This is created in Jdeveloper
New Gallery -> All Technologies ->Connections ->WSIL Connection ->
Select Resource pallet and give the WSIL file
 
http://localhost:8001/inspection.wsil 



Wednesday, May 2, 2012

Understanding WSDL Faults

Understanding WSDL Faults

Consider the WSDL with  portType and operations as shown below

< portType name="Sample" >
    < operation name="sayHello" >
      < input message="tns:sayHello"/ >
      < output message="tns:sayHelloResponse"/ >
    < /operation >
    < operation name="addNum" >
      < input message="tns:addNum"/ >
      < output message="tns:addNumResponse"/ >
    < /operation >
    < operation name="subNum" >
      < input message="tns:subNum"/ >
      < output message="tns:subNumResponse"/ >
    < /operation >
  < /portType >
     
   

 


" In the above example each operation has input and output message. For each operation we can add the fault message it returns. The message definition is shown below

 
< message name="SayHelloFaultMessage" >
 < part name="error" type="xs:string" / >
 < /message >

 < message name="AddNumFaultMessage" >
 < part name="error" type="xs:string" / >
 < /message >

 < message name="SubNumFaultMessage" >
 < part name="error" type="xs:string" / >
 < /message >
     

     
After adding the fault the porType is shown below
   
  < portType name="Sample" >
    < operation name="sayHello" >
      < input message="tns:sayHello"/ >
      < output message="tns:sayHelloResponse"/ >
    < fault name="fault" message="tns:SayHelloFaultMessage" / >

    < /operation >
    < operation name="addNum" >
      < input message="tns:addNum"/ >
      < output message="tns:addNumResponse"/ >
    < fault name="fault" message="tns:AddNumFaultMessage" / >

    < /operation >
    < operation name="subNum" >
      < input message="tns:subNum"/ >
      < output message="tns:subNumResponse"/ >
    < fault name="fault" message="tns:SubNumFaultMessage" / >

    < /operation >
  < /portType >


Note the following while adding fault:
WSDL does not require that we use unique fault names within the namespace used
to define the operation. In other words, that faults that have the same name and are
defined within the same namespace will be considered as the same fault in BPEL.
Keep this in mind when designing services that can potentially become partners
of BPEL business processes, because this can lead to conflicts in fault handling
during execution.

In the above we have given unique name so that all the faults are considered as different

Sunday, April 22, 2012

This project is not associated with an Oracle Service Bus Configuration

When does this happen?
Often you may have to copy code from one place to another. Let us say you have code inside the folder “abc” . Folder abc contains, OSB configuration project, OSB project and some webservices.
Now you move this code from “abc” folder to some other folder say “testing” folder.
Let us say you open the oepe and start importing the moved code/ project. Select FileImport->General->exsiting project from workspace Select root directory. It shows all the  projects in that directory including configuration project. Select all  and click on finish.


Running the configuration(Right click on Configuration and select “run” as and run )
Now if you run the congiguration you may get the above error as “This project is not associated with an Oracle Service Bus Configuration” .

You need to follow these steps
1)Click “Project” and select Clean
2)Drag  the OSB Project into to OSB Configuration project.
Now the issue should be resolved.

Friday, April 20, 2012

OSB 11.1.1.6 Demo Sample developed from scratch

Proof of Concept: OSB Demonstration
This demonstrates the basic OSB sample. You should have already installed OSB and weblogic on your system.

Refer my previous post for installing OSB and weblogic
http://aleemkhan09.blogspot.in/2012/04/installing-osb-11116-with-osb-ide-on.html

For complete document with screen shot you can refer google doc
https://docs.google.com/open?id=0B2u9s7xy74d9WVVjSVdVd1RKM3M


For OSB demo we require the following :
1. Webservice (with WSDL,XSD)
2. Business Service which is developed using above webservice
3. Proxy Service which invokes the above Business service
Let us first construct the WebService
Step A : Construction of Webservice
1)Double click on OEPE which is installed in FMW_HOME/OEPE folder. Choose File->New->Web Service Project as shown below





2)Give the project name as Sample_WS where WS stands for WebService project. If Target run time is not defined then create the new one buy clicking on new runtime and select the version. Here 10.3.6 is selected as weblogic version is 10.3.6


3)Click the Finish button and the Target runtime is visible as shown below

4)Click on Next and follow as shown below

5)change the context root to business/sample
5)
6)Click on Yes” for the below dialogue. Let it be Java EE perspective
7)The webservice Project is created as shown below

8)Right click on src folder and create the package com.osb.sample as shown below


9)Now right click on the package and select weblogic web service and give the name as Sample

10)The following code Sample.java is generated as shown below where you can put your own logic.
Here we have added three methods.
String sayHello(String s)
Int addNum(int a, int b)
Int subNum(int a, int b)

The class is as shown below

import javax.jws.*;

@WebService
public class Sample {

@WebMethod
public String sayHello(String s) {
return "Hello"+s;
}

@WebMethod
public int addNum(int a,int b) {
return a+b;
}

@WebMethod
public int subNum(int a , int b) {
return a+b;
}
}





Step B Configuring the Server and running the webservice
1)Add the server if not added as shown below
Click File->New->other->Server








2)You should be able to see the message as shown above. “Started”
3)Now we need to run the webservice. Right click on the Sample_WS project and click run and select the server added.


4)Access the WSDL through URL
http://localhost:7001/business/sample/SampleService?WSDL





Step C: Create OSB configuration project
Now webservice Is ready. From now onwards the real OSB work starts
we need to create OSB configuration project. .It represents the configuration information associated with an OSB domain (a group of servers, all similarly configured and providing identical functionality).
1)FileNewotherOracle service bus Configuration Project

2)You can keep the default name or if you want can give some meaningful name


Now the configuration is ready hence we need to proceed further to create OSB Project

Step D: Creating Sample OSB project
1)file->Oracle service Bus Project

2)Ensure that OSB Configuration 1 is selected which was created earlier. Give the name which has suffix as _SB just to denote it is Service Bus project as shown below

3)The Sample_SB(Sample Service Bus) project is created as shown below


Step E : Developing Business Service
The next step is to develop business Service which is called by Proxy service
To develop business service we require WSDL of the service which was created earlier.
1)To generate the WSDL , go to the Sample_WS project, under src go to Sample.java , right click and select weblogic webservices and select Generate WSDL as shown below


2)Service is created in the same package as shown below


3)Copy the SampleService.wsdl and the xsd into the Sample_SB project


4)Notice the following in WSDL






Replace the location


With
http://localhost:7001/business/sample/SampleService?WSDL

It should look as shown below







5)Now we can develop business service as shown below as we have WSDL file for the same. Right-click the Sample_SB project in the Project Explorer window and select New -> Business Service from the pop-up menu



6)make sure that the Sample_SB project is selected, and then set the file name field to SampleBiz where Biz stands for Business


7)Busniess service is created as shown below
8)The General Configuration settings needs to be done as shown below


9)Select the WSDL and port (SamplePort) as shown below




10)Select Yes when we get the following dialog


Note:If you select NO then under transport tab you get the error

Step F: Creating the proxy service

Once the Business Service is ready next is to create Proxy Service.The easiest way to create proxy service is to “Right click “ on SampleBiz, select the Oracle Service Bus and select generate proxy which will automatically create the proxy service.
The other way of doing is given below but you need to add more steps
1)Right click project explorer->Proxy Service



2)Select Sample_SB to get rid of the above error. Give the name of proxy as “sample”



3)Do the General configuration as shown below


4)Do the transport configuration as shown below
Change the end point to /osb/Sample


5)Click on the Message flow tab as shown below


6)Add the routing so that it gets routed to SampleBiz. Drag Route from Nodes from RHS.

7)Click on Routing from route Actions. After adding Routing it looks as shown below


8)Click on Routing on LHS and browse the Service and point to SampleBiz as shown below

Step G: Deploy project
1)Go the server tabs, right click on the server tab, click “Add and Remove”



2)Add OSB_Configuration , Sample_ws, Sample_SB to the server
Note: The Sample_SB project is part of the OSB_Configuration, so you do not need to add it explicitly. Just click the Finish button, and OEPE will deploy the projects.



3)After clicking finish the services would be deployed

4)Verify the service
Login to localhost:7001/sbconsole weblogic/welcome1 , notice the proxy service , business service are deployed



5)When you try to launch test console to test the proxy service through “Actions” as shown in above figure, you may get error as "Test Console" service is not running. Contact administrator to start this service.

Note: Test console will work only when OSB server is up and running (Along with admin server); and all deployments on OSB server are in active state. Make sure to check this by logging to em. If osb server is not up then start the server

6)Now start the OSB_server
startManageWeblogic.cmd osb_server1 from the location
E:\ oracle\fmw11116\user_projects\domains\osb_domain\bin
Check through EM if it has been started
7)testing the proxy service
Now launch the TestConsole as described previously and give the input . Select the addNum operation from the available operations. Given the input as 3,3 and you should get the ouput as 6.



8)Analyzing more details
If you scroll down in the same test console , you could see the invocation trace. Notice thei incoming request, also notice it is getting routed to sample business service called samplebiz.

Tuesday, April 17, 2012

Installing OSB 11.1.1.6 with OSB IDE on windows 7 64 bit

Installing OSB on windows 7 64 bit:
It is not very straight forward to install OSB server, OSB IDE ,weblogic on windows 7 64 bit. For 32 bit we get OEPE with weblogic which is quite easy to install, but on 64 bit you don't have OEPE with weblogic. You need to install weblogic separately then install OEPE . Here selecting the OEPE version is tricky. If weblogic version is 11.1.1.6 , it does not mean you have to select OEPE version of 11.1.1.6. It will not work. Infact the correct version of OEPE is 11.1.1.8. Now what about OSB? which version should be selected? OSB should be of version 11.1.1.6 . So in summary
weblogic: 11.1.1.6
OEPE: 11.1.1.8
OSB 11.1.1.6

Important points

1)Weblogic and OSB versions should be same if you want OSB IDE to be installed.
So weblogic is 11.1.1.4 , then OSB should be 11.1.1.4.
Incase if they don’t match then while installing OSB (from osb_generic_11.1.1.4) you may get error as “weblogic is not suited for this version of IDE” at step 4 (Typical/Custom step)

2)OEPE should be compatible with the OSB version.

Here are the list of compatible OEPE with OSB . There is no document for this though
OSB Weblogic Server OEPE
11.1.1.6.0 10.3.6 11.1.1.8.0
11.1.1.5.0 10.3.5 11.1.1.7.2
11.1.1.4.0 10.3.4 11.1.1.6.1
11.1.1.3.0 10.3.3 11.1.1.5


STEP1: Install JDK
Install JDK (Jrockit can be preferred)
jrockit-jdk1.6.0_26-R28.1.4-4.0.1-windows-x64(1) should be installed .Always prefer Jrockit over JDK as Jrocking has very good performance

STEP2: Install Weblogic

1. Open a terminal and go to the folder where wls1036_generic file is.
2. Execute the following command:
Double click on the file
3. When the oracle weblogic installer starts, click next and enter the folder you want to use as Middleware Home Directory, for example:
E:\InstalledSoftwares\oracle\fmw11116
4. Choose the typical installation (or customise if you need). Better to select customize as you can install examples also
5. On the JDK installer screen, the installer should automatically recognise the JDK installed during step 1. If not, click on “Browse” button and point to JDK directory (e.g. /jrocking).
6. Finish the installation.

STEP 3 – Install Oracle Enterprise Pack for Eclipse
Download from
http://www.oracle.com/technetwork/developer-tools/eclipse/downloads/index.html
Just extract the oepe-indigo-all-in-one-11.1.1.8.0.201110211138-win32-x86_64
content into a folder named “oepe” in you middleware home directory, for example:
E:\InstalledSoftwares\oracle\fmw11116\oepe-indigo11.1.1.8.0_64

STEP 4 – Install OSB

Download from :http://www.oracle.com/technetwork/middleware/service-bus/downloads/index.html
1. Extract the downloaded zip file (ofm_osb_generic_11.1.1.6.0_disk1_1of1) into a any folder. Go to that “Disk 1” directory under the extracted folder and run the following command:
E:\softwares\OSB\ofm_osb_generic_11.1.1.6.0_disk1_1of1\Disk1>setup -jreLoc E:\InstalledSoftwares\jrockit
2. we have provided the JDK location in the above command
3. During the rest of the installation used the settings below
Installation location:
Oracle Middleware Home :E:\InstalledSoftwares\oracle\fmw11116\
Oracle Home Directory: Oracle_OSB1
Installation Type: Custom (ensure that ORACLE BUS IDE is selected).
Note the following in “Typical”. If the version is not matched it would say weblogic version is not compatible with OSB IDE. Then in “CUSTOM” you won’t be able to select the ORACLE BUS IDE. This means that weblogic which is selected is of different version say 11.1.1.4 and OSB_GENERIC is of different version say 11.1.1.6
Prerequisite Checks – This stage passes
Product Home Location:
Weblogic Server Location: / E:\InstalledSoftwares\oracle\fmw11116\wlserver_10.3
OEPE Location E:\InstalledSoftwares\oracle\fmw11116\oepe-indigo11.1.1.8.0_64

Note the following: The OEPE location is automatically taken. Suppose if OEPE version is not compatible with OSB , then OEPE will not get recognized. You will get message as “OEPE” location is invalid even if you manually select the OEPE. So in this example OEPE should be 11.1.1.8 and OSB should be 11.1.1.6

Step5: Verify the OSB IDE
Check if OSB IDE has been installed or not
Open the eclipse ide from the below location
E:\InstalledSoftwares\oracle\fmw11116\oepe-indigo11.1.1.8.0_64
Set the workspace to any folder
Check the following
Window->open perspective->other->Oracle Service bus
You should be able to see the Oracle Service bus

Step6)Configuring the OSB SERVER or creating the domain
a) Go to E:\InstalledSoftwares\oracle\fmw11116\Oracle_OSB1\common\bin
b) Config.cmd
c) Select new domain creation.
d) Select the configuration as shown below so that we get OWSM,EM etc
e) give the domain name as osb_domain
f) Give username as weblogic/welcome1
g) Select development mode
h) Give the databse details for OWSM MDS schema(ignore the failure test) and OSB JMS reporting provider
i) Proceed to next step(by pass the DB connection if it asks),


Step 7)Access the sbconsole
Go to the following location:
E:\InstalledSoftwares\oracle\fmw11116\user_projects\domains\osb_domain
And type the following
startWeblogic.cmd
Now access the sbconsole
http//localhost:7001/sbconsole
enter weblogic/welcome1
you should be able the see the screen