If you plan on using datapower to write a modified value to the AppIdentity MQMD header, ensure that your Put Message Options on your destination are correct.

You want to use “2052″ which represents “MQPMO_SET_CONTEXT_ALL” along with “MQPMO_NO_SYNCPOINT”. You need to tell MQ that it should use the message headers from the written message. In Datapower, (for some unknown reason) in the URL Builder for MQ, this is the “User Identity” on/off toggle.

‘No Syncpoint’ tells MQ that this is a single message transaction that isn’t dependent on the writing on subsequent messages. This of it like “I want all 5 messages I write to the queue to be committed all together or none at all”.

If you don’t set your Put Message Options correctly, you won’t see your modified headers written onto the message in the Queue.

Related Posts

• Adding JMS or MQ/JMS Custom Header Attributes
• JMS Function Selectors & Method Bindings
• SCA, BPEL, Websphere Adapter for JDBC and Transactionality
• WSDL Anti-Pattern: xsd:Any and xsd:AnyType To Encapsulate Future Changes
• JDBC Adapter Export with events that comprise multiple rows

If you are using DataPower to pull messages from MQ which contains persistent messages, do yourself a favor and set the ‘Units of Work’ on the QM in DP to 1.

This will enable DataPower to use SyncPoints from MQ and allow you transactionality on a per-message basis.

Without this setting, you can get very strange behavior when you want to discard a message. You could see the entire batch of messages re-appear on your input queue.

My theory is that MQ implicitly creates a syncpoint when DataPower connects and one end it disconnects. If it doesn’t get confirmation that all the messages were successfully processed, then the only recourse is for the QM to rollback the transaction, causing all the messages datapower successfully processed to return to the queue.

Related Posts

• Issues that I encountered while creating my DataPower to MQ Demo
• “What’s New in WebSphere DataPower v3.6.1″
• DataPower Extension Functions
• WB552: Random DataPower Thoughts Part 4
• IBM WebSphere DataPower SOA Appliances Part I: Overview and Getting Started

In WTX, I have a COBOL EBCDIC input with a bunch of filler fields. The Input Type Tree was created by the Cobol Copybook Importer.

I had an ‘invalid input’ occur when I submitted a cobol message to my WTX map. The map failed on a filler item where the input wasn’t spaces, but NULL.

This is apparently valid, but by default, the WTX COBOL Importer will create thsi field of type CHARACTER which the null’s will cause to fail.

I switched the type of the item to ‘BINARY’ (because who cares about filler data) and got an error

“failed item presentation test for TYPE”

Looking into the documentation, I had to ensure that a binary type had a constant value. By default, WTX creates the item with a 0-XX type for the max and min. I changed the value of the min to the max and everything worked ok.

Related Posts

I was using WTX 8.3 to build a type tree off a COBOL copybook. When I then attempted to run a map based on the tree I got the error “One or More Inputs was Invalid”.

My Input data was in EBCDIC format and RFHUtil was my saviour. It was able to display the copybook and the data side-by-side so I could see what values should be where. (Sidenote: Good EBCDIC editor is VEDIT ).

I turned on Map Tracing via the not-well-defined ‘Map Settings’ and InputContentTrace and saw that my data wasn’t matching up with the items in the input. It was trying to put data contained in byte 1000 into an object defined at byte 1050.

Then I noticed that the number of bytes that my imported data in WTX was ‘off’ was the exact same number of bytes as a group.

I opened the Generated type tree and sure enough, a group was missing. Once I added it back as a Child Component in the Root ‘Record’ group (along with a few other missing groups) my input successfully validated.

Now, I don’t know a ton about the structure of cobol copybook or what could have caused it, but if you are in WTX and don’t see your input data lining up properly it’s probably because your WTX Root Object is missing them.

Related Posts

• WebSphere Process Server and RPC/Literal Web Services: Beware Messages defined by ‘type’ instead of ‘element’.
• WebSphere Integration Developer – Namespaces Cannot Span Projects
• MQ Import Anti-Pattern: Multiple MQ Imports connecting to single pair of physical request/response queues
• Interop between BOXMLSerializer and JMSDataBindingImplXML
• Exploring The Contents of a WID Module Project

Just had a problem where a WSDL file that was uploaded to the DataPower device did not show up in the local:// drop down for selection.

Upon further inspection, we found that there was whitespace before the
<? xml .. ?> tag and whitespace before the <wsdl:definitions...> tag.

Once this extra whitespace was removed, the WSDL appeared in the drop downs and worked fine.

Related Posts

• WebSphere Process Server and RPC/Literal Web Services: Beware Messages defined by ‘type’ instead of ‘element’.
• ProcessTemplateNotFoundException: CWWBA0008E: Process template ‘myProcess, -valid_from_date-’ is not found
• UPDATE: WebSphere Adapter for JDBC: Superfluous RecordNotFound Exceptions
• WebSphere Process Server and an RPC/Literal WSDL : Trench War
• IBM TechNote: Content and maintenance of the wstemp directory for WebSphere Process Server V6

I’ve posted a question to the Datapower external newsgroup asking about how Siteminder can be used to authenticate users. The documentation is pretty thin on the subject.

https://www.ibm.com/developerworks/forums/thread.jspa?threadID=315235

Basically, i have a username and password that I’d like Siteminder to authenticate. I’m sure that Datapower invokes a URL and posts the information to the given URI. It then inspects the response cookie and determines if Siteminder was successful.

The usual Siteminder usage pattern is for someone to hit a page with a web browser and then be issued a challenge.. So it’s possible Siteminder requires this step into order to validate.

Related Posts

• Business Object Maps and ‘Required’ Attributes
• Venting some WebSphere Integration Developer Steam
• The VETO SOA Pattern
• Problem Determination and WebSphere Integration Developer
• Datapower: Missing WSDLs from local: File System – Whitespace Issue

From Developerworks, Migrating to WebSphere Process Server V6.2 This tutorial shows you how to migrate WebSphere Process Server configuration data, application data, and databases from V6.1.2.3 to V6.2.0.1. The tutorial also describes the sub-tasks involved and shows you how to use migration log files for troubleshooting. Everyone's favourite task: Migrating between versions.

Related Posts

• Migration to WebSphere Process Server and WebSphere Enterprise Bus 6.2 – Mandatory reading
• Versioning business processes and human tasks in WebSphere Process Server
• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.1
• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.1
• WebSphere InterChange Server migration to WebSphere Process Server

If you are planning on upgrading your WebSphere Servers to a later fixpack level, be sure to start with the Deployment Manager. If you do not, your Deployment Manager will not be able to contact your ‘future level’ node agent.

“Server cannot be started because the node agent for server Node1 on node x is not active”

Attempting to call syncNode to the deployment manager will result in:

ADMU0127E: The version of the Deployment Manager is earlier than that of this node. Deployment Manager version earlier than that of a node is an unsupported configuration.Upgrade the Deployment Manager to the same or later version as that of the node.

Related Posts

• Migration to WebSphere Process Server and WebSphere Enterprise Bus 6.2 – Mandatory reading
• Uninstalling or updating the WebSphere V6.1 test environment using Installation Manager
• IBM Software Support Lifecycle – General Availability, End Of Marketing, End of Support Dates
• IBM Certification Tests
• BPEL Business Process Versioning – Infocenter Link

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!

The infocenter has a great article about how to use “Industry Standard Schemas” with WebSphere Process Server.

This is required reading.

You will need to know about the Sequence object when dealing with

• xsd:any
• xsd:anyType
• xsd:anySimpleType
• xsd:anyAttribute

This used to be completely undocumented and now, the documentation is actually really good. Enjoy your undefined datatype.

I still stick with the rule that undefined types are the scourge of good integration.

Related Posts

• WSDL Anti-Pattern: xsd:Any and xsd:AnyType To Encapsulate Future Changes
• Oracle SOA Suite 11g – Hello Competition!
• WebSphere Process Server and RPC/Literal Web Services: Beware Messages defined by ‘type’ instead of ‘element’.
• Pre-review: WebSphere Business Integration Primer
• IBM Buys ILOG, a Business Rules Engine

The Visual Configuration Explorer

When configuration problems occur in a complex software environment, you can spend a lot of time hunting for subtle changes that might have introduced errors. The new Visual Configuration Explorer tool, which runs as a plug-in to the IBM Support Assistant, simplifies configuration troubleshooting by letting you visualize, explore, and analyze the configurations of various software stacks offline.

You can also use this plugin to compare two configurations and look for changes. Very good if your server ‘magically’ breaks one day or you are trying to track down a change from a while ago.

Related Posts

• IBM Client Application For JMS – Put JMS messages in queues
• Perficient Booth at the IBM WebSphere SOA Connectivity Briefing in Toronto
• WebSphere Application Server: Non-Deterministic Error when configuring Default Messaging Activation Specs
• IBM Software Support Lifecycle – General Availability, End Of Marketing, End of Support Dates
• What’s new in WebSphere Application Server V7

AlbeesOnline has posted a great article showing how difficult integration projects can be when you need to work with teams spread across an organization. A relatively straightforward project turns into a Frankenstein of text files and workarounds. It also shows the reason why projects have meetings that involve 20-30 people five times a week, you miss a department and they’ll pop up out of nowhere and tell you what you are doing is impossible.

I have to admit that I die a little inside when I hear of projects that have to switch from clean-elegant solutions to crazily complicated ones to work around corporate policies. The customer gets the final solution and wonders why the heck they bothered with an integration platform in the first place. It’s depressing.

Related Posts

• Problem Determination and WebSphere Integration Developer
• WebSphere Process Serevr v6.0.2.4 JVM Crashing on Windows with Illegal Operation
• Venting some WebSphere Integration Developer Steam
• Does Commerical Enterprise Software Suck?
• WebSphere Adapter for FTP – Missing Information in User Guide

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!

IBM Redbooks presents: Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.2 & Best Practices

Draft Redbook, last updated: Wed, 18 Mar 2009

- Migration concepts, planning and best practices
- New Workspace migration wizard
- Migration scenarios utilizing Business Space interface

In this IBM Redbooks publication, we discuss the concepts, planning, and migration paths, that you must understand before any attempt to migrate the source artifacts created using IBM WebSphere Studio Application Developer Integration Edition 5.1 product, to the IBM WebSphere Integration Developer 6.2.

I pray for you.

Related Posts

• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.1
• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.1
• WebSphere InterChange Server migration to WebSphere Process Server
• IBM Redbooks: WebSphere Process Server and WebSphere Integration Developer
• Migration to WebSphere Process Server and WebSphere Enterprise Bus 6.2 – Mandatory reading

From Devleoperworks, Top 10 FAQs on core group bridges

Here are the most commonly asked questions about the IBM WebSphere Application Server’s core group bridge service, introduced in Version 6.0, which is used to enable high availability communication between core groups.

The top 10 questions AFTER "What is heck is a core group bridge?"

Related Posts

• WebSphere Application Server 7.0 Feature Pack for Service Component Architecture (SCA)
• System administration for WebSphere Application Server V7: Part 1 — An overview of administrative enhancements
• WebSphere Application Server and The Spring Framework
• IBM Software Support Lifecycle – General Availability, End Of Marketing, End of Support Dates
• Importing/Exporting a WebSphere Profile – The .CAR file