Websphere Integration Developer 6.1 Tutorials

Generate a business process implementation

2009-06-09T18:07:00.001-07:00

Business Process
Websphere Integration Developer v612
Contact us...

Generate a business process Implementation

Generate a business process Implementation

Assembly Diagram

After laying out your components using the assembly editor, you can then generate an implementation for the components.

Interface

This is the interface that the ShippingProcess component uses.

Implementation types

To generate a business process implementation, right-click on a component (i.e ShippingProcess) and select Generate Implementation... > Process from the context menu.

You have 5 implementation types to choose from.

After you select the implementation type, you have to select the folder where the process implementation will be generated. Accept the default folder and click OK.

Generated Business Process implemention

The tooling generated a basic business process component, as shown below. Notice that the properties are derived from the relationship of this component to the other components as shown in the assembly diagram (see above).

Receive
A receive activity is an entry point to a process; it is the point where the process starts or continues. You need one receive activity per operation you define in the process's interface. In the process editor, you can specify which operation corresponds to which receive activity. That means that when a call is made to one of the process's operations, the corresponding receive activity accepts the call, and the process continues running from there. A process requires at least one receive activity to start. A receive activity can also occur in the middle of a business process. In this case, if the process encounters a receive activity while it is running, the process stops and waits for the corresponding operation to be called.

Note:
There is only a Receive activity because the Shipping interface is a one-way operation only. If it were a two-way operation (request/response), the tooling would have also generated a Reply activity in addition to the Receive activity.

Interface Partners
The term Interface Partner in this context is a little bit confusing. Within a process, we use the term partner to describe the other services that may be calling your interfaces, in this case, Shipping. Thus, any service that calls the Shipping interface is considered an Interface Partner. Put very simply, when a client calls your process, you can think of it as an interface partner that called you.

Reference Partners
In the assembly diagram above, you can see that ShippingProcess invokes ProcessOrder and ShippingTask.

Each reference of the component that the process implements corresponds to one reference partner within the process. When you call another service, you will do so using a reference partner.

Tennis Rackets

2009-06-01T20:43:00.001-07:00

Babolat AeroBlast
HEAD Agassi Radical Limited Edition Racquet Review
ProKennex 5G
ProKennex 7G Review
Wilson Hammer 6.2 95 (For Sale)

Babolat AeroBlast

The Babolat Aero Blast features Babolat's new Smart Grip technology. The grip is contoured to fit the shape of the hand. Babolat claims that this places the entire hand in contact with the racquet for more power with less effort, more control with less racquet twisting and more comfort due to the way the grip fits the natural shape of the hand. While the handle shape feels very different on the first pick-up, we quickly found the shape comfortable and natural feeling during play. Offering plenty of pop and a soft and dampened feel, the Aero Blast brings a solid combination of power and comfort to every shot. The large, oversize headsize, 112sq. inches, offers a generous sweetspot that has even off center shots leaving the strings with good pace. We found the racquet easy to maneuver which helped us generate impressive swing speed when hitting topspin shots from the baseline. The quick feel of this racquet translates well to net play, where we found this one easy to maneuver during fast exchanges. There's plenty of spin and pace to be found on serve. The large and forgiving headsize offers a consistent response and the racquet offers easy access to deep and penetrating serving. A solid choice for the 3.5-4.5 level player seeking a blend of power, comfort and spin from a forgiving racquet.

Technologies

HEAD Agassi Radical Limited Edition Racquet Review

In 1993 HEAD developed the original Radical racquet specifically for Andre Agassi. Agassi went on to win 37 of 60 titles with the Radical. Some of the most memorable Agassi victories with the HEAD Radical include his Olympic Gold Medal in Atlanta as well as seven of his eight Grand Slams. Agassi's record on court over the last 13 years has helped make the Radical one of the best-selling tennis racquets worldwide.

Here we review the Agassi Radical Limited Edition. This racquet is an exact replica of the Radical first used by Agassi in 1993. With only a limited number of racquets being produced worldwide, many may end up as collector racquets. However, we felt that to be somewhat of a shame, as we were impressed in our initial hitting sessions with the racquet. In fact, we were so impressed, we just had to let our review team loose with the Agassi Radical Limited Edition for a three-week playtest.

Groundstrokes

The solid and stable response of the 12.1 ounce Agassi Radical Limited Edition impressed our team from the baseline. We tested the racquet as shipped, complete with poly string, rubber band dampener and a blue overgrip. When the factory string began to tire, we restrung the racquet with a comparable leading polyester string that was favored by Agassi during his career.

Impressed by his consistent play with the racquet at the baseline was Spencer. "I was hitting very solid, reliable groundstrokes from both sides. This racquet made me feel very precise in striking the ball. Even off-center hits still felt very solid and stayed on track. I was very impressed with the consistency I was finding with this racquet. The weight of the racquet was noticeable after awhile, but something I'm sure I could adjust to. The power wasn't huge, but it does have enough when you need that little extra." Chris found hitting with the Agassi Radical Limited Edition to be a walk down memory lane. "Ah yes, this is the Radical I remember. Back as a college player I used the Twin Tube Radical Oversize, and this racquet definitely reminds me of that stick. It's been a long time since I've hit with a Radical that plays with such heft and stability. Definitely an old school player's racquet feel, and all the better for it. It's hard to think of another Oversize currently available that would compete with this stick from the baseline. During the test I compared it to the M Speed Pro One 105, the Gamma IPEX 7.0 Oversize and the Flexpoint Radical Oversize and none came close to the performance of this one. I found excellent stability and control on my groundstrokes. With the poly test string, the control from the stringbed was very good. I was able to take big cuts at the ball and be confident my shots would stay within the lines. The racquet felt very well suited to hitting topspin off both wings. I also found this stick to be surprisingly responsive on slice backhands. I was getting plenty of spin and bite on the ball and could either drive my slice deep or cut it for a sharp angle. However, big forehands were the order of the day. I had the most fun running around my backhand and trying to take the felt off the ball with my forehand."

Finding more pace and depth on his groundstrokes was Granville. "From the first few groundstrokes it was apparent I was getting more depth and pace with this racquet than my Wilson Hyper ProStaff 6.1! Combine that with the comfort of swinging a heavy racquet and you get a Radical unlike any in memory. I was getting over the ball with ease on the forehand and was mixing it up well by throwing in some sliders. Same applied to the backhand side. I found it particularly rewarding hitting winners with this racquet." Ryan found the racquet to play phenomenally well off the ground. "There is no doubt in my mind why Andre Agassi liked using this racquet. This racquet is phenomenal on groundies. There is a confidence with this racquet that I haven't found in many racquets. I hit exceptionally well with it. My depth was excellent and I found very good access to spin. The racquet was a bit hefty, but when I was actually swinging, it was just great. The amount of control I had was amazing. I haven't had this much control with a racquet that has decent power in a while. Usually, there is a decrease in control when the power is increased; not so with this racquet. Just sweet." Jon found he had plenty of options off both wings when hitting with the Agassi Radical Limited Edition. "The Agassi Radical Limited Edition is a solid racquet from the baseline. It has decent power, good spin potential, and great control. I had a lot of options with this racquet."

Finding good preparation to be rewarded with crushing power and spin was Jeremy. "I was very impressed with how the racquet handled at the baseline. The headsize and string pattern are perfect for my groundstrokes, whether I was hitting flat, topspin, or slice shots. With the static weight around 12 ounces, all my strokes felt very confident and comfortable. The main thing this racquet required of me was early preparation, as it does have a higher swingweight. Once I got my timing down, the Agassi Radical Limited Edition would crush through the ball, which I found to be very rewarding." Brad enjoyed a solid blend of power, control and stability when hitting with the racquet. "The Agassi Radical Limited Edition was very fun to hit with from the baseline. I found that the racquet offered a good balance of power and control. I do think that some of this was due to the premium polyester that the racquet was strung with, as it helped keep the large stringbed from being too lively. On forehands, I had good depth on all of my shots and I was able to land a lot of them just inside the baseline. It was easy to generate topspin when I wanted to, or flatten my shots when I didn't have as much time to set up for them. On backhands, I felt very comfortable swinging away at the ball. I never felt like it was going to sail on me or that I couldn't control where I wanted my backhand to go. Great control with a very solid feel."

Volleys

At net, the Agassi Radical Limited Edition continued to impress with its solid and stable response - although some testers struggled with the hefty feel. Enjoying the response of the racquet at net was Chris. "Again, the racquet felt very solid and stable. It never felt pushed around by the ball and I found plenty of control on my volleys. I was able to hit some nice angle shots with this stick and felt confident when hitting with touch and placement. I used this racquet in a high level doubles match where I was the lowest ranked player on the court. With the Agassi Radical Limited Edition I was able to hold my own at net and felt every bit as confident as when I volley with my regular stick." Brad struggled with the weight of the racquet at net. "I did struggle a bit with volleys using this racquet. This is one area where I feel that higher swingweight had an effect on my timing. I just wasn't able to get the racquet where I needed it to be in time to make good contact with the ball. I found a lot of my volleys going into the net. When I did manage to get volleys back to my opponent, I had good control of the ball, but not as much power as I would have liked."

Finding the heft of the racquet to be overshadowed by the precise response he found at net was Ryan. "My volleys were the one area that gave me a little bit of trouble. The only reason being that because of it's heft and being only about 6 points head light, the racquet is not quite as maneuverable as I would like. However, when you think of the person who used this racquet, there is no surprise. It was very accurate, and when I was in time and set up, my volleys were great. The extra square inches helped a lot, and made up a lot for the slight deficiency in maneuverability." Jeremy was another player to notice the heft of the racquet when pushing forward to volley. "Volleying would probably be the only downside to this racquet for me. If I was moving into the net after an approach shot, volleying the ball away was not an issue. However, when I would get stuck at the net the weight of the racquet would come into play on quick reaction volleys. There seemed to be just a little too much weight in the head. Aside from that, I found that I was hitting well-placed volleys with good pace." Spencer enjoyed the response of the racquet, but struggled with maneuverability. "Net play was so-so, as the maneuverability of this racquet was somewhat limiting, especially with a good paced shot coming at me. However, both touch and feel were great."

Granville appreciated the heft and solid response at net. "At six points head-light, the Agassi Radical Limited Edition was plenty maneuverable at the net. I was slicing, dicing and punching with ease. It was nice to know I had a racquet massive enough to handle any ball sent in my direction, as opposed to the lighter racquets that can rebound from the ball." Jon found the racquet easy to maneuver and forgiving at net. "With a 107 square inch head, there was plenty of real estate with the racquet to help get that volley back. I was surprised at the large forgiving sweetspot and the maneuverability of the racquet. At over 12 ounces I expected the Agassi Radical Limited Edition to be hard to maneuver at the net, but that wasn't the case. It's a fun racquet for volleying."

Serves

Our team found the Agassi Radical Limited Edition to be an excellent serving tool. Finding both control and power was Brad. "I found a good balance of power and control on my serves with this racquet. I really enjoyed hitting first serves and was able to place my serves up the T or out wide at will. On second serves, I was able to get good depth and pace on my kick serves." Hitting some big serves with the Agassi Radical Limited Edition was Granville. "Here is perhaps the biggest surprise; I loved serving with this racquet. I could rip my regular heaters and place the ball with precision. Kickers were kicking and I noticed my ball climbing a bit higher against the back fence once past my opponent." Chris was also pleased with the response of the racquet on serve. "I served well with this racquet. I was able to find some impressive spin and ample pace. No matter if I was sliding the ball out wide, trying to kick it up high or going for a heater down the middle, I was pleased with the response of the racquet. I was also hitting my overheads well with the racquet. A couple of times I caught the ball a little high in the stringbed and the racquet responded very well, with decent pace and accuracy."

Stepping up to the service line with confidence when using the Agassi Radical Limited Edition was Spencer. "I found I could serve with confidence as consistency once again came into play. It offered a good combination of power and spin on serves. Being able to put good kick and placement on my second serve, I instinctively was going for a bit more on my first. Like most things in life, confidence can be an effective catalyst." Ryan enjoyed serving with this racquet. "Serving was really fun with this racquet. There is good power and the spin was excellent. My kickers were a joy. Placement was very good and control was still great. I loved serving with this racquet. Again, because of the control that this racquet has there is a confidence that I had that made me serve better. I thought the heft was the only thing that might bother me, for the same reason that any racquet over 12 ounces does. But this racquet has a good amount of power, so I didn't mind the heft."

Jon said, "I had good results serving with the Agassi Radical Limited Edition. I was able to generate a lot of spin on my kick serve and a lot of pace on my flat serve. I liked the polyester on serve, as the control was much better than expected." Finding good access to spin was Jeremy. "Another great attribute with this frame was serving. With its 12 ounce weight and oversize head, I was able to put lots of spin on my serves without sacrificing too much speed. Flat serves were still easy to hit and had great pace. Not only that, but serves felt just as comfortable as the groundstrokes."

Returns

The key word from our team when returning with the Agassi Radical Limited Edition was confidence. The solid feel, predictable response from the stringbed, controllable power level and forgiving headsize allowed for aggressive and confident returning. Stepping in and taking a rip at the ball was Ryan. "Confidence was the key. I just took huge rips at the ball and the ball would stay in. This racquet was great for returning serve. The only area that I had trouble with was with my slice return. I floated a couple, which seemed odd, as I didn't really have any problem with that in the groundstrokes. However, I was able to really go after kick serves to the backhand, even when they were high, and feel like I was still getting decent depth (no easy task with a one hander)." Spencer returned well with the racquet. "Whether I was blocking back a hard first serve, or taking a full cut on a slower serve, my results were good. All in all a very comfortable feel." Jeremy continued to play confidently with the racquet. "The Agassi Radical Limited Edition is a very confidence inspiring racquet. This is true for the return of serve as well. After just hitting groundstrokes with it, I started feeling like I could add more power to the ball without the ball going long. This worked as well on the return of serve, as I found myself taking a bigger swing than usual and coming up with better results. When I had to take a shorter backswing on a serve with more speed on it, the 107 square inch head helped add a bit more pace to the ball."

Enjoying the stable response of the racquet when returning was Chris. "I enjoyed returning with this racquet. I was able to hit aggressively while maintaining good placement. The racquet placed plenty of mass behind the ball, offering some nice plough through even on hard hit serves. The stability also worked well when I was pulled wide and had to block the ball back. I felt very confident swinging away with this one and went after returns at full throttle." Finding life to be sweet when returning with the Agassi Radical Limited Edition was Granville. "When returning with the Agassi Radical Limited Edition, with its 12 ounce plus weight, I noticed that returning felt easier. I found if I got the racquet moving it would do much of the work for me. I could reflex my backhand returns low cross court or down the line. If taking the offensive, I was able to get over the ball and add some pace to it, putting my opponent on the defensive early in the point.

Brad found the racquet to offer greater stability than he expected from an oversize. "Serve returns with this racquet were good as long as I didn't take too big of a swing. The weight of this racquet and the large sweetspot made it easy to block serves back. I didn't have any issues with twisting of the racquet on off centered returns that some would expect from an oversized head." Jon was executing returns with great accuracy with the Agassi Radical Limited Edition. "The racquet has a solid feel and good control on service returns. I enjoyed the topspin I generated with this racquet, as I felt I could place the ball anywhere in the court."

Overall

This is an impressive racquet. If you want one of these as a collectable, you've got to get one to hit with, too. Our entire team enjoyed the solid response from all areas of the court offered by this racquet. Going head to head with other current oversize offerings, the Agassi Radical Limited Edition consistently came out ahead. A high level of comfort, controllable power and good access to spin on groundstrokes and serves combined with impressive stability and a forgiving response on volleys and returns. Those accustomed to lighter racquets might find the weight to take some getting used to, but once adjusted, one finds added comfort and a solid feel that's hard to beat. We found the poly string a good fit for the racquet, with an impressive blend of power and control coming from the stringbed. Players seeking even more comfort and/or power can try juicing things up with a multifilament string or natural gut. As for us, we like it just the way Agassi likes it, complete with poly string, a blue overgrip and a rubber band dampener.

Last Shots from our playtesters

Chris. "By far the best Radical Oversize I've hit with in recent years. I enjoyed the weight and player's feel that was present in this one, but has been missing in recent Radicals. While I'm sure many of these will be kept as collectables, this is a racquet that cries out to be hit with."

Spencer. "A pleasant surprise for me. Though the racquet was a bit heavier than I'm used to, it would only be a temporary adjustment. I can't say enough about the consistency. Even off-center hits stayed on track as the stability of this racquet is excellent. Visually, I am not a big fan of oversize racquets, but I could certainly get over that with this one!"

Granville. "I want one."

Ryan. "In my opinion, this racquet is great. I loved the blend of comfort, control, and power. I would recommend this racquet to anyone who plays a lot and does not mind a 12 ounce racquet. This is definitely one of the best racquets that I have ever used. I don't usually care for oversize either, but with this racquet, it was fine. Funny how I liked a really old racquet without any gizmos from 1994 better than a lot of newer model racquets!

Jeremy. "You just can't beat a good solid graphite frame. This racquet really lets you swing through the ball, gives you ample power and control. If you can handle a 12 ounce racquet, I would recommend picking up one of these Radicals."

Jon. "The Agassi Radical Limited Edition was no disappointment. I enjoyed hitting the Agassi Radical and would definitely consider it if I was in the market for a new stick."

Brad. "It's a shame that there aren't more oversized player's racquets on the market like this one. We tested this racquet against five other oversized player's racquets on the market and I found the Agassi Radical Limited Edition to be my favorite. The thing that the Radical had that the others didn't was a good balance of power, control and stability."

Agassi Radical Limited Edition Combined Scores

(Scores are determined by averaging individual play test scores)

Technical Specifications
Length	27 inches	69 centimeters
Head Size	107 square inches	690 square centimeters
Weight	12.1 ounces	343 grams
Balance Point	12.75 inches 32 centimeters	6pts Head Light
Construction	21 mm Straight Beam
Composition	Graphite
String Pattern	18 Mains / 19 Crosses

Babolat RDC Ratings
	Score	Grade
Flex Rating	63	Range: 0-100
Swing Weight	338	Range: 200-400

ProKennex 5G

ProKennex 7G Review

Wilson Hammer 6.2 95 (For Sale)

Photos

Determine the best component implementation type and characterist

2008-10-26T15:31:00.007-07:00

Programming Model and Design

Websphere Integration Developer v612

How to Determine the best component implementation type and characteristics when building a business process

Related links

Use the business process editor to create a business process component

2008-10-22T14:00:00.001-07:00

Component Implementation
Websphere Integration Developer v612
Contact us...

Use the business process editor to create a business process component (including path conditions, activities, snippets, etc.)

Business Process example

This is a business process editor window with a completed business process.

Receive activity

A receive activity is an entry point to a process; it is the point where the process starts or continues.

You need one receive activity per operation you define in the process's interface.

In the process editor, you can specify which operation corresponds to which receive activity. That means that when a call is made to one of the process's operations, the corresponding receive activity accepts the call, and the process continues running from there.

A process requires at least one receive activity to start. A receive activity can also occur in the middle of a business process. In this case, if the process encounters a receive activity while it is running, the process stops and waits for the corresponding operation to be called.

Below, you will find out other capabilities of the business process editor.

Using the Business Process Editor

Here are some of the functions you can do with the business process editor.

How to generate a business process implementation

How to add an activity to a Business Process

How to establish transaction boundaries within a business process

How to create a Business Module

How to add a Visual Snippet to a business process

How to setup a Business Process Invoke activity

How to Configure BPEL activities using the properties view

How to create a While loop

How to add activities inside a While Loop

How to add a variable-Business Process

How to initialize a variable using the Assign Activity

How to implement an event handler

How to implement a fault handler

How to add Qualities of Service (QoS) qualifiers to a Business Service

How to generate a business process implementation

How to add an activity to a Business Process

How to establish transaction boundaries within a business process

How to create a Business Module

How to add a Visual Snippet to a business process

How to setup a Business Process Invoke activity

How to Configure BPEL activities using the properties view

How to create a While loop

How to add activities inside a While Loop

How to add a variable-Business Process

How to initialize a variable using the Assign Activity

How to implement an event handler

How to implement a fault handler

How to add Qualities of Service (QoS) qualifiers to a Business Service

Adapter Patterns

2008-08-21T17:36:00.000-07:00

Adapter Patterns wizard How to

Websphere Integration Developer v612

Introduction

How to create an inbound Flat File service to read from a local file

How to create an outbound Flat File service to write to a local file

Introduction

Overview

Patterns enable the creation of integrated solutions based on pre-defined pieces. Websphere Integration Developer allows you to choose a pattern, provide relevant parameters exposed by a set of domain-specific wizards, which in turn create a deployable solution.

Patterns are useful time-savers in the creation of integrated solutions. They provide an already proven ready-to-use result. Patterns are basically parameterized Websphere Integration Developer artifacts that can generate single or multiple artifacts using existing or new modules or libraries.

Websphere Integration Developer facilitates the reuse of existing and new patterns using the Business Integration perspective.

Currently, the available patterns are:

Integration
- Adapters
  - Email
    - Create an outbound Email service to send mail
  - FTP
    - Create an inbound FTP service to read from a remote file
    - Create an outbound FTP service to write to a remote file
  - Flat File
    - Create an inbound Flat File service to read from a local file
    - Create an outbound Flat File service to write to a local file
Business processes
- Implementation
  - Human Task Client from Lotus Form

Related links

Working with patterns
Patterns
Adapter patterns overview
Adding patterns to the Patterns view
An introduction to the WebSphere Adapter for Flat Files (IBM DeveloperWorks)

How to create an inbound Flat File service to read from a local file

Related links	Creating a service with the adapter pattern wizard
Overview	The Flat File inbound pattern creates a service that retrieves a file from a directory on the local file system. If the file is not in an XML format, you can specify a data handler that will transform from the file content format to business objects. The file content can be split if the content contains multiple copies of the data structure for processing. The inbound service receives the file from the file system for processing. Do the following steps to create the inbound service using the adapter pattern wizard.
Activate Adapter Pattern wizard Right-click SeparateCustomers and select New > Project > From Patterns. A New from Pattern window is displayed.
Select Pattern to create In the New from Pattern window, select Flat File > Create an inbound Flat File.... and click Next. A New Inbound Flat File Service window is displayed. Note: WID 6.1.2 currently supports only the patterns on the right.
Set Flat File service name Change the Name to CustomersIn and click Next.
Set Business object and directory Click Browse besides the Business object: field and select Customer. Click Browse besides the Directory: field and select c:flatfilesinboundevents Click Next
Select Data Type Select Customer and click OK.
Business object and directory setup Business object and directory setup is complete. Click Next.
Set Input file format and file content split option Input file format Select XML File content split option Select Split file content by delimiter. In the field, enter `####;rn`. The delimiter is ####. The semi-colon (;) indicates there are more delimiters after the ####. The rn, in the Windows environment, indicates a new line. Click Next.
Specify the archive directory Click Browse to find the local directory to archive processed files. Click Finish.
The inbound Flat File service is created Note the following additions: CWYFF_FlatFile CustomersIn export CustomersIn interface Binding Resources There is also 1 warning: The export does not specify a target component or import.

How to create an outbound Flat File service to write to a local file

Related links	Creating a service with the adapter pattern wizard
Overview	The Flat File outbound pattern creates a service that stores data in a file in a directory on the local file system. If the required output format is not an XML format, you can specify a data handler that will transform the business object to the file content format. The outbound service outputs a file that has been processed to the file system. Do the following steps to create the outbound service using the adapter pattern wizard.
Activate Adapter Pattern wizard Right-click SeparateCustomers and select New > Project > From Patterns. A New from Pattern window is displayed.
Select Pattern to create In the New from Pattern window, select Flat File > Create an outbound Flat File.... and click Next.
Set Flat File service name Change the Name to SeparateCustomerOut and click Next.
Set Business object and directory Click Browse besides the Business object: field and select Customer. Click Browse besides the Directory: field and lookup c:flatfilesoutputdir Click Next
Select Data Type Select Customer and click OK.
Business object and directory setup Business object and directory setup is complete. Click Next.
Set Output file name The Output file name window opens. A variety of ways can be used to create an output file name. Accept the defaults, which will result in output files for each customer record in the format Customer.<number of customer record>.txt. The Customer.seq file will contain the number of customer records processed. Generating a random file name is useful if your application requires unique generated output file names. If, in creating the inbound service you had created a wrapper business object, then you would select the wrapper business object to specify the output file name. In that case, you can also select an append operation for writing all business objects to a single file rather than multiple files. Accect the defaults and click Next.
Select Output file format Select XML. Click Finish.
The outbound Flat File service is created Note the following additions: SeparateCustomersOut export (EIS binding) SeparateCustomersOut interface CommonSchemas under Data Types

Adapters (Flat File adapter app)

2008-08-21T08:32:00.000-07:00

Reading and Writing Files Application (Adapters) How to

Websphere Integration Developer v612

Completed Adapter application (Reading and Writing Files)

How to build the Adapter application (Reading and Writing Files)

Completed Adapter application (Reading and Writing Files)

Related links

Source

IBM Websphere Integration Developer 6.1.2 sample

Introduction

This tutorial will demonstrate how an application can read from a file on the file system and write to a file on the file system using the IBM® WebSphere® Adapter for Flat Files. You will also learn how to create an application with WebSphere Integration Developer that processes the incoming data before writing the processed data to the file on the file system. This tutorial is for developers who work with adapters generally and the Flat Files adapter specifically.

After completing this tutorial, you will understand how to use WebSphere Integration Developer with the WebSphere Adapter for Flat Files to develop a service that reads data from a file on the file system, processes the data and writes the processed data to a file on the file system. Specifically, you will learn how to perform the following tasks:

Develop an inbound service using the adapter pattern wizard with the Flat Files adapter to read data from a file on the file system
Develop an outbound service with the same wizard and adapter to write data to a file on the file system
Implement the business logic to process the data read from a file on the file system
Test your application.

The article An introduction to the WebSphere Adapter for Flat Files formed the basis of this tutorial.

Overview

When working with this tutorial, you should know several concepts related to flat files, adapters, processing data to and from an application created in WebSphere® Integration Developer with an adapter and have a high-level understanding of the application you will create.

The following concepts are discussed in this section:

Flat files
WebSphere Adapter for Flat Files
Inbound processing
File splitting
Record delimiters
Splitting by size
Custom data bindings
Outbound processing
Overview of the application in this tutorial

What is a Flat file?

The term flat file refers to any file stored on a local file system, as opposed to a more complex set of files, such as those in a structured database. The data records in a flat file are typically stored sequentially and without any metadata, such as the indices, keys, and relationships that you would find in database storage. You can use the adapter for flat files to read and write any type of file. However, you typically use the adapter for flat files to read and write text files that store records in a flat file format such as XML or Comma-Separated Values (CSV) records. The following example shows records in each format.

XML format

<?xml version="1.0" encoding="UTF-8"?> <customer> 	<title>Mr</title> 	<name>Smith</name> 	<city>Ottawa</city> 	<state>ON</state> </customer> <customer> 	<title>Mrs</title> 	<name>Jones</name> 	<city>Winnipeg</city> 	<state>MB</state> </customer>

CSV format

Mr,Smith,Ottawa,ON
Mrs,Jones,Winnipeg,MB

What is the WebSphere Adapter for Flat Files?

Suppose you have an external system that outputs sets of files to a directory. An example might be an order processing system that produces text files containing order information to be processed in a batch mode during off-peak hours. You would use the WebSphere Adapter for Flat Files along with WebSphere Integration Developer to help you process these files. Another information system might use sets of text files in a directory as input to programs. You would use the WebSphere Adapter for Flat Files along with WebSphere Integration Developer to help you create and manage these files.

Any WebSphere application can use the adapter for flat files to create and manage files or to monitor a directory and read files from this directory. You have two options when creating a service associated with adapter for flat files, both of which are documented in the information center of the product:

Adapter pattern wizard: With this wizard, you create a service by specifying the directories that the WebSphere Adapter for Flat Files reads from and writes to and formats of the data in those directories. Then the adapter pattern wizard generates the service. For many users, this quick and easy way of creating a service is sufficient. We will use this approach in this tutorial.
External service wizard: With this wizard, you create a service by a longer, more comprehensive process. Some users may find this more detailed approach more suitable. You begin by specifying the type of adapter you will require and then specify the directories that the WebSphere Adapter for Flat Files reads from and writes to, and the format of the data in those directories. Then you continue using further pages with fields in an advanced section to add more control over the generated service.

What are inbound and outbound processing?

Inbound processing is the mode of operation in which the WebSphere Adapter for Flat Files monitors the file system, reads new files, and sends the data to an operation in a WebSphere application.

Outbound processing is the mode of operation in which the WebSphere Adapter for Flat Files receives requests (from a component of a WebSphere application) to perform an operation on an enterprise information system and, when applicable, returns the results to the caller. Example operations include creating a file, writing to a file, or checking if a specific file exists.

Inbound processing

During inbound processing, the adapter for flat files listens for events that are produced by an event directory. An event is a record of what changes have occurred in the event directory. The directory that the adapter for flat files monitors for new files is called the event directory.

The following diagram shows the four steps that occur during inbound processing:

An external system outputs its files to the event directory.
The adapter for flat files polls for files from the event directory and converts the data from those files into events. The adapter can be configured to poll for only certain types of files, or for files created during a certain time period.
Events are temporarily placed in an event store. This is either a database or an in-memory representation of the event table. If you use a database, events will not be lost before your application can process them if the server goes down after an event is created, for example. This is referred to as assured delivery. Using in-memory tables, the event processing will be faster but you lose the event recovery capability.
The adapter for flat files retrieves the events from the event store and passes each event in the form of a business object through an exported inbound interface, which the adapter pattern wizard or the external service wizard created.

This method of retrieving data, that is, passing data in the form of a business object, is called non-pass-through or Data Transformation Framework (DTF), and it operates on structured data.

If the application does not know the format of the data files, you can configure the adapter for flat files to run in pass-through mode, operating on unstructured data. In that case, it would not transform an event into a business object.

File splitting

You use file splitting when the files you want to retrieve are large or they each contain more than one record. You can split files into smaller chunks based on a delimiter or on a fixed-size value, which allows parts of the file to be processed in parallel. Each chunk is considered a separate event and is individually sent to an operation in a WebSphere application through the exported inbound interface.

Record delimiter

Typically, input is stored as a single record per file. However, when the input file contains more than one record, you often separate the records in the file with a delimiter, which can be any text string and is usually a combination of characters followed by rn (platform dependent new line character). The adapter can both read and write files that contain a delimiter.

Using our XML format and CVS format examples discussed earlier, we have the string #### followed by a new line as the delimiter in the XML file shown in the following example. We have a new line as the delimiter in the CSV file.

XML format with #### as a delimiter

<?xml version="1.0" encoding="UTF-8"?> <customer> 	<title>Mr</title> 	<name>Smith</name> 	<city>Ottawa</city> 	<state>ON</state> </customer> #### <customer> 	<title>Mrs</title> 	<name>Jones</name> 	<city>Winnipeg</city> 	<state>MB</state> </customer> ####

CVS format with a new line as a delimiter

Mr,Smith,Ottawa,ON Mrs,Jones,Winnipeg,MB

Split by size

The split-by-size feature is similar to splitting by delimiter because you use it to divide a file into smaller chunks and transfer them to the operation in the WebSphere application one by one. However, use this feature with unstructured data in a pass-though scenario because the unstructured data is not going to be put into business objects. You specify the split criterion in the adapter as a number of bytes. The adapter reads the file as chunks (events) of that byte size. Each chunk will be the size defined by split criteria, except the last one, which might be smaller.

Custom data binding

Data in flat files can come in many different formats, such as the previously discussed XML and CSV formats. Others formats include name and value pairs, tab-separated, and fixed-width formats. A data binding maps from the format in the data files to the attributes of a business object.

Using the adapter for flat files default data binding, you can convert files to and from XML format. In other formats, you have to use custom data bindings that define the mapping between the file format and a business object. To implement a custom binding, create a Java™ class that converts the data for the specific format and enter this class in the adapter pattern wizard or external service wizard when you configure the adapter.

For more information about creating a custom data binding, refer to the WebSphere Adapters documentation.

Outbound processing

To write or modify files, the application uses the operations defined in the outbound interface, which you create using the adapter pattern wizard or the external service wizard. You can create both unstructured data (in pass-through mode) and structured data (in non-pass-through mode) using the different operation types:

Create – stores data to a new file or creates an empty file
Append – appends data to an existing file
Overwrite – overwrites an existing file with a new data
Delete – deletes an existing file
Exists – checks if a specific file exists
List – lists files in a directory
Retrieve – reads content from a file (binary only)

Only the create and append operations are used with the adapter pattern wizard.

Overview of the application in this tutorial

Imagine that you want to create an application that monitors a certain directory in a file system so that you can collect customer record information. When a file is created, the adapter calls the export with the data that is stored in a business object. The export is wired to a business process component that separates the data from the file into individual records that are each placed into their own file in an output directory.

This scenario is shown in the following diagram:

When files that contain customer records are in the inbound events directory, the resource adapter retrieves them, creates a customer business object, and calls an export in the module, which initiates a business process. The process generates a new file name based on the number of existing files, and specifies the output directory. Then, the business process writes the customer business object data to a separate XML file in the output directory of the file system.

Reading and Writing Files Application

Business Integration View

The business integration view shows all the resources used by the application (i.e data types, interfaces, etc..).

Assembly Diagram

The Assembly Diagram shows all the components used by the application (i.e export component, interface mapping component, and import components).

How to build the Adapter application (Reading and Writing Files)

Steps

Build the library
Build a Mediation Module
Assemble the mediation module
Implement the mediation flow component

Step1 Build the library

Resources such as interfaces and business objects should be contained in libraries so that they can be easily shared by modules.

Start building the Stock Quote sample by creating the resources library and its contents.

Create a new Project (workspace)
Create a library and call it Resources
Import a WSDL file into the Resources library. Refer to WSDL file at right for further details.
Create business objects (3) in the Resource library. Refer to business objects diagram at right for further details.
Create an interface (1) called StockQuoteService in the Resource library. Refer to interface diagram at right for further details.

Completed Resource library

WSDL File

Note: use the wsdl file found in IBM Websphere Integration Developer 6.1.2.
E:Program FilesIBMSDP70Sharedpluginscom.ibm.wbit.samples.content_6.1.200.v20080615_0659artifactsstockquotewsdl

Business objects diagram

Interface diagram

Step2 Build a Mediation Module

Create a mediation module called StockQuote.

Configure it to use the Resources library and to generate a default mediation flow component called StockQuote_MediationFlow

Step3 Assemble the Mediation Module

Mediation modules contain assembly diagrams that are wired together to form the integrated service application.

The StockQuote mediation module consists of the following elements:

StockQuoteService has a WSDL interface, called StockQuoteService, and uses SOAP/JMS web service binding so that the servlet front end can connect to the mediation module by using JAX-RPC. In this sample, you will create the StockQuoteService interface and generate the WSDL file.

- Drag the Resources Interfaces StockQuoteService to the Assembly diagram to create an Export with no Binding component.

- Rename the component to StockQuoteService.

-Generate Web Services binding on StockQuoteService
StockQuote_MediationFlow contains the mediation flow. In this sample, you will create and implement the StockQuote_MediationFlow component.
RealtimeService has a web service binding and an interface that matches the real-time (premium) service. In this sample, you will import the WSDL file RealtimeService.wsdl.

- Drag the Resources Interfaces RealtimeServicePortType to the Assembly diagram to create an Import with Web Service Binding component.

- Rename the component to RealTimeService.
DelayedService has a web service binding and an interface that matches the delayed (standard) service. In this sample, you will import the WSDL file DelayedService.wsdl.

- Drag the Resources Interfaces DelayedServicePortType to the Assembly diagram to create an Import with Web Service Binding component.

- Rename the component to DelayedService.

Wire the components as shown.

Step4

Adapters

2008-08-20T17:14:00.000-07:00

Adapter How to

Websphere Integration Developer v612

Introduction

How to add, configure, and bind an adapter

Introduction

Overview

Introduction

Adapters enables you to connect to enterprise information systems (EIS).

WebSphere® Adapters, also known as resource adapters, enable managed, bidirectional connectivity between enterprise information systems (EISs) and J2EE components supported by the server.

IBM® adapters allow you to integrate enterprise applications, and data storage facilities, in a service-oriented way. Adapters expose low-level EIS functions, or events, in the form of a service.

Adapters are sometimes referred to as resource adapters, and provide a standard interface to proprietary systems. Using standard interfaces avoids the maintenance issues associated with non-standard solutions.

Some adapters come with WebSphere® Integration Developer and are licensed for production use, others are only for development purposes: that is, they can be used to develop and test an application. Generally, after you deploy your application to WebSphere ESB, or WebSphere Process Server, you will need a licensed runtime resource adapter.

Types of adapters

There are two types of IBM adapters:

WebSphere Adapters

Also referred to as JCA adapters.
- WebSphere Adapters are based on Java™ 2 Platform, Enterprise Edition (J2EE) Connector architecture (JCA), and are the recommended adapters to use with WebSphere ESB and WebSphere Process Server.
- If an application is developed with a WebSphere Adapter embedded, the adapter is deployed with the application.
WebSphere Business Integration (WBI) Adapters
- WebSphere Business Integration Adapters reside outside of WebSphere ESB or WebSphere Process Server. The run time communicates with this type of adapter through a Java Message Service (JMS) transport layer.

Both types of adapter can be split into two classes:

Technology Adapters.
- Technology adapters let you integrate files, FTP, databases and email: these adapters come with WebSphere Integration Developer and are licensed for production use with WebSphere ESB and WebSphere Process Server.
Application Adapters.
- Application adapters let you integrate enterprise application suites, such as SAP Exchange Infrastructure (XI).

Related links

How to add, configure, and bind an adapter

Related links

Configuring and using adapters

Overview

Before you begin using an adapter, you first need to import it as a project into your application. Resource adapters are bundled into Resource Adapter Archive (RAR) files. RAR files are a type of ZIP file that contain the adapter and a set of additional files that help WebSphere Integration Developer (or any other tool) give you options on configuring the adapter.

There are several ways to add, configure, and bind an adapter. You can add an adapter using any of the following ways:

Use the adapter pattern wizard
This is the preferred way to add, configure, and bind an adapter. However, the adapter pattern wizard in WID 6.1.2 only support a few adapters.
Use the External service wizard
You can also use the External service wizard to add, configure, and bind any of the adapters available in WID 6.1.2.
Use the Palette
You can also use the Palette to add, configure, and bind any of the adapters available in WID 6.1.2.

How to add an adapter using the External service wizard

Related links	Configuring and using adapters
External Service Wizard In the Business integration view, right-click a module (i.e adapters) and select New > External Service.
Select External Service type Select the type of service you would like to access (i.e Adapters) and click Next.
Select an adapter Select the adapter you want to use and click Next.
Import an adapter Import a resource adapter archive (RAR) from the file system to create a connector project for the adapter. Select the target runtime (Webpshere process server v6.1 or Websphere ESB Server v6.1). Click Next.
Set processing direction Select the direction of adapter processing at runtime (i.e Outbound) and click Next.
Set Service configuration properties For this service, specify security and connection configuration properties as required. Click Next.

How to add an adapter using the Palette

Related links	Configuring and using adapters
Select an adapter from the palette The Palette shows all the available adapters (outbound/inbound) supported in WID 6.1.2. You can add outbound (imports) and inbound (exports) adapters using the Palette. To do this, click on an adapter (i.e Flat File) and drag/drop it into the Assembly diagram.
Select flat file service creation You have the option of creating a flat file service using the typical or advanced method. Select advanced and click Next.
Select an adapter Select the adapter you want to use and click Next.
Import an adapter Import a resource adapter archive (RAR) from the file system to create a connector project for the adapter. Select the target runtime (Webpshere process server v6.1 or Websphere ESB Server v6.1). Click Next.	Flatfile Project After importing the adapter, a Flatfile project is created by WID 6.1.2
Set Service configuration properties For this service, specify security and connection configuration properties as required. Click Next.

How to configure the flat file adapter

Related links	Configuring and using adapters
Overview The following adapters can be configured to work with WebSphere Integration Developer. In the documentation for each adapter, you will be shown how to use the external service wizard with the adapter as well as additional information that will be helpful such as field level reference information and runtime information.	WebSphere Adapter for Email WebSphere Adapter for Email enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to send e-mails to and receive e-mails from a mail server. WebSphere Adapter for Flat Files WebSphere Adapter for Flat Files enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus modules to interact with files on a local file system. WebSphere Adapter for FTP WebSphere Adapter for FTP enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to access files on an FTP server. WebSphere Adapter for JDBC WebSphere Adapter for JDBC enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to exchange information with a database. WebSphere Adapter for JD Edwards EnterpriseOne WebSphere Adapter for JD Edwards EnterpriseOne enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to interact with a JD Edwards EnterpriseOne server. WebSphere Adapter for Oracle E-Business Suite WebSphere Adapter for Oracle E-Business Suite enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to interact with Oracle database components. WebSphere Adapter for PeopleSoft Enterprise WebSphere Adapter for PeopleSoft Enterprise enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to exchange data with a PeopleSoft Enterprise server. WebSphere Adapter for SAP Software WebSphere Adapter for SAP Software enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to interact with SAP applications on an SAP server. WebSphere Adapter for Siebel Business Applications WebSphere Adapters for Siebel Business Applications enables applications running on WebSphere Process Server or WebSphere Enterprise Service Bus to exchange information with a Siebel Application Server. CICS ECI resource adapter The Customer Information Control System External Call Interface (CICS ECI) resource adapter lets you access programs on CICS servers. Working with the external service wizard, the CICS ECI resource adapter creates services that invoke CICS transactions on a CICS server. IMS TM resource adapter The IMS™ TM resource adapter is used by services to access IMS transactions running on host IMS systems. It can also be used for IMS transactions to access external services (calling out to external services requires IMS TM Resource Adapter Version 10). Using WebSphere Business Integration Adapters These adapters do not comply to either the J2C architecture or the Enterprise Metadata Discovery specification, yet can be used with the external service wizard.
Configuring an inbound flat file adapter For this service, specify security and connection configuration properties as required. Configuring the module for inbound processing Inbound configuration properties
Configuring an outbound flat file adapter For this service, specify security and connection configuration properties as required. Configuring the module for outbound processing Outbound configuration properties Click Next.

How to bind an adapter

Related links

Overview of adapters

Accessing external services with adapters

Configuring and using adapters

Overview

You can add an adapter as follows:

Use the adapter pattern wizard
Use the Pallette

Qualities of Service

2008-08-17T12:37:00.000-07:00

Qualities of Service How to

Websphere Integration Developer v612

Introduction

How to add qualities of service qualifiers to Interfaces

How to add qualities of service qualifiers to References

How to add qualities of service qualifiers to Implementation

Introduction

Related links	Quality of service: Qualifiers for business services Quality of service qualifier reference Viewing and changing qualifier settings
Qualities of Service Qualities of service can be added to: Interfaces References Implementation

How to add qualities of service qualifiers to Interfaces

Related links

Adding qualities of service qualifiers

Interfaces

Interface qualifiers are used to advertise the qualifiers supported by a target service, and therefore represent a contract with a client of the service. Qualifiers establish the preferred interaction style for the interfaces.

You can add the following qualifiers to interfaces:

Data validation
Determines whether the input data should be validated against its definition (ie. the XSD that describes the data).
Event sequencing
Places a control on the order in which the runtime environment processes events. When two or more events are received that invoke any of those operations that have the same key, the event sequencing qualifier ensures that they are processed in the order they are received. Without such a qualifier, the multithread runtime environment does not necessarily process events in the order that they are received.
Join activity session
Determines whether or not the hosting container will join any propagated (client) activity session.
Join transaction
Determines whether or not the hosting container will join any propagated (client) transaction.
Security permission
Specifies a role, which is a semantic grouping of permissions that a given type of users must have to use an operation in an interface. The identity of the caller must have this role in order to be permitted to call the interface or operation. If no security permission is specified, then no permissions are checked and all callers are permitted to call the interface or operation.

How to add qualifiers to an interface

Interface qualifiers can be applied at three levels of a component or import:

For all of its interfaces
For an individual interface
For an individual operation of an interface

To add qualifiers, click on Interfaces or CCam bil_DateTime_I or getTimeOfDay and then click Add.

Select the qualifier you need from the pop-up window.

All interfaces (Interfaces)	Individual Interface (CCambil_DateTime_I)	Individual operation of an interface (getTimeOfDay)

How to add qualities of service qualifiers to References

Related links

Adding qualities of service qualifiers

References

References qualifiers specify the reliability for asynchronous invocations and whether a target component’s methods should be federated as part of any client transaction.

You can add the following qualifiers to References:

Asynchronous invocation
Determines if asynchronous invocations should occur as part of any client transaction.
Reliability
Determines the quality of an asynchronous message delivery. In general, better performance usually means less reliable message delivery. With an Assured specification, the client application cannot tolerate the loss of a request or response message. With a Best effort specification, the client application can tolerate the possible loss of the request or response message.
Request expiration
The length of time after which an asynchronous request will be discarded if it has not been delivered, beginning from the time when the request is issued.
Response expiration
The length of time that the runtime environment must retain an asynchronous response or must provide a callback, beginning from the time when the request is issued.
Suspend activity session
Prevents the propragation of the activity session context to a target component. This applies when the target is invoked using the synchronous invocation.
Suspend transaction
Determines whether the invocation of a target service runs completely within the client's global transaction. This qualifier only applies to synchronous invocations.

How to add qualifiers to references

Reference qualifiers can be applied at two levels of a component or import:

For all of its references
For an individual reference

To add qualifiers, click on References or CCam bil_DateTime_IPartner and then click Add.

Select the qualifier you need from the pop-up window.

All References (References)	Individual References (CCambil_DateTime_IPartner)

How to add qualities of service qualifiers to Implementation

Related links	Adding qualities of service qualifiers
Implementation Qualifiers for implementation identify the service's authority and express its requirements for a transactional environment. You can add the following qualifiers to an Implementation: Activity session Determines if the component's processing will be executed under an activity session. An activity session is an alternative unit-of-work scope to the one provided by global transaction contexts. An activity session context can be longer lived than a global transaction context and can encapsulate global transactions. Security identity Specifies the identity under which the implementation executes at run time. Transaction The transaction qualifier determines the logical unit of work that the component's processing runs.
How to add qualifiers to implementation Select Properties/Implementation tabs. In the Implementation window, click Add and select the qualifier you need.

Export/Import (HTTP)

2008-08-10T10:57:00.000-07:00

Export/Import HTTP Binding How to

Websphere Integration Developer v612

Introduction

How to generate an HTTP export Binding

How to generate an HTTP import Binding

Introduction

When to use HTTP bindings

Consider an HTTP binding when these factors are applicable:

You need to access an external service over the Internet or provide a service over the Internet and you are working with other Web services based on the HTTP model; that is, using well-known HTTP interface operations like GET, PUT, DELETE, and so on.
The services are loosely coupled
Synchronous communication is preferred; that is, a request from one service can wait for a response from another.

Related links

Example of the HTTP binding

Uses of the HTTP binding

HTTP binding overview

Connectivity

Accessing services
Bindings
Service import and export binding types
Selecting appropriate bindings
Imports and exports

How to generate an HTTP export Binding

Related links	Generating an HTTP export binding HTTP data bindings
Generate HTTP Export In the assembly diagram, do the following: Right-click on a component (i.e DateTime_C) Select Generate Export > HTTP Binding An HTTP Export Binding window appears (see below).
Configure HTTP Export Service Configure the following HTTP export service properties: Context path Data binding (click Browse) Function selector (click Browse)
Configure Data Binding To configure data binding, do the following: Select data binding (i.e Show predefined data bindings ) Select Matching data binding (i.e HTTP XML message data binding). Click OK.
Configure Function Selector To configure function selector, do the following: Select function selector(i.e Show predefined function selectors ) Select Matching function selectors(i.e HTTP Function Selector based on URL...). Click OK.
HTTP export generated An HTTP export is generated.

How to generate an HTTP import Binding

Related links	Generating an HTTP import binding
Generate HTTP import from a HTTP export We will create an HTTP import binding from an existing HTTP export. Open the assembly diagram of a service requester module (i.e CCambil_Consumer_M) Drag a HTTP export (i.e DateTime_CExport) from another module(i.e CCambil_Provider_M) and drop it into the assembly diagram of the service requester module. A warning window appears (see below)
Creating Import from Export using HTTP binding A warning message is issued to do required configuration before deployment. Click OK.
HTTP Import binding generated An HTTP import binding is generated.

Generate Web Service import from a Web Service export

We will create a web service import binding from an existing web service export.

Open the assembly diagram of a service requester module (i.e CCambil_Consumer_M)
Drag a Web Service export (i.e CCambil_DateTime...) from a library (i.e CCambil_Library) and drop it into the assembly diagram of the service requester module (i.e CCambil_Consumer_M)
A Component Creation window will display (see below)

Select the type

In the Component Creation window, select Import with Web Service Binding and click OK.

A Web Service import binding is created.

Wire the Import

Wire the service requester component (i.e CCambil_Consumer_C) to the import as required.

Note:

Notice that the import and export web service binding properties are identical.

Export/Import (MQ)

2008-08-10T10:55:00.000-07:00

Export/Import MQ Binding How to

Websphere Integration Developer v612

Introduction

How to generate a MQ export Binding

How to generate a MQ import Binding

Introduction

When to use MQ bindings

Consider an MQ binding when these factors are applicable:

You need to access a WebSphere MQ messaging system and need to use the MQ native functions
The services are loosely coupled
Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.

Related links

Working with MQ bindings

WebSphere MQ (WMQ)

WebSphere MQ programming model

Connectivity

Accessing services

Service import and export binding types

Selecting appropriate bindings

How to generate an MQ export Binding

Related links	Generating an MQ export binding
Generate MQ Export In the assembly diagram, do the following: Right-click on a component (i.e DateTime_C) Select Generate Export > Messaging Binding > MQ Binding The Configure JMS Export Service dialog box opens (see below).
Configure Websphere MQ Export Service An interface with a two-way operation results in the dialog shown on the opposite column. Configure the MQ export service as follows: Message resource configuration Leave the default selection (Specify properties for configuring...). Request queue manager Enter any value (i.e MQqmgrname) Receive Destination queue Enter any value (i.e MQqnamereceivedest) Send Destination queue Enter any value (i.e MQqnamesenddest) Host Name Enter any value (i.e MQhostname) Leave the rest on default settings After configuring the required properties, click OK to continue (see JMS export binding generated below).
Select Data binding In the Data binding selection window, select the required data binding: Show data binding configurations (default) lists the data binding configurations you have created. Creating your own data binding configurations is discussed in Working with configurations that access external services. Show predefined data bindings lists the predefined data bindings provided by WebSphere Integration Developer. The available predefined data bindings are discussed in JMS, MQ JMS and generic JMS bindings. If you intend to use one of the default data bindings beginning with Simple JMS, you must have previously created the business objects required (see the Prerequisites section). Show data binding classes lists all data binding classes available. Click OK to continue.
Select function selector In the Function selector window, select the required function selector: Show function selector configurations (default) lists the function selector configurations you have created. Creating your own function selector configurations is discussed in Working with configurations that access external services. Show predefined function selectors lists the predefined function selectors provided by WebSphere Integration Developer. The available predefined function selectors are discussed in JMS, MQ JMS and generic JMS function selectors. Show function selector classes lists all function selector classes available.
MQ Export Binding generated The basic MQ binding is created and shown in the properties view when the Binding tab is selected. Note: The MQ binding is complete at this point. You would only change the values for the fields shown in the properties view if a change were required in the binding sometime after generation.
Messaging resource configuration blah blah blah....later

How to generate an MQ import Binding

Related Links	Generating an MQ import binding
Generate MQ import from an MQ export We will create an MQ import binding from an existing MQ export. Open the assembly diagram of a service requester module (i.e CCambil_Consumer_M) Drag the MQ export of the service provider module (i.e DateTime_CExport) which is in CCambil_Provider_M module and drop it into the assembly diagram of the service requester module (i.e CCambil_Consumer_M) A warning window appears (see below)
Creating Import from Export using MQ binding Essentially, this warning message requires you to deploy the export module first, otherwise a runtime exception will occur. Click OK to continue.
Wire the Import Wire the service requester component (i.e CCambil_Consumer_C) to the import as required.

Connectivity

2008-08-07T18:05:00.000-07:00

Connectivity How to

Websphere Integration Developer v612

Introduction

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Configure bindings to support asynchronous invocation patterns (JMS, MQ)
Create imports from external services
Add, configure, and bind an adapter
Use and configure the data binding framework

Introduction

Related links

Connectivity

Accessing services

Selecting appropriate bindings

Invocation Patterns

SCA provides four invocation patterns.

Synchronous - Client issues a request and waits for the response.
Asynchronous one-way - Client issues a request and a response is not expected.
Asynchronous deferred response - Client issues a request and the response will be requested by the client at a later point in time.
Asynchronous call back - Client issues a request and the target will call a service implemented by the client with the response.

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Related links

JMS binding configuration

Use JMS binding when you need to access a messaging system

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

MQ binding configuration

Use MQ binding when you need to access a WebSphere MQ messaging system and need to use the MQ native functions.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

Web Service binding configuration

Use Web Service binding when you need to access an external service over the Internet or provide a service over the Internet

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

HTTP configuration

Use HTTP binding when you need to access an external service over the Internet or provide a service over the Internet and you are working with other Web services based on the HTTP model; that is, using well-known HTTP interface operations like GET, PUT, DELETE, and so on.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

Configure bindings to support asynchronous invocation patterns (JMS, MQ)

Related links

Asynchronous invocation qualifier

SCA asynchronous invocation patterns in depth

JMS binding configuration

MQ binding configuration

Create imports from external services

Related links

Add, configure, and bind an adapter

Related links

Use and configure the data binding framework

Related links

Visual Snippet

2008-08-06T17:20:00.000-07:00

Visual Snippet How to

Websphere Integration Developer v612

How to create custom Java logic using the visual snippet editor

How to create custom Java logic using the visual snippet editor

Related links	Visual snippet editor The building blocks of the visual snippet editor Customizing behavior with visual snippets Unleashing visual snippets and business state machines in your service-oriented application
This is a Completed Visual Snippet. It will do the following: Accept an input parameter and prints it on the Console. It will create a new instance of a Business Object. It will retrieve the current date and time and return it. The following steps below describe the activities in detail.
1-Create a Visual Snippet Right-click the Reply activity and select Insert Before > Snippet.
2-Empty Visual Snippet An empty Visual Snippet is created with a default name of Snippet. Change the default snippet name as required.
Select Visual Snippet Right-click inside the visual snippet editor canvas and select the required visual snippet.
Print the input parameter on the Console Add an expression (Expression) and populate as shown. Add a print to log utility (Standard...> utility folder**) Wire the expression to the print to log.
Create a New Instance of of a Business Object. Add the namespace and name of the Business Object to create BO ((Standard...> SCA Services folder)
Return the date and time

Importing/Exporting WSDL Files

2008-07-22T13:40:00.000-07:00

Importing/Exporting WSDL Files How to

Websphere Integration Developer v612

How to import a WSDL

How to import a WSDL

Related links

Importing WSDL files

Importing and exporting WSDL files

Import a file

In the business integration view, right click on a library (i.e Resources) or module and select Import...

Select an Import source

Expand Business Integration folder and select WSDL/Interface.
Click Next.

Set WSDL/Interface Import

Enter the location of the WSDL file you want to import (Import from: ) or click Browse... to find the WSDL file in your computer/network file system.
Select the WSDL file you want to import.
Check Import dependent resources.
Click Finish.

Note:

use the wsdl file found in IBM Websphere Integration Developer 6.1.2.
E:Program FilesIBMSDP70Shared

pluginscom.ibm.wbit.samples.content_6.1.200.v20080615_0659

artifactsstockquotewsdl

WSDL files importation generated artifacts

After WSDL files importation, the following artifacts were generated/added to the library (i.e Resources).

Business objects were created/added to the Data Types folder
Interfaces were created/added to the Interfaces folder
Web Services Ports folder was created/added including the specific ports

Before	After

RealtimeService.wsdl file

You can copy this into a notepad file and then change the extension from .txt to .wsdl file.

You can then import it as a WSDL file.

<?xml version="1.0" encoding="UTF-8" ?>

- <!--

 @copyright_start@      Licensed Materials - Property of IBM      5724-I82, 5724-L01, 5655-N53, 5655-R15      (C) Copyright IBM Corporation 2005. All Rights Reserved.      US Government Users Restricted Rights- Use, duplication or disclosure      restricted by GSA ADP Schedule Contract with IBM Corp.      @copyright_end@

-->

- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://stockquote.samp.sibx.websphere.ibm.com/RealtimeService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="RealtimeService" targetNamespace="http://stockquote.samp.sibx.websphere.ibm.com/RealtimeService/">

- <wsdl:types>

- <xsd:schema targetNamespace="http://stockquote.samp.sibx.websphere.ibm.com/RealtimeService/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

- <xsd:element name="symbol">

- <xsd:complexType>

- <xsd:sequence maxOccurs="1" minOccurs="1">

<xsd:element maxOccurs="1" minOccurs="1" name="symbol" type="xsd:string" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

- <xsd:element name="value">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element maxOccurs="1" minOccurs="1" name="value" type="xsd:float" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:schema>

</wsdl:types>

- <wsdl:message name="getQuoteResponse">

<wsdl:part name="value" type="xsd:float" />

</wsdl:message>

- <wsdl:message name="getQuoteRequest">

<wsdl:part name="symbol" type="xsd:string" />

</wsdl:message>

- <wsdl:portType name="RealtimeServicePortType">

- <wsdl:operation name="getQuote">

<wsdl:input message="tns:getQuoteRequest" />

<wsdl:output message="tns:getQuoteResponse" />

</wsdl:operation>

</wsdl:portType>

- <wsdl:binding name="RealtimeServiceSOAP" type="tns:RealtimeServicePortType">

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />

- <wsdl:operation name="getQuote">

<soap:operation soapAction="http://stockquote.samp.sibx.websphere.ibm.com/RealtimeService/getQuote" />

- <wsdl:input>

<soap:body use="literal" />

</wsdl:input>

- <wsdl:output>

<soap:body use="literal" />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

- <wsdl:service name="RealtimeService">

- <wsdl:port binding="tns:RealtimeServiceSOAP" name="RealtimeServiceSOAP">

<soap:address location="http://localhost:9080/RealtimeService/services/RealtimeServiceSOAP" />

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

DelayedService.wsdl file

You can copy this into a notepad file and then change the extension from .txt to .wsdl file.

You can then import it as a WSDL file.

<?xml version="1.0" encoding="UTF-8" ?>

- <!--

 @copyright_start@      Licensed Materials - Property of IBM      5724-I82, 5724-L01, 5655-N53, 5655-R15      (C) Copyright IBM Corporation 2005. All Rights Reserved.      US Government Users Restricted Rights- Use, duplication or disclosure      restricted by GSA ADP Schedule Contract with IBM Corp.      @copyright_end@

-->

- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://stockquote.samp.sibx.websphere.ibm.com/DelayedService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="DelayedService" targetNamespace="http://stockquote.samp.sibx.websphere.ibm.com/DelayedService/">

- <wsdl:types>

- <xsd:schema targetNamespace="http://stockquote.samp.sibx.websphere.ibm.com/DelayedService/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

- <xsd:element name="symbol">

- <xsd:complexType>

- <xsd:sequence maxOccurs="1" minOccurs="1">

<xsd:element maxOccurs="1" minOccurs="1" name="symbol" type="xsd:string" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

- <xsd:element name="value">

- <xsd:complexType>

- <xsd:sequence maxOccurs="1" minOccurs="1">

<xsd:element maxOccurs="1" minOccurs="1" name="value" type="xsd:float" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:schema>

</wsdl:types>

- <wsdl:message name="getQuoteResponse">

<wsdl:part name="value" type="xsd:float" />

</wsdl:message>

- <wsdl:message name="getQuoteRequest">

<wsdl:part name="symbol" type="xsd:string" />

</wsdl:message>

- <wsdl:portType name="DelayedServicePortType">

- <wsdl:operation name="getQuote">

<wsdl:input message="tns:getQuoteRequest" />

<wsdl:output message="tns:getQuoteResponse" />

</wsdl:operation>

</wsdl:portType>

- <wsdl:binding name="DelayedServiceSOAP" type="tns:DelayedServicePortType">

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />

- <wsdl:operation name="getQuote">

<soap:operation soapAction="http://stockquote.samp.sibx.websphere.ibm.com/DelayedService/getQuote" />

- <wsdl:input>

<soap:body use="literal" />

</wsdl:input>

- <wsdl:output>

<soap:body use="literal" />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

- <wsdl:service name="DelayedService">

- <wsdl:port binding="tns:DelayedServiceSOAP" name="DelayedServiceSOAP">

<soap:address location="http://localhost:9080/DelayedService/services/DelayedServiceSOAP" />

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

Miscellaneous

2008-07-17T09:14:00.000-07:00

Miscellaneous How to

Websphere Integration Developer v612

How to add a Component/Node

How to apply late binding techniques

How to add Qualities of Service (QoS) qualifiers to a Business Service

How to generate an Implementation

How to login to the Administrator Console
How to wire nodes

How to apply late binding techniques

What are the benefits of late binding?

Late binding enables you to make your running application dynamic and flexible so it can handle changing business conditions without requiring you to redeploy the application.

When a client invokes a process, that client can be configured either to choose a specific version each time, or to pick up the currently valid version of the process. This is the basic concept behind early binding and late binding.

With early binding, a client is hard-wired to a process in such a way as to force a continued relationship between the two of them, even if another version of the process becomes available.

In contrast, with late-binding the relationship between the client and the process is dynamic in that it is resolved in the runtime environment.

In other words, if the caller instantiates a process using early binding, a specific version of the process is used to create that instance, and if they use late binding, the currently valid version of the business process is used.

What are the techniques for late binding?

You can use the following techniques for late binding

Versioning
Using Selectors
Using Business rules

How to login to the Administrator Console

Select Server to log into

Click the Servers tab.
Right-click the required Server (WESB or WPS) and select Run administrative console.

Enter User ID

Enter your User ID (any user ID is acceptable) and click Log in.

The Admin Console is displayed.

How to add Qualities of Service (QoS) qualifiers to a Business Service

Qualities of Service Qualities of service can be added to: Interfaces References Implementation
Interfaces You can add the following qualifiers: Join activity session Join transaction Security permission To add qualifiers, click on Interfaces or Shipping or shipOrder and then click Add. Select the qualifier you need from the pop-up window.
References You can add the following qualifiers: Asynchronous invocation Reliability Request expiration Response expiration Suspend activity session Suspend transaction To add qualifiers, click on References or ProcessOrderPartner or ShippingTaskPartner and then click Add. Select the qualifier you need from the pop-up window. Note: Note that the Add button is in-active when you click on ProcessOrder or orderShipped.
Implementation You can add the following qualifiers: Activity session Security identity Transaction To add qualifiers, click Add and select the qualifier you need from the pop-up window.

How to wire nodes

Wired nodes example
Display the wire handle Hover the mouse over the component to display the wire. Click the wire tip to drag it.
Drag and Drop Drag the wire to another component and drop it.
Click OK.

How to generate an Implementation

1-Select an implementation type

Right-click the component and select Generate Implementation... > Process.

Note:

You have 5 implementation types to select from. Choose the required implementation type.

2-Select the folder

Click OK if this is the required folder. Otherwise, click New Folder... and specify another folder.

3-A Default Business Process Implementation

How to add a Component/Node

1-Open the Assembly Diagram

Double-click the assembly diagram icon in the Business Integration view to open the Assembly Diagram.

2-Add a Component/Node

Right-click inside the Assembly Diagram and select Add Node > ???

You can add the following:

Business Module:

Mediation Module:

3-A Component is added

You can rename the component as required.

Projects

2008-07-17T09:06:00.000-07:00

Projects How to

Websphere Integration Developer v612

How to create a new project

How to deploy or remove a project

How to create a new Project

Related links	Creating a new project
Start Websphere Integration Developer 6.1 Start Websphere Integration Developer 6.1. Enter Workspace location and click OK.
Close Welcome Window Close the Welcome window by clicking on the X on the right side of Welcome
A new workspace is created A new workspace is created displaying the Business Integration view as the default view. You can now begin to define your projects.

How to deploy or remove a project

Select the deployment server Select the Servers tab Right-click the Server you want to deploy to (i.e Websphere Process Server) and select Add and remove projects... Pre-requisite The server must have been started.
Select the Project Select the project you want to deploy and click Add >.
Complete deployment Click Finish to complete the deployment.
Check deployment status The project deployment completed successfully when you see 'Application started: xxxxxModApp'.
Remove a project To remove a project, select the project you want to remove and click < Remove, and then click Finish.

Migration

2008-07-16T18:06:00.000-07:00

Migration How to

Websphere Integration Developer v612

Migrating Websphere Integration Developer 6.0.xx to 6.1.2 using Project Interchange

Related links	Migrating to WebSphere Integration Developer
Error during import A project (completed version) created in Websphere Integration Developer 6.0.xx is imported into WID 6.1.2 using Project interchange. Errors occured during the importation. Below are the steps to be taken to fix the problem.
Open interface Double-click the ShippingTask interface to open it.
Reselect business objects In the ShippingTask interface editor, select the Input Type (i.e Order) and re-select it. Do the same thing for the Output Type (i.e ShippedOrder).
Clean the Project Click on the Project menu and select Clean.
Clean all projects Select Clean all projects and click OK. Note: If the error indicators stills shows up, you have to re-start WID 6.1.2.
Re-start WID 6.1.2 Exit and re-start WID 6.1.2 to refresh the workspace and remove the error indicator (maybe another WID 6.1.2 bug). No more errors!!!

Mediation Flow (StockQuote Application)

2008-07-16T12:48:00.001-07:00

StockQuote Application (Mediation Flow) How to

Websphere Integration Developer v612

Completed StockQuote Application (Mediation Flow)

How to build the StockQuote Application (Mediation Flow)

Completed StockQuote Application (Mediation Flow)

Related links
Source	Websphere Integration Developer 6.1.2 runtime
Introduction	The Stock Quote sample demonstrates how you can easily integrate different services and manipulate messages at runtime without affecting the client applications. This integration is achieved through the Service Component Architecture and mediation functionality provided by the WebSphere® Enterprise Service Bus. The StockQuote mediation service is built with the business integration tools for building mediations: the assembly editor and the mediation flow editor. Mediation flows intercept and modify messages that are passed between existing services (providers) and clients (requesters) that want to use those services. This sample runs on WebSphere Enterprise Service Bus v 6.1 or WebSphere Process Server v 6.1.
Overview	This Stock Quote sample addresses the business need of a financial services company that provides an interactive Web-based stock market service to its customers. The company wants to differentiate itself from its competition by offering tiered levels of service. The company's goal is to offer delayed stock quotes to their standard customers and real-time quotes to their premium customers, that is, customers who pay a subscription. The company wants to: Offer the delayed and real-time stock quote services as a single service, which dynamically determines which external service to invoke based on the customer's subscription level. If the real-time service is unavailable, route requests to the delayed service without affecting the running application. Log all requests to the service to satisfy audit requirements.
StockQuote Application Business Integration View The business integration view shows all the resources used by the application (i.e data types, interfaces, etc..). Assembly Diagram The Assembly Diagram shows all the components used by the application (i.e export component, mediation flow component, and import components).
StockQuote_MediationFlow - Request This is the completed StockQuote_MediationFlow: Request
StockQuote_MediationFlow - Response This is the completed StockQuote_MediationFlow: Response

How to build the StockQuote Application (Mediation Flow)

Steps

Build the library
Build a Mediation Module
Assemble the mediation module
Implement the mediation flow component

Step1 Build the library

Resources such as interfaces and business objects should be contained in libraries so that they can be easily shared by modules.

Start building the Stock Quote sample by creating the resources library and its contents.

Create a new Project (workspace)
Create a library and call it Resources
Import a WSDL file into the Resources library. Refer to WSDL file at right for further details.
Create business objects (3) in the Resource library. Refer to business objects diagram at right for further details.
Create an interface (1) called StockQuoteService in the Resource library. Refer to interface diagram at right for further details.

Completed Resource library

WSDL File

Note: use the wsdl file found in IBM Websphere Integration Developer 6.1.2.
E:Program FilesIBMSDP70Sharedpluginscom.ibm.wbit.samples.content_6.1.200.v20080615_0659artifactsstockquotewsdl

Business objects diagram

Interface diagram

Step2 Build a Mediation Module

Create a mediation module called StockQuote.

Configure it to use the Resources library and to generate a default mediation flow component called StockQuote_MediationFlow

Step3 Assemble the Mediation Module

Mediation modules contain assembly diagrams that are wired together to form the integrated service application.

The StockQuote mediation module consists of the following elements:

StockQuoteService has a WSDL interface, called StockQuoteService, and uses SOAP/JMS web service binding so that the servlet front end can connect to the mediation module by using JAX-RPC. In this sample, you will create the StockQuoteService interface and generate the WSDL file.

- Drag the Resources Interfaces StockQuoteService to the Assembly diagram to create an Export with no Binding component.

- Rename the component to StockQuoteService.

-Generate Web Services binding on StockQuoteService
StockQuote_MediationFlow contains the mediation flow. In this sample, you will create and implement the StockQuote_MediationFlow component.
RealtimeService has a web service binding and an interface that matches the real-time (premium) service. In this sample, you will import the WSDL file RealtimeService.wsdl.

- Drag the Resources Interfaces RealtimeServicePortType to the Assembly diagram to create an Import with Web Service Binding component.

- Rename the component to RealTimeService.
DelayedService has a web service binding and an interface that matches the delayed (standard) service. In this sample, you will import the WSDL file DelayedService.wsdl.

- Drag the Resources Interfaces DelayedServicePortType to the Assembly diagram to create an Import with Web Service Binding component.

- Rename the component to DelayedService.

Wire the components as shown.

Step4

Websphere Integration Developer 6.1 Tutorials

Generate a business process implementation

Generate a business process Implementation

Assembly Diagram

Interface

Implementation types

Generated Business Process implemention

Related links

Tennis Rackets

Babolat AeroBlast

HEAD Agassi Radical Limited Edition Racquet Review

ProKennex 5G

ProKennex 7G Review

Wilson Hammer 6.2 95 (For Sale)

Determine the best component implementation type and characterist

How to Determine the best component implementation type and characteristics when building a business process

Use the business process editor to create a business process component

Use the business process editor to create a business process component (including path conditions, activities, snippets, etc.)

Related links

Adapter Patterns

Contents

Introduction

How to create an inbound Flat File service to read from a local file

How to create an outbound Flat File service to write to a local file

Adapters (Flat File adapter app)

Contents

Completed Adapter application (Reading and Writing Files)

How to build the Adapter application (Reading and Writing Files)

Adapters

Contents

Introduction

How to add, configure, and bind an adapter

How to add an adapter using the External service wizard

How to add an adapter using the Palette

How to configure the flat file adapter

How to bind an adapter

Qualities of Service

Contents

Introduction

How to add qualities of service qualifiers to Interfaces

How to add qualities of service qualifiers to References

How to add qualities of service qualifiers to Implementation

Export/Import (HTTP)

Contents

Introduction

How to generate an HTTP export Binding

How to generate an HTTP import Binding

Export/Import (MQ)

Contents

Introduction

How to generate an MQ export Binding

How to generate an MQ import Binding

Connectivity

Contents

Introduction

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Configure bindings to support asynchronous invocation patterns (JMS, MQ)

Create imports from external services

Add, configure, and bind an adapter

Use and configure the data binding framework

Visual Snippet

Contents

How to create custom Java logic using the visual snippet editor

Importing/Exporting WSDL Files

Miscellaneous

How to apply late binding techniques

How to login to the Administrator Console

How to add Qualities of Service (QoS) qualifiers to a Business Service

How to wire nodes

How to generate an Implementation

How to add a Component/Node

Projects

How to create a new Project

How to deploy or remove a project

Migration

Table of Contents

Migrating Websphere Integration Developer 6.0.xx to 6.1.2 using Project Interchange

Mediation Flow (StockQuote Application)

Table of Contents