Monthly Archives: July 2008

Oracle Fusion : Getting Started on Oracle Fusion : TUTORIAL

Posted on by
2

Oracle Fusion is a Suite of Products being provided as a END-END to solution by Oracle.

Following are the Productions within the FUSION suite you should be familiar with to call yourself a MASTER of Oracle Fusion
  1. Oracle Access Manager [With Installation Videos ]
  2. Oracle Identity Manager [With Installation Videos]

Objective : Install Oracle Fusion

The objective of this tutorial is to install Oracle Fusion Middleware using the documentation provided.

Resources

Use the following document for the installation

Notes

I used the following for doing the POC

  1. VMware WorkStation ( I tried with Vmware Server but had lot of issues )
  2. I Used Oracle Enterprise Linux 6.0

Steps

Prerequisites :

  1. Install VMware work station
Step 1: Install Oracle Enterprise Linux 6.0
Step 2 : Install Oracle database 11g r2 
Step 3 : Install Oracle Weblogic Server
Step 4 : Install Oracle Repository Creating Utility ( RCU)

Repository Creation Utility is a graphical and CLI-based tool used to create and manage Oracle Fusion Middleware database schemas

Step 5 : Install SOA

This is only Needed for Oracle OIM

Step 6 : Configuring  SOA

This is only Needed for Oracle OIM





What is MQSeries ? And where to get started

Posted on by
2

If you are familiar with JAVA and also familiar with JMS then it would make things very easy.

Couple of days back i met a person in my office, a very nice guy, and he recommended the following article to get started of and i also found it is very nice

http://www.redbooks.ibm.com/redpapers/pdfs/redp0021.pdf

Here are couple of highlights for starters,

  • It is a middleware for messaging and queuing.
  • MQSeries is used in a client/server or distributed environment
  • Message queuing is a method of program-to-program communication.
  • Messaging means that programs communicate with each other by sending data in messages and not by calling each other directly
  • Messaging is again 2 types,
  1. asynchronous messaging, the sending program proceeds with its own processing withoutwaiting for a reply to its message
  2. synchronous messaging waits for the reply before it resumes processing
  • Queuing means that programs communicate through queues. Programs communicating through queues need not be executed concurrently

Note : The programmer cannot specify the name of the target application to which a message is sent. However, he or she can specify a target queue name; and each queue is associated with a program.

MESSAGES

A message consists of two parts:
1. Data that is sent from one program to another
2. The message descriptor or message header [ Contains : Version, Message ID, …. etc ]

The message descriptor identifies the message (message ID) and contains control information,
also called attributes, such as message type, expiry time, correlation ID, priority, and the name of
the queue for the reply.
A message can be up to

4 MB or

100 MB long [ depending on the MQSeries version] you use.

Note : MQSeries Version 5 (for distributed platforms) supports a maximum message length of 100 MB.

  • Messages can be segmented or grouped

Message Segmenting and Grouping

  • the queue manager segments a large message when it does not fit in a queue
  • On the receiving end, the application has the option to either receive the entire message in one piece or each segment separately
  • A second method of segmenting leaves the programmer in control so that he or she can split a
    message according to logical boundaries or buffer size available for the program.
  • To reduce traffic over the network, you can also group several small messages together and build
    one larger physical message. This message is then sent to the destination and is there
    disassembled. Message grouping also guarantees that the order the messages are sent in is
    preserved.

Distribution Lists

  • send a message to more than one destination queue with one MQPUT call

Message Types

  • Datagram: A message containing information for which no response is expected.
  • Request: A message for which a reply is requested.
  • Reply: A reply to a request message.
  • Report: A message that describes an event such as the occurrence of an error or a confirmation on arrival or delivery

Persistent and Non-Persistent Messages

  • Delivery of persistent messages is assured
  • they are written to logs to survive system failures
  • Non-persistent messages cannot be recovered after a system restart

Queue Manager

This is the heart of MQSeries. –> message queue manager (MQM),

  • Manage queues and messages for applications
  • provides the Message Queuing Interface (MQI) for communication with applications
  • It coordinates updates to databases and queues using a two-phase commit. Gets and puts from/
    to queues are committed together with SQL updates, or backed out if necessary.
  • It segments messages (if necessary) and assembles them
  • It can send one message to more than one destination with one API call using a user-defined
    dynamic distribution list, thus reducing network traffic.
  • It provides additional functions that allow administrators to create and delete queues, alter the
    properties of existing queues,
  • MQSeries clients do not have a queue manager in their machines.

In contrast to MQSeries clients, each workstation that runs MQSeries for Windows (Version 2)
has its own queue manager and queues. MQSeries for Windows is a single-user queue manager
and is not intended to function as a queue manager for other MQSeries clients. This product is
designed for a mobile environment.
Note: MQSeries for Windows and MQSeries for Windows NT are two different products.

Queue Manager Clusters

  • Queue managers that form a cluster can run in the same machine or in different machines on different platforms
  • Clustering also permits multiple instances of a queue (with the same name) on different queue managers. This allows for workload distribution, that is, the queue manager can send messages todifferent instances of an application

Queue Manager Objects

  • The queue manager is an object, too.
  • Administrator creates one or more queue managersand their objects. A queue manager can use objects of the following types:

1. Queues
2. Process definitions
3. Channels

QUEUES

used to store messages sent by programs. There are local queues that are
owned by the local queue manager, and remote queues that belong to a different queue manager

Channels

A Channel is a logical communication link.

  1. Message Channel

A Message channel connects 2 Queue Manager via Message Channel Agents ( MCA )Such
a channel is unidirectional. It comprises two message channel agents, a sender and a receiver,
and a communication protocol. An MCA is a program that transfers messages from a transmissionqueue to a communication link, and from a communication link into the target queue.

  1. MQI channels

A Message Queue Interface (MQI) channel connects an MQSeries client to a queue manager
in its server machine. Clients don’t have a queue manager of their own. An MQI channel is
bidirectional.

A channel can use the following transport types: SNA LU 6.2, TCP/IP, NetBIOS, SPX and DEC
Net. Not all are supported on all platforms

Process Definitions

A process definition object defines an application to a queue manager. For example, it contains
the name of the program (and its path) to be triggered when a message arrives for it.

Queues are defined as objects belonging to a queue manager

Local queue

is a real queue

Remote queue

structure describing a queue

Transmission queue (xmitq)

local queue with special purpose

Initiation queue

local queue with special purpose

Dynamic queue

local queue created “on the fly”

Clients and Servers

There are two kinds of clients:
• Slim client or MQSeries client
• Fat client

Fat clients have a local queue manager; slim clients don’t.