You can import and export your WebSphere Application Server or WebSphere Process Server profiles into .CAR archive files.

Importing and exporting version 6 WebSphere Application Server profiles provides the specific wsadmin (or RAD/WID) steps to perform.

Related Posts

• Follow up to Profile Creation Fails on WebSphere 6.1.0.19: Java Juristiction Policy Files
• Migration to WebSphere Process Server and WebSphere Enterprise Bus 6.2 – Mandatory reading
• Profile Creation on WebSphere Application Server 6.1.0.19 Fails with Certificate Error
• Exploring The Contents of a WID Module Project
• IBM APAR PK49507: PROFILE RECREATION Required!

Your business has decided to use CEI to emit business relevant events, you got approval for your project, you are ready to code.. and then find out that there’s a thin amount of documentation on how to actually work with the APIs.

Below are some links that can help you figure out whats going on:

Use the Event Catalog in the IBM Common Event Infrastructure

Related Posts

• How to emit a Common Base Event in Java
• WebSphere Process Server v6.1 API
• WebSphere Admin Console SRVE0190E: FileNotFound Errors when clicking certain hyperlinks
• WebSphere Process Server Discussions
• Event Sequencing Message Locking – Resolution!

If you would like to specify a constant value for an XPath Duration (used in a wait activity or an escalation) you can follow the format specified by the w3 consortium for durations.

The lexical representation for duration is the [ISO 8601] extended format PnYn MnDTnH nMnS, where nY represents the number of years, nM the number of months, nD the number of days, ‘T’ is the date/time separator, nH the number of hours, nM the number of minutes and nS the number of seconds. The number of seconds can include decimal digits to arbitrary precision.

Weirdly enough, the duration needs to start with a ‘P’.

Also, if you are in the WebSphere Integration Developer editors, ensure that your constant is contained within single quotes.

'PT2M'

as opposed to

PT2M

The latter will cause the runtime to look for a child element named PT2M.

Related Posts

• WebSphere Transformation Extender – “One or More Inputs was Invalid”
• Variable Substitution in WSAdmin: Variables in braces are treated as constants
• Versioning business processes and human tasks in WebSphere Process Server
• Business Object Maps and ‘Required’ Attributes
• Interop between BOXMLSerializer and JMSDataBindingImplXML

Uninstalling or updating the WebSphere V6.1 test environment using Installation Manager; Update Failed.

If you try to update your WebSphere Process Server Unit Test Server from 6.1 to 6.1.2, you may run into an error. This can occur because updates have been applied to the server outside of Installation manager. Basically, WID’s Installation Manager and WPS’s Update Manager are out of sync with each other. This document explains how to fix the problem.

It is also noted that this synchronization issue is fixed in 6.1.2.1.

As usual, ensure you read the appropriate update documentation before attempting any upgrades.

Related Posts

• Upgrading WebSphere Integration Developer v6.1 – Installation Manager
• Upgrading WebSphere Application Servers – Update the Deployment Manager First!
• Venting some WebSphere Integration Developer Steam
• Problem Determination and WebSphere Integration Developer
• Close WebSphere Integration Developer when updating Fixpacks for WebSphere Process Server

From DeveloperWorks, Managing tasks and business processes using WebSphere Business Space:

Learn how to create WebSphere BPM V6.1.2 Business Space dashboards using the run-time artifacts from the WebSphere BPM V6.1.1 Clips and Tacks tutorial. You'll create a business space to manage the tasks and business forms input, run some processes that use forms, and finally create a business space you can use to monitor the process and tasks.

A good resource if you'd like to know more about what a 'Business Space' is.

Related Posts

• Managing tasks and business processes using WebSphere Business Space
• Versioning business processes and human tasks in WebSphere Process Server
• WebSphere Business Process Management V6.1.2 Production Topologies
• What’s new in WebSphere Integration Developer V6.2
• Building clustered topologies in WebSphere Process Server V6.1

From DeveloperWorks, WebSphere Process Server operational architecture: Part 1: Base architecture and infrastructure components

Part 1 of this two-part article series dives deeply into the operational architecture of IBM WebSphere Process Server. This article introduces you to concepts, such as Service Component Architecture (SCA), Business Process Choreographer (BPC) and Service Integration Bus (SIB) in the context of WebSphere Process Server, and shows you how they work together to build a secure transactional runtime environment for your SOA. In this respect, you will be able to better articulate the technical architecture of WebSphere Process Server, which will improve your ability to operate WebSphere Process Server in your organization..

Theres always a desire to understand the architecture and implementation of complicated software that makes your life 'easier'. This is a great article that delves into the layers that compose Process Server and WebSphere Integration Developer.

Related Posts

• SCA Component for Ruby with WebSphere Process Server
• Developing integration solutions with WebSphere Process Server relationships
• Use ARM to monitor SCA invocations in IBM WebSphere Process Server
• Asynchronous SCA One-Way Operations And How To Recover
• WebSphere Integration Developer & WebSphere Process Server v6.1.2 released

From DeveloperWorks, What’s new in WebSphere Integration Developer V6.2

New enhancements to IBM® WebSphere® Integration Developer V6.2 support the latest features and standards provided by WebSphere Process Server and WebSphere ESB V6.2. … You’ll learn about the solution view, editor enhancements, and services gateway pattern support, and be introduced to new features like business calendars and support for the Web Services Feature Pack. You’ll also learn about improved testing and problem determination, along with enhancements for migration

It’s the most wonderful time of the year, the holiday season because it means that we’re getting new versions of WebSphere Process Server and WebSphere Integration Developer! I’ll go through the list of features:

WebSphere Business Modeler interaction

I’m not sure what to make of this feature. One of the new parts that I’m sure IBM will be pushing is the ability in Modeler 6.2 ‘Design to Deploy’.

WebSphere Process Server V6.2 enables a new direct deploy scenario, where users of WebSphere Business Modeler can directly deploy modules into the WebSphere Process Server runtime.

I believe this feature is more for testing, but I really have to play with it more. Without more investigation, deploying an application from a business analyst perspective into a technical server like WebSphere Process Server sounds weird. As more people use Modeler to deploy, will it just become WebSphere Integration Developer, just with an even more candy UI?

Solution view

Woo hoo! It’s about time. You can finally have some kind of visualization of your entire solution and the interactions between modules! No more visio (or if you are like me, MS Paint) diagrams and manually ensuring the interactions are correct.

Process editor Improvements

There is finally an ability to use Business Object maps directly in a BPEL. No more visual snippets!

Human task editor Improvements

the option to bind a participating human task to the process lifecycle

Finally, your human tasks can terminate if your instantiating business process dies. And finally,there’s an editor for those insane BPEL/Human Task variables.

Assembly editor enhancements

Don’t you worry, it’s been made prettier More importantly, the WebSphere Web Services Features Pack is now supported. It’s also got policy set support for all you guys that want to do your WSReliableMessaging.

You can define new policy sets through the administrative console, export into an XML file, then import into WebSphere Integration Developer.

Blech.

Mediation Flow Editor

Performance is improved by eliminating the hop between modules, improving efficiency

Hmm, I wonder what this actually means? I know that the SCA.SYSTEM bus creates an ungodly amount of queues for an application, I wonder if someone finally looked at this to minimize them?

Support for Services Gateway pattern

This is very interesting. It appears that WID v6.2 now is starting to support patterns and wizards to create these patterns.

Other editor enhancements

Versioning! You can now version all components in your assembly diagram.

I also see a ton of new features added to the Integration Test Client that sound very exciting.

Conclusion

All-in-all, it looks like a good release on paper. Of course, what really matters is how it behaves when you are using it. The progression of WebSphere Integration Developer from 6.0 -> 6.0.1 -> 6.0.2 -> 6.1 -> 6.2 has been very good so I have faith that this will be another large step in the right direction.

Related Posts

• WebSphere Integration Developer & WebSphere Process Server v6.1.2 released
• What’s new in WebSphere Integration Developer V6.1.2
• Whats new in WID/WPS v6.1
• Versioning business processes and human tasks in WebSphere Process Server
• IBM Redbooks: WebSphere Process Server and WebSphere Integration Developer

From DeveloperWorks, WebSphere Process Server invocation styles

As you author applications in WebSphere Integration Developer, you may find it necessary to set or verify the invocation style that one component will use to call another. Users are often surprised to find that this is not as easy a task as it may seem. This article explains how to determine which invocation style will be used at runtime, based on characteristics of your application.

Another article from my former colleagues (they’re been busy!). This one explains what interaction style an invocation will use between two component. This is important to understand for error handling and transaction boundary issues. Another must read.

Related Posts

• Use ARM to monitor SCA invocations in IBM WebSphere Process Server
• BPEL: Beware the use of nested loops in a short running process
• DataPower – Proxy & Co-Processing
• IBM Redbooks: WebSphere Process Server and WebSphere Integration Developer
• WebSphere Process Server operational architecture: Part 1: Base architecture and infrastructure components

 According to the tech-note, you have to follow some manual steps to get the debugger to work on a server that has security enabled:

http://www-01.ibm.com/support/docview.wss?uid=swg24015747v

Related Posts

• WebSphere Process Server Failed Event Manager: “The Recovery Sub-system is disabled.”
• Avoid the WebSphere Integration Developer Debugger
• Introducting the SCA HTTP Binding
• Securing JMS connections to WebSphere Enterprise Service Bus V6.1
• Variable Substitution in WSAdmin: Variables in braces are treated as constants

The scenario

I have an MQ Request queue that takes multiple types of business objects as input. The MQ request queue consumer evaluates the type of the message and routes it to the appropriate downstream service. When the response comes back from the downstream system, it is placed into the single MQ Response queue. Therefore, the MQ Response Queue contains multiple types of response messages.

In my scenario, I need to invoke two services. I do this by placing two distinct message requests onto the request queue: Service invocation 1 and Service Invocation 2.

I create a BPEL process to invoke the two services in serial.

The Anti-Pattern

I create two MQ Imports and two WSDL files representing each operation. One for the invocation of service 1 and a second for the invocation of service 2. I configure each MQ Import to have it’s own unique listener port but I have them use the same queue manager and same physical request and response queues.

The Problem Manifests

What I see is that sometimes, the response message from my invocation of service 2 is picked up by the listener port for service 1. Service 2 never gets the response values and service 1 throws an exception. Eventually the listener ports will shut themselves down from the errors.

Why?

By creating two MQ Imports, I have now created two independent listener ports that are listening for messages on the same queue. They’re in a race condition about which one will get notified about the arrival of a message.

The MQ Import Pattern

Stick with a single listener port for your set of request/response queues.  In order to use a single listener port, you need to have a single MQ Import. You could do this by creating a single WSDL for your two operations to the request queue, or I believe you could add multiple wsdl interfaces to a single MQ Import.

Related Posts

• WSDL Anti-Pattern: The ‘Single XML String’ Service
• Asynchronous SCA One-Way Operations And How To Recover
• Whats new in WID/WPS v6.1
• WSDL Anti-Pattern: xsd:Any and xsd:AnyType To Encapsulate Future Changes
• WebSphere Default Messaging (SIBus) and WebService Error Handling

From DeveloperWorks, Error handling in WebSphere Process Server, Part 1: Developing an error handling strategy

With the emergence of service oriented solutions, we’ve seen a sharp rise in developer productivity. Developers are empowered with a new found freedom of service construction and reuse. However, with this freedom comes an increased exposure to inconsistent service definitions. These inconsistencies expose weaknesses in error handling and system recovery across the solution. Along with the proper governance controls, IT organizations need to define and enforce the proper error handling strategies tailored for solution recovery. Part 1 of this article series introduces the topic of error handling strategies and highlights key concepts and objectives for developing a strategy

This is an article written by my former colleagues at IBM. It goes into depth about the part of your process that you likely left until the last moment: What to do when something goes wrong. I recommend it as required reading for any WebSphere Integration Developer user.

Related Posts

• WebSphere Process Server: Repairing Business Processes
• WebSphere Default Messaging (SIBus) and WebService Error Handling
• Handling unmodeled faults within WebSphere Process Server V6.1
• Asynchronous replication of WebSphere Process Server and WebSphere Enterprise Service Bus for disaster recovery environments
• WebSphere Integration Developer – Namespaces Cannot Span Projects

From DeveloperWorks, Managing tasks and business processes using WebSphere Business Space

Learn how to create WebSphere BPM V6.1.2 Business Space dashboards using the run-time artifacts from the WebSphere BPM V6.1.1 Clips and Tacks tutorial. You'll create a business space to manage the tasks and business forms input, run some processes that use forms, and finally create a business space you can use to monitor the process and tasks.

An example of what a 'Business Space' is.

Related Posts

• Managing tasks and business processes using WebSphere Business Space
• Getting Started with IBM WebSphere Business Services Fabric V6.1
• Versioning business processes and human tasks in WebSphere Process Server
• WebSphere Business Process Management V6.1.2 Production Topologies
• Use ARM to monitor SCA invocations in IBM WebSphere Process Server

From DeveloperWorks, Versioning business processes and human tasks in WebSphere Process Server

This article shows you how to build versions of business processes and human tasks that are based on best practices in IBM WebSphere Integration Developer V6.1 and WebSphere Process Server V6.1.

Versioning of a Business Process is the most important feature of the BPEL Container, and likely the feature you know the least about. The choices you make in how to invoke parent-child processes define the way they behave when the BPEL templates are updated. If you wire them together in the assembly editor, then the two specific versions of the template are bound together forever. Parent process A v1.0 will always use Child Process B v1.0. If child B 2.0 is deployed, A will continue to use 1.0. Not exactly the behavior you would expect. This article defines the way that the BPEL engine resolves versions and it should be required reading.

Related Posts

• What’s new in WebSphere Integration Developer V6.2
• BPEL Business Process Versioning – Infocenter Link
• WebSphere Process Server Discussions
• Handling unmodeled faults within WebSphere Process Server V6.1
• WebSphere Process Server: Repairing Business Processes

From DeveloperWorks, Seamless access to SAP services using IBM WebSphere integration tools

This article shows you how to design, develop, configure, deploy, and test an end-to-end purchase order scenario using WebSphere Process Server, WebSphere Adapters, and SAP. You also learn how to create applications that Web enable SAP services and help in the analysis, design, and implementation of similar integration applications.

A nice scenario developed by IBM to show off how to use the WebSphere Adapter for SAP, WebSphere Process Server and WebSphere Integration Developer.

Related Posts

• Getting Started with WebSphere Process Server and WebSphere Enterprise Service Bus Parts 1 & 2
• Web services with SOAP/JMS in IBM WebSphere Process Server
• Whats new in WID/WPS v6.1
• Use ARM to monitor SCA invocations in IBM WebSphere Process Server
• IBM Redbooks: WebSphere Process Server and WebSphere Integration Developer

Geez, I don’t know how I missed this one.  ILOG is a business rules engine that can already integrate with WebSphere Process Server so this acquisition makes sense. It’s better than the one bundled with the product and used by more companies.

Anyway, I’ll defer to the bloggers of the world who have more industry insight than I to explain this acquisitions relevance:

•  James Taylor at SmartEnoughSystems
• Tony Baer at OnStrategies Perspectives

Related Posts

• Updated – Impact 2008: Bloggers in Attendance
• Impact 2008: Twitter HashTags.org #impact2008
• Automatic Build Solution for WebSphere Integration Developer
• Oracle SOA Suite 11g – Hello Competition!
• IBM Partners Blocked from Rational Conference