[z/OS]

Applying maintenance for Feature Pack for EJB 3.0 for z/OS

Similar to maintenance done to the base WebSphere Application Server for z/OS product, maintenance to the WebSphere Application Server Optional Materials is applied using SMPE, then moved into production. Optional Materials includes feature packs and other interim deliverables, all shipped as maintenance to FMID JIWO610.

Before you begin

In general, feature pack maintenance levels for WebSphere Application Server Version 6.1 are closely linked to base WebSphere Application Server maintenance levels. On distributed platforms, feature pack maintenance is applied automatically when base maintenance is installed. On z/OS, customers are responsible for upgrading feature pack levels whenever base service levels are upgraded. If the WebSphere Application Server base service level is higher than the feature pack service level, feature-pack enabled servers will not start.

The WebSphere Application Server for z/OS service support page provides PTF lists for base WebSphere Application Server for z/OS, and for each feature pack or other interim deliverable. The general rule is that each feature pack level will run correctly with base WebSphere Application Server at the same level, or one level higher. Thus, Feature Pack Services Version 6.1.0.13 will run with base WebSphere Application Server Version 6.1.0.13 or Version 6.1.0.14. If you upgrade the base WebSphere Application Server code to Version 6.1.0.15, you will also need to install a new level of Feature Pack for Web Services Version 6.1.0.15.

Note: In general, the "even" service levels are for base WebSphere Application Server for z/OS only; this is the reason for the "one level higher" exception.

What to do next: Decide which base WebSphere Application Server for z/OS maintenance level you will be upgrading to, and which feature packs or other interim deliverables will need to be upgraded.

Contact the IBM Software Support Center or consult the WebSphere Application Server for z/OS support page to determine the PTFs for the required feature pack or interim deliverable maintenance levels, and order or download these PTFs.

About this task

What to do next

The WebSphere Application Server for z/OS nodes that are upgraded to the new service level are now running with compatible WebSphere Application Server for z/OS and Optional Materials maintenance.

Restarting a WebSphere Application Server for z/OS node at a previous service level normally involves simply switching the runtime to use the previous level of code (datasets and product filesystem); the post-installer will check that any configuration changes made since the old level are backwards compatible.

New service levels which are not backwards compatible will have this fact flagged in an ACTION HOLD statement for the service PTFS; customers who need to restart at the earlier service level will need to run the backoutPTF.sh script, as documented in Completing post-installation tasks before using SMP/E to restore to the previous accepted service level. To back out configuration changes for feature packs or other optional materials, specify the feature pack identifier (rather than "WebSphere") in the backoutPTF.sh command:
backoutPTF.sh FPEJB3 f00742.08		for Feature Pack for EJB e3.0     

backoutPTF.sh WSFP wf130742.10		for Feature Pack for Web Services



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_ejbmaint_zos
File name: tins_ejbmaint_zos.html