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

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 DeveloperWorks, Securing JMS connections to WebSphere Enterprise Service Bus V6.1

Security is an integral part of SOA, and since WebSphere ESB is at the heart of many SOA solutions, the security of a WebSphere ESB server and its transports is vital to the enterprise systems that use it. Messaging, such as the JMS implementation provided by WebSphere ESB, is particularly important for business applications because of its reliability, performance, and asynchronous nature. This article shows you how to implement security with an example using WebSphere ESB V6.1 and a J2EE client container application communicating via JMS messaging.

Securing the messaging engine is a task that most customers need to do but documentation of all the steps was hard to come by. This article puts them to light to make the entire process easier.

Related Posts

• WebSphere Application Server: High Availability to JMS Clients?
• WebSphere Integration Developer & WebSphere Process Server v6.1.2 released
• Web services with SOAP/JMS in IBM WebSphere Process Server
• Make SOA real with IBM WebSphere Enterprise Service Bus and IBM WebSphere DataPower SOA Appliances
• WebSphere Enterprise Service Bus – Mediation Flow Component: No Refactoring for WSDL Faults

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

• 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
• WebSphere Integration Developer & WebSphere Process Server v6.1.2 released

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

If you are looking at WebSphere Process Server Disaster Recovery, you should know that the UUID’s that uniquely identify a server in both the Messaging Engine Database and the transaction log are unique for that particular installation. Running the equivalent installation commands on the restored system will not generate a server with the same id. This implies that you need to ensure your server installation (and profile) itself is backed up should restoration be needed in the future.

Also, as far as I know, there is no way to manually edit the UUID of a server. If you don’t keep a backup of the install, disaster recovery will be more difficult than expected and you may end up losing transactions.

Related Posts

• WebSphere Process Server Failed Event Manager: “The Recovery Sub-system is disabled.”
• Asynchronous replication of WebSphere Process Server and WebSphere Enterprise Service Bus for disaster recovery environments
• Uninstalling or updating the WebSphere V6.1 test environment using Installation Manager
• IBM Installation Manager Tip: Don’t “Save Files For Rollback”
• Migration to WebSphere Process Server and WebSphere Enterprise Bus 6.2 – Mandatory reading