From IBM Redbooks, Integrating WebSphere Service Registry and Repository with WebSphere Process Server and WebSphere ESB This IBM® Redpapers™ publication describes how you can integrate IBM WebSphere® Service Registry and Repository with IBM WebSphere Enterprise Service Bus and IBM WebSphere Process Server to create a flexible and robust infrastructure for the execution of SOA solutions.

Related Posts

• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.2 & Best Practices
• Securing JMS connections to WebSphere Enterprise Service Bus V6.1
• Fifteen common Websphere Partner Gateway problems and how to solve them

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, Fifteen common Websphere Partner Gateway problems and how to solve them

Websphere Partner Gateway enables companies to connect large groups of trading partners to their businesses and extend internal integration outside the enterprise. This article discusses 15 common problems that can occur during Partner Gateway operations and their solutions.

While I don't use WebSphere Partner Gateway, I really like this article for the way that it presents a single location to solve a bunch of common problems.

Related Posts

• IBM Partners Blocked from Rational Conference
• Impact 2008: SOA Jam – “ESB: Too Many Products, Skill Spread too thin”
• Impact 2008: SOA Jam – “Foster an External Community for Practitioners”
• Securing JMS connections to WebSphere Enterprise Service Bus V6.1
• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.2 & Best Practices

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