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

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

• 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

From IBM Redbooks: WebSphere Application Server V7: Concepts, Planning and Design

Redbook, published: Fri, 20 Feb 2009

- Discusses end-to-end planning for WebSphere implementations
- Defines WebSphere concepts and best practices
- Addresses distributed and z/OS platforms

This IBM® Redbooks® publication discusses the concepts, planning, and design of WebSphere® Application Server V7.0 environments.

This redbook weighs in at a whopping 522 pages of WebSphere Application Server 7.0 goodness. A must read (or atleast skim )

Related Posts

• IBM Software Support Lifecycle – General Availability, End Of Marketing, End of Support Dates
• System administration for WebSphere Application Server V7: Part 1 — An overview of administrative enhancements
• Follow up to Profile Creation Fails on WebSphere 6.1.0.19: Java Juristiction Policy Files
• Using Spring and Hibernate with WebSphere Application Server
• WebSphere Application Server 7.0 Feature Pack for Service Component Architecture (SCA)

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

If you are installing the Business Flow Manager, ensure that you are enabling the Rest API with a proper context root. The REST API is used by some widgets inside of the Business Process Choreographer and if you do not configure the URL properly, you will get errors when trying using the process state view.

• WebSphere Process Server Failed Event Manager: “The Recovery Sub-system is disabled.”
• WB552: Random DataPower Thoughts Part 3
• Uninstalling or updating the WebSphere V6.1 test environment using Installation Manager
• ProcessTemplateNotFoundException: CWWBA0008E: Process template ‘myProcess, -valid_from_date-’ is not found
• WebSphere Integration Developer & WebSphere Process Server v6.1.2 released

From Developerworks, Repairing processes with WebSphere Process Server

WebSphere Process Server V6.1.2 supports manual repair and change of control flow logic. This article describes these repair features, provides useful tips, and identifies potential pitfalls when applying them. You’ll learn how to repair processes and dynamically react to cases in which modeled fault handling and automated recovery mechanisms are not useful in solving the situation.

This is an unbelievably complete article about BPEL processes and what happens when an error occurs. It also goes into what you need to consider at development time for error handling as well as your options once something has gone wrong.

A must read for anyone uses BPEL in an enterprise 24/7 solution and can’t just terminate business processes when something goes wrong.

Related Posts

• Error Handling in WebSphere Process Server: Developing an Error Handling Strategy
• WebSphere Process Server Endurance
• Handling unmodeled faults within WebSphere Process Server V6.1
• Versioning business processes and human tasks in WebSphere Process Server
• Asynchronous replication of WebSphere Process Server and WebSphere Enterprise Service Bus for disaster recovery environments

Just a quick FYI to those of you who are doomed to write WSAdmin scripts, if you use variable names and enclose them in curly braces ‘{‘, then commands will treat it as a constant string and your variables will not resolve to their values.

$AdminTask blah {-file $VariableFileName}

Will cause and error that the physical file “$VariableFileName” could not be found.

To resolve the issue use the subst or list command:

$AdminTask blah [subst {-file $VariableFileName}]

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

Related Posts

• Problem Determination and WebSphere Integration Developer
• Exploring The Contents of a WID Module Project
• WebSphere Process Server Failed Event Manager: “The Recovery Sub-system is disabled.”
• Updates required for WebSphere Integration Developer debugger to work when security is enabled
• WebSphere Integration Developer – Namespaces Cannot Span Projects

If you have a 6.1.x environment and are thinking about upgrading to 6.2, then you must read:

Migration to WebSphere Process Server and WebSphere Enterprise Bus 6.2 – Mandatory reading

WebSphere Process Server and WebSphere Enterprise Service Bus version 6.2 provide major functional improvements over previous versions, and in order to take advantage of these new features while preserving your existing applications and profile configuration you must migrate to version 6.2 of the product. WebSphere Process Server 6.2 is not a refresh pack or an upgrade version. Version 6.2 must be installed alongside the older version of the product. To facilitate your migration process, WebSphere Process Server 6.2 provides improved version-to-version migration utilities to help you migrate your existing applications and profile configuration information.

Related Posts

• Migrating to WebSphere Process Server V6.2
• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.2 & Best Practices
• Upgrading WebSphere Application Servers – Update the Deployment Manager First!
• Versioning business processes and human tasks in WebSphere Process Server
• BPEL Business Process Versioning – Infocenter Link

When looking in the top right corner of the Failed Event Manager, the following error is displayed:

The Recovery sub-system is disabled. Enable the Recovery sub-system in order to work with failed events.

You get directed to the following tech-note:

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

which states that there is a problem with the Failed Event Manager MBean in your server/cluster.

Interestingly, when the failed event manager EAR is installed manually (or via script) in 6.0.2.x the MBeans are not automatically installed for you. You have to go back to your server configuration and configure them manually. When you create a profile using the profile creation wizard, everything is fine.

Related Posts

• WebSphere Process Server Disaster Recovery: UUIDs are unique to an install
• Asynchronous SCA One-Way Operations And How To Recover
• Event Sequencing Message Locking – Resolution!
• WebSphere Adapter for FTP – Missing Information in User Guide
• Techniques for Managing Large WebSphere Installations

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

In the admin console, when trying to stop a template contained in an ear so that the ear could be updated, the following exception occurred:

com.ibm.bpe.api.ProcessTemplateNotFoundException:
CWWBA0008E: Process Template
'MyProcess, Web 2008-10-10 12:32:22.00' 
is not found.

It’s unknown how many times that the EAR was attempted to be stopped or what happened on the initial removal from the server.

To investigate the ProcessTemplateNotFoundException, I looked at the BPEDB’s PROCESS_TEMPLATE_B_T table. This table holds the persisted information in the database for process templates. A simple select * from PROCESS_TEMPLATE_B_T should give a list.

When I ran this query, I found that the table was empty. So the database has no records of any process templates. The weird part is that I can still see the templates in the ‘Business Processes’ tab from the admin console. I’m not sure how this information is populated. Does it come from the EAR file itself or is it generated via BPE API calls? If it’s the latter, I’m even more confused why the BPE API would return a list of templates while the database was empty.

I removed the ear from the admin console and it uninstalled properly. I then installed the EAR and looked at the PROCESS_TEMPLATE_B_T table and it was populated properly.

As far as I know, this was a one-off incident. There is a theory that something occured when ‘Update’ of an existing EAR was selected and the updated EAR contained additional templates. But it’s just a theory.

I thought I’d write this up just in-case anyone else out there runs into this issue. The BPEDB should be the ‘gold standard’ as to the state of your business processes. If it gets out of sync with the admin console, weird errors can result.

Related Posts

• How not to migrate your server – Internal Database Copying
• WebSphere Adapter for JDBC: Superfluous RecordNotFound Exceptions
• WebSphere Admin Console SRVE0190E: FileNotFound Errors when clicking certain hyperlinks
• JDBC Adapter Export with events that comprise multiple rows
• Tip: WebSphere Process Server – Do not delete the ‘tranlog’ on a production server