From DeveloperWorks, Using Spring and Hibernate with WebSphere Application Server

If you're considering using Spring or Hibernate with IBM WebSphere Application Server, this article explains how to configure these frameworks for various scenarios with WebSphere Application Server. This article is not an exhaustive review of either framework, but a critical reference to help you successfully implement such scenarios. (Updated for Spring Framework 2.5 and WebSphere Application Server V7.) (IBM WebSphere Developer Technical Journal)

Related Posts

• WebSphere Application Server and The Spring Framework
• Still Springing Along
• Adding pre-built JAR files to your EAR in Rational Application Developer
• Do not use forward slashes in SIBus Destination names with JMS
• WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB

When defining the usage of an authentication alias in a resource in the administration console of WebSphere Application Server, there are two places the data can be specified:

1. Component Managed Authentication
2. Container Managed Authentication

Component Managed Authentication is used when the resource configured in the EJB’s deployment descriptor res-auth property is set to ‘Application’.

Container Managed Authentication is used when the resource configured in the EJB’s deployment descriptor res-auth property is set to ‘Container’.

The WebSphere v6 Administration Console notes that Container managed is deprecated and that component should be used.

EDIT #1: Thanks to David Currie for pointing out that it’s actually the specification of the authentication alias directly in the resource that is deprecated.

You should verify the res-auth setting of your jndi resources if you find that you configured an authentication aliasbut recieve an exception about null username at runtime.

Related Posts

• WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB
• IBM APAR PK49507: PROFILE RECREATION Required!
• WebSphere Application Server: Non-Deterministic Error when configuring Default Messaging Activation Specs
• Adding pre-built JAR files to your EAR in Rational Application Developer
• WebSphere Admin Console SRVE0190E: FileNotFound Errors when clicking certain hyperlinks

From DeveloperWorks, Establish a policy-driven SOA using WebSphere Service Registry and Repository and WebSphere ESB

The WS-Policy specification provides a simple language for expressing policies supported by Web services. IBM WebSphere Service Registry and Repository supports loading, changing, and retrieving policy documents, and also supports using policy attachments to link a given policy with a service. This can then be used by a run time component, like an Enterprise Service Bus, to retrieve defined policies for a particular service or operation and act accordingly. This article shows how you can utilize standard WS-Policy documents stored in a registry to impact run time behavior in an ESB -- and then change that behavior on the fly with no code changes or redeployment. (IBM WebSphere Developer Technical Journal)

An example of invoking WSRR API from a WebSphere Enterprise Service Bus medation module to use WS-Policy.

Related Posts

• Using DataPower SOA Appliances to query WebSphere Service Registry and Repository
• Create classification taxonomies programmatically in IBM WebSphere Service Registry and Repository
• Hello World: WebSphere Service Registry and Repository
• WebSphere Business Services Fabric V6.1.2: Integrating with WebSphere Service Registry and Repository
• WebSphere Business Services Fabric, Part 2: Extending the ontology models

One of the biggest pain points in any IBM product are the non-sensical error messages that are generated by the products when something goes wrong. The exception itself usually doesn’t provide much of a clue as to the root cause of the issue. To proceed you either need to be an expert in reading stack traces, you open a PMR with IBM (a lengthy process) or you pop the exception message into google and hope that you hit something (like say the awesome danzrobok.com ).

What I’d like to see is IBM take control of this information about explaining in greater detail how an exception can occur and likely resolutions. I’d also take this one step farther and take this information from the infocenter (where it starts out as a shell) and populate it in a wiki format. The wiki would allow people who experienced the exception to describe how it occured, attach project interchange files and create discussions based around specific errors.

When resolutions are discovered, they can be updated directly into this central location for information about this exception, aiding future users. This solution would decrease the number of support calls that IBM recieves and it empowers the users of the product to resolve their own issues. Win - Win.

Related Posts

• WB552: Random DataPower Thoughts Part 6
• Venting some WebSphere Integration Developer Steam
• Problem Determination and WebSphere Integration Developer
• IBM APAR PK49507: PROFILE RECREATION Required!
• WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB

From DeveloperWorks, Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.1

Draft Redbook, last updated: Mon, 6 Oct 2008 - Migration concepts, planning and best practices - Migration tools and scripting - Migration end to end scenarios In this IBM Redbooks publication, we discuss the concepts, planning, differences 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.1.

Related Posts

• Migrating WebSphere Business Integration Server Foundation to WebSphere Process Server V6.1
• WebSphere InterChange Server migration to WebSphere Process Server
• WebSphere MQ Workflow Transition to WebSphere Process Server
• IBM Redbooks: WebSphere Process Server and WebSphere Integration Developer
• Tip: WebSphere Process Server - Do not delete the ‘tranlog’ on a production server

Should you find that you have some links in your WebSphere Administration console that generate an error in the following format:

com.ibm.ws.webcontainer.webapp.WebAppErrorReport:
SRVE0190E: File not found: /xxxxxxxxxxx.content.main
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java)
at com.ibm.ws.webcontainer.servlet.FilterProxyServlet.dispatch(FilterProxyServlet.java)
at com.ibm.ws.webcontainer.servlet.FilterProxyServlet.service(FilterProxyServlet.java)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java(Compiled Code))
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java(Compiled Code))
t com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java(Compiled Code))
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java(Compiled Code))
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.invokeFilters(WebExtensionProcessor.java)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java)

It appears that the admin console couldn’t find the servlet that should be used to display the page.

You likely have a corrupted Admin console registry. You can run

iscdeploy -restore

from the ‘bin’ directory of the profile in question. This will cause WebSphere Application Server to reinstall the admin console.

The relevant information from an IBM technote can be found here.

Related Posts

• WebSphere Adapter for JDBC Export - ‘InvalidVerbException’
• WebSphere Adapter for JDBC: SetObjectKeys NullPointer Exception
• The WebSphere Exception Trace: Deconstructed
• Make SOA real with IBM WebSphere Enterprise Service Bus and IBM WebSphere DataPower SOA Appliances
• WebSphere Process Server’s default log size: Very Small

From DeveloperWorks, Asynchronous replication of WebSphere Process Server and WebSphere Enterprise Service Bus for disaster recovery environments

This article describes an environment that is based on using a disk replication system in asynchronous mode. You can include this environment in a disaster recovery plan that includes a secondary data center using IBM WebSphere Process Server or WebSphere Enterprise Service Bus.

A serious concern if you are using WebSphere Process Server for mission critical-must-continue-to-run applications. It deals with the question of how to implement a disaster recovery solution that spans physical remote sites.

Related Posts

• Asynchronous SCA One-Way Operations And How To Recover
• Getting Started with WebSphere Process Server and WebSphere Enterprise Service Bus Parts 1 & 2
• Getting Started with WebSphere Process Server and WebSphere Enterprise Service Bus Part 3: Runtime
• Goals
• What’s new in IBM WebSphere Enterprise Service Bus V6.1

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

• 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
• Advanced techniques and patterns for business process client development

From DeveloperWorks, What's new in WebSphere Application Server V7

IBM WebSphere Application Server V7 has powerful new features and dramatic enhancements to help you achieve heightened productivity, stronger security, tighter integration, and simplified administration. Find out about some of the new key features that enable this new release to provide a flexible and reliable foundation for your service-oriented architecture.

Related Posts

• What’s new in WebSphere Process Server V6.1.2
• What’s new in IBM WebSphere Enterprise Service Bus V6.1
• What’s new in WebSphere Integration Developer V6.1.2
• WebSphere Application Server: Component vs Container Managed Authentication Alias
• WebSphere Application Server 7.0 Feature Pack for Service Component Architecture (SCA)

This session was delivered by Martin Wildberger, IBM VP and Director of the Toronto Software Lab.

This session was attended by around 70 people, a pretty large turnout for one of these all-day events.

Martin asked the crowd if they were from the line of business side or the IT side. I didn’t see a single hand raised for the LOB, so as expected most people in the crowd are interested in SOA from an IT perspective.

There was a slide about comments from Gartner regarding “Don’t postpone SOA…. Reprioritize your road map”

1. “… [prioritize] projects that will turn an ROI faster”
2. “…address lower-cost projects sooner”
3. “Choose SOA projects were reuse of established systems is prevalent”

This is a great heuristic to determine SOA project candidacy and prioritization.

Martin went through a set of slides about the success of SOA at various companies and the capabilities that can be leveraged to increase ROI.

WebSphere sMash was also brought up as an integral product to the story.

Also, this is a slide that I’ve seen so many times, I wish someone would redesign it in a new color:

Avoid the notion of explaining SOA in terms of IT. Explain it in terms of business value, agility.

Related Posts

• ICTY Toronto 2008: Lower Operational Costs and Improving Quality of Service Using Application Virtualization
• Impact 2008: SOA Jam Day 3
• Impact 2008: Impressions of Day 2
• Impact 2008: SOA Jam - “ESB: Too Many Products, Skill Spread too thin”
• Impact 2008: SOA Jam - “Foster an External Community for Practitioners”

From DeveloperWorks, WebSphere Business Process Management V6.1.2 Production Topologies

Draft Redbook, last updated: Thu, 4 Sep 2008 - Securing, administering, and extending WebSphere Process Server topologies - Incorporating WebSphere Business Services Fabric - Incorporating WebSphere Business Monitor IBM's WebSphere Dynamic Process Edition is a comprehensive set of role-based, SOA-enabled product capabilities providing customers the ability to continuously optimize processes and adapt them to rapidly changing needs.

Related Posts

• Building clustered topologies in WebSphere Process Server V6.1
• WebSphere Process Server Discussions
• Developing integration solutions with WebSphere Process Server relationships
• WebSphere Adapter for JDBC Export and SQL Server 2000: Table Locking while Polling
• SOA Jam: Unify The Numerous Enterprise Service Bus Products

From DeveloperWorks, WebSphere Business Services Fabric V6.1.2: Integrating with WebSphere Service Registry and Repository

WebSphere Business Services Fabric V6.1.2 now offers significant integration with WebSphere Service Registry and Repository V6.1 (WSRR). The old integration with WSRR no longer exists, as the new integration offers new ways of working with WSRR. This article describes how to use the new integration options.

Related Posts

• Hello World: WebSphere Service Registry and Repository
• Create classification taxonomies programmatically in IBM WebSphere Service Registry and Repository
• Getting Started with IBM WebSphere Business Services Fabric V6.1
• Establish a policy-driven SOA using WebSphere Service Registry and Repository and WebSphere ESB
• Using DataPower SOA Appliances to query WebSphere Service Registry and Repository

From DeveloperWorks, Introducing IBM WebSphere sMash, Part 1: Build RESTful services for your Web application

In this series, learn all about IBM WebSphere sMash, a simple environment for creating, assembling, and executing applications based on current Web technologies. In this first article, get a hands-on tour of the innovations that let you create, assemble, and deploy powerful Web applications. Learn how WebSphere sMash is community driven, and about its conventions for creating RESTful Web services. Using a step-by-step example, you set up the environment, create a project, build a RESTful service to expose data, test your application, and import a sample application to consume the RESTful services.

Step-by-step examples are always good in getting up to speed on a new software platform.

Related Posts

• Project Zero - Introduction
• ICTY Toronto 2008: A Smart SOA Approach in Any Economic Climate
• Impact 2008: Impressions of Day 2

From DeveloperWorks, Introduction to application server clustering with WebSphere Business Services Fabric

Clustered deployments are essential for growing enterprises because they enhance your ability to deliver reliable and scalable SOA solutions. This article provides an overview of how to deploy and configure WebSphere Business Services Fabric in a clustered environment.

Related Posts

• Getting Started with IBM WebSphere Business Services Fabric V6.1
• WebSphere Business Services Fabric
• WebSphere Business Services Fabric, Part 2: Extending the ontology models
• Demystifying WebSphere Business Services Fabric End Point Selection
• Adding custom roles in WebSphere Business Services Fabric

From DeveloperWorks, DataPower Architectural Design Patterns: Integrating and Securing Services Across Domains

Draft Redbook, last updated: Tue, 26 Aug 2008 - Introduction to DataPower Services - Integration Services - Security Services IBM® WebSphere® DataPower® SOA Appliances are purpose-built network devices that offer a wide variety of functionality such as the securing and management of SOA Applications, Enterprise Service Bus Integration, and high speed XSL execution.

I'm happy to see the emergence of design patterns for datapower.

Related Posts

• Make SOA real with IBM WebSphere Enterprise Service Bus and IBM WebSphere DataPower SOA Appliances
• IBM WebSphere DataPower SOA Appliances Part III: XML Security Guide
• IBM WebSphere DataPower SOA Appliances Part II: Authentication and Authorization
• IBM WebSphere DataPower SOA Appliances Part IV: Management and Governance
• IBM WebSphere DataPower SOA Appliances Part I: Overview and Getting Started