feature pack for web services - ibm · 2019-06-19 · feature pack for web services, but not the...

WebSphere Application Server for z/OS V6.1

Feature Pack forFeature Pack forFeature Pack forFeature Pack for

Web ServicesWeb ServicesWeb ServicesWeb Services(Known throughout this document and elsewhere as "FPWS")

This document can be found on the web at:www.ibm.com/support/techdocs

Search for document number WP101084 under the category of "White Papers"

Version Date: January 9, 2009See "Document Change History" on page 41 for a description of the changes in this version of the document

Written by the WebSphere Application Server for z/OS Support Team at the

IBM Washington Systems CenterIBM Washington Systems CenterIBM Washington Systems CenterIBM Washington Systems Center

Part of the IBM Americas Advanced Technical Support (ATS) organization

Many thanks to Harvey McGee, Rohith Ashok, and Diane Fahr, all of WebSpherez/OS development.

The WebSphere for z/OS support team at the Washington Systems Center consistsof: John Hutchinson, Bob Teichman, Mike Kearney, Louis Wilen, Lee-Win Tai,

Steve Matulevich and Don Bagwell. Mike Cox, Distinguished Engineer, serves astechnical consultant and advisor.

For questions or comments regarding this document, send e-mail to Don Bagwell [email protected]

Table of Contents

27Federating the Standalone server into the Deployment Manager cell . . . . . . . . . . . . . . . . . . . . . . . . . .27The customized jobs that are generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Upload to the z/OS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Configure the Standalone definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Start AST and launch zPMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Creating a Standalone Server node with the FPWS included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21The customized jobs now on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Upload to the z/OS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Configure the DMGR definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Start AST and launch zPMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Creating a Deployment Manager node with FPWS included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15The basics of how it is done . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Creating a New Node or Cell with FPWS Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Installing the Feature Pack for Web Services optional code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Using Rational Product Updater to bring AST to 6.1.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Installing Application Server Toolkit 6.1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Upgrading AST (and zPMT) and Installing Optional Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10What's next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Installation process at a high level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Minimum level of WebSphere Application Server required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10WebSphere Application Server "Optional Materials" installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Installation of the Feature Pack for Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Where you should go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Is there a charge for the AST? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9If I don't have a copy of the AST, can I get one? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9May I use the ISPF panels for any of this work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9How do I know that the update worked? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Do the application servers in the other nodes have to be stopped as well? . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Is there a way to "un-augment" the Deployment Manager if I change my mind? . . . . . . . . . . . . . . . . . . . . . . . .8Does the Deployment Manager have to be down when this is done? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8How long does the DMGR augmentation update take? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Does the augmenting of the DMGR change the configuration file structure? . . . . . . . . . . . . . . . . . . . . . . . . . . .8Does the DMGR need to be augmented before a FPWS node can be federated? . . . . . . . . . . . . . . . . . . . . . .8Will this involve the use of "intermediate symbolic links?" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8How does a node know about this Feature Pack for Web Services code? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8How do I provide this new function to an application server node? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Do I need this feature pack code included in all my nodes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Without this feature pack are web services in general not possible? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Is this something I should do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Is this something I must do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Some initial questions and answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Scenario Three - discard existing node and rebuild with feature pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Scenario Two - new appserver node with DMGR augmented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Scenario One - everything brand new from the start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Three scenarios for introducing the Feature Pack for Web Services function into a cell . . . . . . . . . . . . . . . . . .5The central role of the zPMT tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Important - managed nodes can not be augmented to include FPWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4New function is made available to nodes that need it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Web Services Feature Pack delivered as separate product HFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Some important starting concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

WP101084 - Feature Pack for Web Services

Section: MainVersion Date: Friday, January 09, 2009

- 1 -© 2007, IBM Americas Advanced Technical SupportWashington Systems Center, Gaithersburg, MD

41Document Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Granting necessary UNIXPRIV privileges to ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Performing a local update of Web Service Feature Pack optional code . . . . . . . . . . . . . . . . . . . . . . . .39Performing a local update of AST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37WSSampleServicesSei - simple ping and echo application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Sample applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36By using the versionInfo.sh shell script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36In a server's JES job log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36If you don't have access to the Administrative Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Check to see what servers are eligible to run applications that use FPWS function . . . . . . . . . . . . . . . . . . .35Check to see what nodes have been enabled for FPWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Updated Admin Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Visual validation in Admin Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Validation of Web Services Feature Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Restart the Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Run the IWOCAUGD job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Stop the Deployment Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Backup your configuration file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Upload to the z/OS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Configure the augmentation definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Start AST and launch zPMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Important Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Augmenting an Existing Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27The completed cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Overview

In the past, interim new function was introduced into WebSphere Application Server in the normalmaintenance stream. The function was then applied to the environment of everyone who installedthe maintenance, whether they wanted that new function or not.

But now there's a slightly new model being used. "Feature Packs" are a way of providing newfunction on an optional basis. Those who want it get the feature pack, those who do not want itsimply forego the feature pack.

This paper is focused on the first available feature pack for WebSphere Application Server for z/OS-- the "Web Services" feature pack. Information on what's included in the feature pack can befound at this URL:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg21264563

Here's a snippet of what can be found on that page. This gives an indication of what's included inthe Feature Pack for Web Service:

� Web Services Reliable Messaging (WS-RM) � Web Services Addressing (WS-Addressing) � SOAP Message Transmission Optimization Mechanism (MTOM) � Web Services Secure Conversations (WS-SC) � New standards-based programming model support: � Java API for XML Web Services (JAX-WS 2.0) � Java Architecture for XML Binding (JAXB 2.0) � SOAP with Attachments API for Java (SAAJ 1.3) � Streaming API for XML (StAX 1.0)

If you're not familiar with Web Services, or are not presently using that capability of WebSphereApplication Server, then you probably don't need to worry about installing the feature pack at thistime.

Some important starting concepts

More detail will follow, but to start the discussion let's get some essential concepts on the tableso the rest of this will make sense.

Web Services Feature Pack delivered as separate product HFS

WebSphere Application Server for z/OS ships a "product HFS" that contains files and codeneeded to support a WebSphere z/OS runtime configuration. This product HFS is shippedas hlq.SBBOHFS, where hlq is the high level qualifier you give it. For example,

WAS610.WAS.SBBOHFS. This is then mounted at a UNIX Systems Services mount point

such as /usr/lpp/zWebSphere/V6R1.

This new "Feature Pack for Web Services" resides in a separate product HFS. It is installedinto the "Optional Materials" (FMID JIWO610) product HFS. This is mounted at a mountpoint such as /usr/lpp/zWebSphere_OM/V6R1 ... different from the WebSphere product

HFS. PTF UK26168 and UK26278 are what load the FPWS code into this separate HFS.

/usr/lpp

/zWebSphere

/V6R1

/zWebSphere_OM

/V6R1

(The WebSphere z/OS product HFS)hlq.SBBOHFS

(WebSphere "Optional Materials" product HFS)

UK26168 and UK26278 will populate FPWS code here)

hlq.SIWOHFS




What all this means is that any WebSphere cell that wants to use this new function needs tobe told where this Feature Pack for Web Services product HFS is located. How that's doneis one of the main points of this paper.

New function is made available to nodes that need it

A WebSphere for z/OS cell consists of at least one node, and in most cases multiple nodes.Here's a picture of a "typical" cell that spans two LPARs. We'll use this just to illustrate ourpoints:

CR

Daemon

CR SR

DMGR

Node

CR

Node Agnt

Node A

CR SR

AppSvr

CR SR

AppSvr

MVS System Image A

CR

Daemon

CR

Node Agnt

Node B

CR SR

AppSvr

MVS System Image B

Cell

And here are the key points we wish to make at this point:

� Lets say you wanted the servers in Node A to use the function offered in the newFeature Pack for Web Services, but not the servers in Node B. That would mean NodeA would be built to connect to the Feature Pack, while Node B would not need to be.

In other words, this Feature Pack for Web Services is a node-by-node thing.Note:

� If any one of the application server nodes in the cell is going to make use of the FeaturePack for Web Services, then the Deployment Manager node must also be updated touse the feature pack functionality.

Very typical. The DMGR has to have access to any new function the appserver nodeswill make use of.

Note:

So far that's pretty standard and typical stuff. But wait ... there's more:

� An application server node can not be updated to include the Feature Pack for WebServices functionality. An application server node must be built that way from the start.You do that by using the zPMT to create the jobs to build the node, and you tell thezPMT to include the Feature Pack for Web Services function as well.

This brings up some interesting questions about how to incorporate this functionality intoa cell that already exists. We'll get to that in a minute.

Note:

� But a Deployment Manager node can be updated to include the Feature Pack for WebServices. That involves doing something called "augmenting" the DMGR withknowledge of this new functionality. You do this by using the zPMT to create a singlejob that augments the DMGR configuration with the FPWS function.




Important - managed nodes can not be augmented to include FPWS

This is really just a restatement of what was just said. To avoid any confusion about thisissue, you should be aware that a managed node -- otherwise known as a "federated node,"or "an application server node" -- can't be augmented (updated) to include the FPWS. TheDeployment Manager node can, but managed nodes can not.

See "Three scenarios for introducing the Feature Pack for Web Services function into a cell"on page 5 for information on how to accomodate this restriction.

The central role of the zPMT tool

The ISPF configuration panels have no knowledge of this new "Feature Pack for WebServices" option. You can't build a new node using FPWS using the ISPF panels and youcan't update an existing DMGR with FPWS using the ISPF panels.

The tool to use is the zPMT, which is a workstation-based GUI tool that's included inside theApplication Server Toolkit. The zPMT has been updated to include the ability to build anode with the feature pack functionality, and it has the ability to create the job to augmentan existing DMGR node.

The important thing is you have to be at the right level of the Application Server Toolkit tomake this work. And you have to install an "optional feature" so the zPMT knows about this"Feature Pack for Web Services" thing.

We show how to install and update the AST and install the FPWS optional feature under"Upgrading AST (and zPMT) and Installing Optional Feature" starting on page 11.

Three scenarios for introducing the Feature Pack for Web Services function into a cell

We'll offer three scenarios to give you a starting sense for how this new function can bemade available to a WebSphere cell

Scenario One - everything brand new from the start

Since we know that an existing application server node can't be updated withconnections to this new function, we know it's going to involve building the node fromthe start with that function.

How that's done is shown in "Creating a New Node or Cell with FPWS Included" startingon page 15.

Note:

A Deployment Manager can also be built so that it has this new function from the verybeginning as well.

Therefore, one scenario we have before us is the creation of a brand new cell. Built inthe following way:

� Use the zPMT to create the customized jobs that are used to build the DMGR node. Tell thezPMT to include the Feature Pack for Web Services functionality. Run the jobs to create theDMGR.

� Use the zPMT to create the customized jobs that are used to build a Standalone applicationserver node. Tell the zPMT to include the Feature Pack for Web Services functionality. Runthe jobs to create the Standalone server.

� Use the zPMT to create the job that's used to federate the Standalone server into the DMGRcell.

This is the standard methodology. The difference is the zPMT must be used, and youneed to tell the zPMT to include the FPWS function. We outline this process under"Creating a New Node or Cell with FPWS Included" starting on page 15.




Scenario Two - new appserver node with DMGR augmented

Imagine you have an existing cell and you want to start using some of the functionincluded in the Feature Pack for Web Services. We know that an existing applicationserver node can't be updated to include the new function. But a new node can becreated with the new function and federated into the cell:

CR

Daemon

CR SR

DMGR

Node

CR

Node Agnt

Node A

CR SR

AppSvr

CR SR

AppSvr

MVS System Image A

CR

Daemon

CR

Node Agnt

Node B

CR SR

AppSvr

MVS System Image B

Cell

CR

Node Agnt

Node AA

CR SR

AppSvr

zPMT

Built with Feature Pack for Web Services function included

Build and federate

This would also require augmenting the existing DMGR with the Feature Pack for WebServices function before doing the federation.

This scenario may be less-than-ideal for you. We show this so that you understand thatit's possible. But we admit it does bring up some issues concerning namingconventions.

The naming convention recommended by the Washington Systems Center (andincorporated into the PRS1331 planning spreadsheet found at the Techdocs website,ibm.com/support/techdocs), does not easily allow for two application server nodes

to exist on the same MVS image for the same cell.

Note:

But do you see the main point here? Since we can't update an existing applicationserver node with the FPWS function, this provides a way to get a node into the cellwhich has that function.

There's a third scenario, which is a variation on this second one ...

Scenario Three - discard existing node and rebuild with feature pack

Let's assume you don't like the idea of creating a "parallel node" on an MVS image.And you can't just build a whole new cell. Then the final option may be for you: it




involves unfederating an existing node and building a new node with the FPWS functionincluded:

CR

Daemon

CR SR

DMGR

Node

CR

Node Agnt

Node A

CR SR

AppSvr

CR SR

AppSvr

MVS System Image A

CR

Daemon

MVS System Image B

Cell

CR

Node Agnt

Node B

CR SR

AppSvrzPMT

Built with Feature Pack for Web Services function included

Build and federate

CR

Node Agnt

Node B

CR SR

AppSvr

Unfederate and discard

This would also require augmenting the existing DMGR with the Feature Pack for WebServices function before doing the federation.

This scenario would necessarily mean losing any post-construction customization you'ddone on the node that's unfederated. It also means that any applications deployed toservers in that node would have to be re-deployed after the new node is built andfederated.

So this option may not be ideal for you either. But those are the three ways in which youcan get the Feature Pack for Web Services function into a node so you can start usingthem.

Some initial questions and answers

Is this something I must do?

No. You consider this only if you want to provide to your WebSphere configuration the newfeatures that are provided in the Web Services Feature Pack.

Is this something I should do?

That depends. If you intend to use Web Services and you wish to take advantage of thenew function delivered in this Web Services Feature Pack (see list on page 3) ... then yes.But if you don't use web services, or the web services you do is fairly basic, then perhapsnot.

Without this feature pack are web services in general not possible?

You can still do web services, even without this feature pack. WebSphere ApplicationServer for z/OS V6.1 had web services support as part of the base product. What the




feature pack does is deliver new Web Services functionality above and beyond what wasthere before. We provided a bullet list of those new functions back on page 3.

Do I need this feature pack code included in all my nodes?

No. Only those application server nodes where you want to use the new functionality andthe Deployment Manager node. Application server nodes that don't need this newfunctionality don't require knowledge of or access to the feature pack.

How do I provide this new function to an application server node?

By building the node from the beginning with this function. You can't "update" or "augment"an existing application server node with the Feature Pack for Web Services. That is onlypossible for the Deployment Manager. Go back and review "Three scenarios for introducingthe Feature Pack for Web Services function into a cell" starting on page 5 for some insightinto how you can bring this function into play in your application server nodes.

How does a node know about this Feature Pack for Web Services code?

By way of a series of symbolic links which "connects" the configuration HFS with the WebServices Feature Pack code. This is true for the DMGR as well as any application servernode that's built with this Feature Pack for Web Services included.

Will this involve the use of "intermediate symbolic links?"

We strongly recommend you consider the use of an "intermediate symbolic link" betweeneach node and the actual Feature Pack for Web Services product HFS. This will helpmaintain proper isolation and flexibility.

"Intermediate symbolic links" are a way to improve the flexibility of your configuration when itcomes time to update it, such as with maintenance or when migrating to a new version.They are not strictly required. They do provide greater isolation and flexibility betweennodes.

See WP100396 at ibm.com/support/techdocs. That white paper explains the concept

of intermediate symbolic links, as well as the broader topic of node and cell isolation neededto do "Test, Production and Maintenance" type work.

Note:

Does the DMGR need to be augmented before a FPWS node can be federated?

Yes. Federation won't work otherwise.

Does the augmenting of the DMGR change the configuration file structure?

Yes it will. Whenever you augment DMGR node with this feature pack, be sure to back upyour cell's configuration file system.

How long does the DMGR augmentation update take?

It depends, but figure on about 20 minutes.

Does the Deployment Manager have to be down when this is done?

Yes. The Deployment Manager must be stopped when this update is performed.

Is there a way to "un-augment" the Deployment Manager if I change my mind?

There's no un-augment job. You can restore the backup copy of your file system.

Do the application servers in the other nodes have to be stopped as well?

No. They can continue running while the Deployment Manager is stopped for the update.




How do I know that the update worked?

The first good sign will be RC=0 for all four steps of the IWOCAUD job that updates your

configuration. Beyond that, there are some validation routines we documented under"Validation of Web Services Feature Pack" starting on page 35.

May I use the ISPF panels for any of this work?

No. The zPMT is what's required. The zPMT is part of the Application Server Toolkit(AST). The ISPF panels have no knowledge of this new feature pack.

Consider the ISPF panels more or less "deprecated" at this point in time. The zPMT methodof creating configurations and updating them will be what's used going forward from here.

Note:

Further, the AST and zPMT need to be brought up to the proper level for this to work. Weshow how to do that under "Upgrading AST (and zPMT) and Installing Optional Feature"starting on page 11.

If I don't have a copy of the AST, can I get one?

Yes. See the instructions for doing that under "Upgrading AST (and zPMT) and InstallingOptional Feature" starting on page 11.

Is there a charge for the AST?

If you have a valid license for WebSphere Application Server -- distributed or z/OS -- youhave the right to use the AST/zPMT. No charge.

Where you should go from here

"Other Information" on page 39.... are interested in seeing some other informationwe included that you might find useful ...

"Validation of Web Services Feature Pack" onpage 35.

... want to see how to validate that the FeaturePack for Web Services function you added actuallyworks ...

"Augmenting an Existing Deployment Manager" onpage 28.

... need to understand how to augment an existingDeployment Manager node so it can access andrecognize the new Feature Pack for Web Servicescode ...

"Creating a New Node or Cell with FPWS Included"on page 15.

...want to see how to create a new DMGR orappserver node with the FPWS code included ...

"Upgrading AST (and zPMT) and InstallingOptional Feature" on page 11.

... wish to find out how to acquire a copy of theAST, or update your existing copy, and how toinstall the Feature Pack for Web Services optionalcode into the AST ...

"Installation of the Feature Pack for Web Services"on page 10.

... need to understand more about the SMP/Einstallation of the FPWS code ...

Then go to ...If you ...




Installation of the Feature Pack for Web Services

The Feature Pack for Web Services comes as a PTF to WebSphere Application Server. Butinstallation of it is a little more involved than simply applying the PTF.

WebSphere Application Server "Optional Materials" installed

The FPWS requires that the WebSphere "Optional Materials" be installed. That is FMIDJIWO610. That is typically installed at /usr/lpp/zWebSphere_OM/V6R1.

The FPWS will be installed into that zWebSphere_OM structure.

Minimum level of WebSphere Application Server required

You must be at 6.1.0.9 at a minimum, but 6.1.0.15 or higher is preferred.

Installation process at a high level

� Receive and apply PTF UK26168. This contains a job that will create the necessary

directories in the "optional materials" (the /usr/lpp/zWebSphere_OM/V6R1 structure)

into which the FPWS code will be written.

� Receive and apply PTF UK26278. This is what populates the directories created by PTF

UK26168 with the FPWS code.

� Receive and apply ++APAR fixes PK47711 and PK47531. This fixes problems that were

discovered after UK26278 was closed.

Those fixes were supposed to be included in 6.1.011, but at least one user found that evenas high as 6.1.0.15 they were not. Better to assume it's not there and try to apply.

Note:

What's next

Once the code has been installed, you then update your configuration nodes to link to theproduct files that were installed with UK26278. Or, if you prefer, create a brand new cell that

points to the new FPWS code from the start. Both require the zPMT tool.

"Other Information" on page 39.... are interested in seeing some other informationwe included that you might find useful ...

"Validation of Web Services Feature Pack" onpage 35.

... want to see how to validate that the FeaturePack for Web Services function you added actuallyworks ...

"Augmenting an Existing Deployment Manager" onpage 28.

... need to understand how to augment an existingDeployment Manager node so it can access andrecognize the new Feature Pack for Web Servicescode ...

"Creating a New Node or Cell with FPWS Included"on page 15.

...want to see how to create a new DMGR orappserver node with the FPWS code included ...

"Upgrading AST (and zPMT) and InstallingOptional Feature" on page 11.

... wish to find out how to acquire a copy of theAST, or update your existing copy, and how toinstall the Feature Pack for Web Services optionalcode into the AST ...

Then go to ...If you ...




Upgrading AST (and zPMT) and Installing Optional Feature

To be able to create the customized job that does the Web Services Feature Pack augmentation,the Application Server Toolkit (AST, which contains the zPMT) must be at 6.1.1.3 or higher.Further, you must have the "Feature Pack for Web Services" optional product installed.

You can validate the level you currently have doing the following:

� Open up the Application Server Toolkit

� Go to Help � Software Updates � IBM Rational Product Updater

� This is what you need to create the customized augmentation job:

AST and Web Services Feature Pack optional feature

At least 6.1.1.3 and 1.0.0

If you don't see this, or you don't have the Application Server Toolkit at all, then follow theinstructions offered next to install and update your AST.

Installing Application Server Toolkit 6.1.1.0

If you already have Application Server Toolkit 6.1.1.0 at a minimum, then skip to the nextsection. Otherwise, follow the instructions to download and install AST 6.1.1.0 or update yourearlier version of AST to 6.1.1.0. Version 6.1.1.0 is the launching point to getting to 6.1.1.3,which is what you need to do this Web Services Feature Pack thing.

Note:

� Go to the following URL:

http://www.ibm.com/support/docview.wss?uid=swg24014241

� Scroll down to the section titled "Download package"

� Use either the FTP method or the DD (Download Director) method to download the fileesd.image.ast.win32.zip. The file is approximately 781MB in size.

� Unzip that file into a temporary folder. It'll produce two sub-folders: /disk1 and /disk2.

� Double-click on the file install.exe, which is found in the /disk1 folder.

� The installation process is fairly typical. Take the defaults.

Using Rational Product Updater to bring AST to 6.1.1.3

Once AST is at 6.1.1.0 at a minimum, you may then upgrade to 6.1.1.3. This is done with theRational Product Updater feature (otherwise known as "RPU"). Do the following:

� Close the AST if it's currently open. (The AST can't be open when RPU tries to update it.)

� Go to Start � All Programs � IBM WebSphere �




Application Server Toolkit V6.1.1 � Rational Product Updater

You may have other copies of RPU on your machine. But it's important the RPU you start isthe one associated with the AST. That's why we're driving you into the AST folder to startRPU from there.

Note:

� RPU should show you what's currently installed. Do the following:

Should show the 6.1.1 version as presently installed.

Click "Find Updates" 1

� You may see this:

This means that RPU itself needs a few updates. If you see this, go ahead and click "OK."It'll download a few files then recycle itself. You'll come right back to where you left offbefore.




� RPU will then go out to the web and search for updates. You'll see a little status barindicating it's looking for things. When it completes, you should see what is shown in thenext picture. Perform the steps indicated:

Make sure "IBM WebSphere Application Server Toolkit 6.1.1.3"

is present and is checked

1

Click "Install Updates"2

� It'll display a "License Agreement" panel. Select the "I Accept" radio button and click on"OK" to proceed.

� RPU will then go to the web to download and install the update files. This process takestime (perhaps 10 minutes or more). Please be patient.

If you find your firewall prevents FTP to the site without a proxy, you may need to do what'scalled a "local update." See "Performing a local update of AST" on page 39 for more on thisprocedure.

Note:

� When it completes you'll see what's shown next. Do what's shown here:

Click on "Installed Products"1

Should see AST 6.1.1.3 displayed

Appears blank, but that's because it's on the "Updates" tab.

You're now ready to install the optional feature for the Web Services Feature Pack.

Installing the Feature Pack for Web Services optional code

This optional code is what will provide the zPMT knowledge of how to create the Web ServicesFeature Pack augmentation job.




� Do the following:

Click on "Find Optional Features"

1

� RPU will go back out to the web to find what optional features are available for AST 6.1.1.3.This may take a few minutes, so please be patient. When it is done, you should see that ithas found two updates. But you only want one of them. Do the following:

Select "Feature Pack for Web Services" 1

Unselect "z/OS Extended Deployment"

2

Click "Install Features" 3

� RPU will then go to the web to download and install the update files. This process takestime (perhaps 10 minutes or more). Please be patient.

Again, you may find your firewall prevents FTP to the site without a proxy. You'll need to doa "local update." See "Performing a local update of Web Service Feature Pack optionalcode" on page 39 for more on this procedure.

Note:

� When it has completed, this is what you should see:

Your AST is now up to the minimum level to customize and create the Web ServicesFeature Pack augmentation job.




Creating a New Node or Cell with FPWS Included

To use the Feature Pack for Web Services functionality in an application server node, it isnecessary to include the FPWS at the time the node is initially built. You can't update an existingapplication server node with the FPWS function after the fact.

You can do that for a Deployment Manager node, however. How that's done is shown under"Augmenting an Existing Deployment Manager" starting on page 28.

Note:

Back on page 5 we showed "three scenarios" illustrating how the FPWS function can be broughtinto a cell. As a quick recap, those three were:

1. Build a cell from scratch, adding the FPWS function to each node as you build it.

2. Build a new standalone server with FPWS and federate it into an existing cell. This would require theexisting DMGR node to be updated (page 28) before the new standalone with FPWS was federated. Wenoted how this might mean having two nodes on the same MVS image, which tends to complicate thenaming convention.

3. Unfederate an existing application server node and discard it. Then build a new standalone server withFPWS and federate it into an existing cell. The DMGR would need to be updated (page 28) prior tofederating.

All three of those scenarios involve creating a node new and including the Feature Pack for WebServices at the time of creation.

The basics of how it is done

At a high level:

� The creation of the customized jobs that build the node must be done using the zPMT. The ISPFcustomization dialogs will not be able to incorporate the FPWS function.

� It involves one simple zPMT panel over and above what is normally required to configure aStandalone node or a Deployment Manager node.

� The same customized jobs are created by the zPMT as would be done if FPWS wasn't included.(However, some of the jobs do slightly more things.)

� The "planning spreadsheet" offered at ibm.com/support/techdocs under number PRS1331 can

be used to plan nearly all of the variable input. But at this time it still requires you to fill in the oneFPWS screen manually.

The message is this: if you're familiar with using the zPMT to create a WebSphere for z/OSnode, then creating one that includes FPWS will be very easy. The process is nearly identical.The only difference: one zPMT panel and one of the jobs (BBO*HFSA) takes longer than

before.

Creating a Deployment Manager node with FPWS included

Start AST and launch zPMT


Application Server Toolkit V6.1.1 � Application Server Toolkit

� When the "Select a Workspace" window appears, specify a location such asC:\ZPMT\aaaaa where aaaaa is the cell short name you'll be creating. Then click on

"OK."

This is just a folder location on your hard drive. The exact location doesn't matter. Whatdoes matter is that you not forget where you put this. We recommend creating acommon place for all zPMT configurations: C:\ZPMT. Under that would be different

folders for each cell: C:\ZPMT\DBCELL, C:\ZPMT\JHCELL, C:\ZPMT\RTCELL, etc.

Note:




� Go to Window � Preferences

� Scroll down and expand "Server"

� Click on "WebSphere for z/OS Customization". You'll see a window that looks like this:

Configure the DMGR definition

� Click on the button labeled "Create."

� Click the "Next" button to get past the panel with the link to the InfoCenter.

� On the first "Environment Selection" panel, do the following:

Select "Feature Pack for Web Services"

1

Click "Next" 2

� If you don't see the option "Feature Pack for Web Services," it means you haven'tupdated your copy of the AST to include it. See "Upgrading AST (and zPMT) andInstalling Optional Feature" starting on page 11 for information on how to do this.

� Selecting the "Feature Pack for Web Services" option is the key piece of this. Thistells the zPMT to create a "stacked" definition -- one that includes the cell creationas well as the addition of the FPWS functionality.

Notes:




� You'll see another "Environment Selection" panel. Do the following:

Select "z/OS deployment manager with Feature Pack for

Web Services"

1

Click "Next" 2

If you were creating a Standalone server then you'd select the other option.Note:

� At the "Customization Name and Location" panel, do the following:

Change the "Customization definition name" to something related to the cell and

standalone, for instance: JHCELL_NODEC1

Allow the "definition directory" to default. 2

For "Response file" see the note that follows this picture

3

Click "Next" 4

This "response file" field is a way to import the values for the variables so you don't haveto spend time setting them all. How do you create a "response file?" The "planningspreadsheet" offered under Techdoc PRS1331 at ibm.com/support/techdocs has

a worksheet tab that produces all the variables and values. Just copy out of there, pasteinto a notepad session and save. Then point to that file here. See WP100999 atibm.com/support/techdocs for an example of using the spreadsheet to create a

response file for import into the zPMT.

Note:




� The next dozen or so panels are exactly identical to what the zPMT would show if youwere doing a normal Standalone server creation without the FPWS. Exactly the same.We won't show those here because other documents cover that (WP100653 onibm.com/support/techdocs, for example).

However, we urge you to pay attention and not click "Next" again and again too quicklybecause the key "Feature Pack for Web Services" panel will slip by you. It will appearjust before the "Job Statement" panel (where you get to set the JOB card).

� The "Feature Pack for Web Services" panel is where you tell the zPMT where you'veinstalled the FPWS code:

See notes below1

2

3

Notes:

1. This field will be grayed out. It will contain the value for the mount point and "Deploymentmanager root directory," specified earlier in the zPMT. You can't change that value here.

2. For "Feature Pack for Web Services," specify the location where the Feature Pack productcode is installed. For example, /usr/lpp/zWebSphere_OM/V6R1/FPWS.

This will create symbolic links within your DMGR's configuration that point to this location. Forthat reason, you may wish to consider creating an intermediate symbolic link and use itbetween the node configuration and the product code, for example:

[node configuration] � /wasv61config/jhcell/jhdmnode_wsfp �

/usr/lpp/zWebSphere_OM/V6R1/FPWS

The key is you have to pick up the ./FPWS part of that.

In this example /wasv61config/jhcell/jhdmnode_wsfp is the intermediate

symbolic link. It points to the Web Services Feature Pack HFS. The value you'dcode into the zPMT would be the intermediate link, not the actual Feature Packlocation.

For more information on the basic principle behind intermediate symbolic links, seethe white paper WP100396 at ibm.com/support/techdocs.

Note:

3. For "Product File system directory," specify the location where the base WebSphere productcode is installed. For example, /usr/lpp/zWebSphere/V6R1.

This too will result in symbolic links being created within the node's configuration that point towhat you specify. For that reason, you may wish to consider using intermediate symbolic linkshere as well. For example:




[node configuration] � /wasv61config/jhcell/jhdmnode_wassmpe �

/usr/lpp/zWebSphere/V6R1

In this example /wasv61config/jhcell/jhdmnode_wassmpe is the

intermediate symbolic link. It points to the WebSphere product code. The valueyou'd code into the zPMT would be the intermediate link, not the actual FeaturePack location.


Note:

� Click the "Next" button.

� Now you'll see the "Job Statement Definition" panel. This gives you the opportunity tocustomize the JOB statement that will get generated on the jobs.

The jobs have different levels of authority needed ... some require RACF authority,others require the authority to do various UNIX things like chmod and chown. The

"instruction member" that's generated (BBOCCINS) will have the authority required by

each job.

See "Granting necessary UNIXPRIV privileges to ID" on page 40 for information on howto get around using a UID=0 ID. That involves granting another ID access to someUNIXPRIV profiles to give it just enough authority to do the work.


� At the "Customization Summary" panel, click the "Create" button.

� You'll see the "Operation in Progress" status bar window, then it'll return to the"Summary" panel but this time the "Finish" button will be available. Click the "Finish"button.

� You'll now see something like this:

Your customization definition

Opportunity to Upload to the z/OS system

Upload to the z/OS system

The zPMT has created the customized jobs and they are now ready to be uploaded to thez/OS system for execution. To upload them, do the following:

� Make sure the new definition is highlighted, then click on the "Upload" button.

� At the "Upload Customization Definition" panel, do the following:




See notes below

1

2

3

4

5

6

Notes:

1. Make sure the "Target z/OS system" field correctly specifies the IP host name of the systemwhere you want the jobs to run. Provide the proper IP host name if the field is blank or thename is not correct.

2. The UserID and password fields are used by the zPMT to establish the FTP session andupload the files. This can be your personal userid.

3. Leave the port at the default 21 unless you know the FTP port on the target system issomething different. Leave the timeout value as the default.

4. The target data set fields are grayed out ... they are not open to modification. This is tellingyou where it'll put the files. If what is displayed here is not correct, you need to cancel out andgo back into the zPMT and correct the "Target Data Set" definition in the definition.

5. Select this checkbox if you want zPMT to allocate the data sets just prior to uploading thedata. Otherwise, leave it unchecked if you know the data sets already exist and have thecorrect allocation parameters (CNTL: FB 80; DATA: VB 255)

6. When ready, click "Upload."

� You'll see this:

Then ...

� Click the "OK" button.

� You'll once again see this:




At this point you're done with the zPMT. That is, unless you discover a problem with thecustomized jobs and you need to regenerate them. If you find you need to correct somesmall error, do the following:

� Make sure the definition is highlighted� Click on "Regen"

� Work through the panels just as you did originally, correcting what needs correcting

� Click "Create" and "Finish" to complete the process, just as you did before

� Upload the files again

But that's only if you find an error. If the jobs run fine, you don't need to do this. You canclose the AST whenever you wish.

Note:

The customized jobs now on z/OS

The number of generated jobs and the names of the jobs are exactly the same as if you hadcreated them without the FPWS functionality. Execute the jobs in the sequence specified inthe "instruction member" BBOCCINS.

You'll find that the BBODHFSA job runs longer than it does without the FPWS function added

to the work it does.

Creating a Standalone Server node with the FPWS included

A standalone server is a building block towards a Network Deployment (ND) configuration. Astandalone server is "federated" into the DMGR cell to extend that cell to include the standaloneserver node. A node agent is automatically created when federation takes place.




� When the "Select a Workspace" window appears, specify a location such asC:\ZPMT\aaaaa where aaaaa is the cell short name of the DMGR cell into which this

standalone will eventually be federated. Then click on "OK."

This is just a folder location on your hard drive. The exact location doesn't matter. Whatdoes matter is that you not forget where you put this. We recommend creating acommon place for all zPMT configurations: C:\ZPMT. Under that would be different

folders for each cell: C:\ZPMT\DBCELL, C:\ZPMT\JHCELL, C:\ZPMT\RTCELL, etc.

Note:







DMGR definition if you did that first

Configure the Standalone definition

� Click on the button labeled "Create."


� On the first "Environment Selection" panel, do the following:

Select "Feature Pack for Web Services"

1

Click "Next" 2

� If you don't see the option "Feature Pack for Web Services," it means you haven'tupdated your copy of the AST to include it. See "Upgrading AST (and zPMT) andInstalling Optional Feature" starting on page 11 for information on how to do this.

� Selecting the "Feature Pack for Web Services" option is the key piece of this. Thistells the zPMT to create a "stacked" definition -- one that includes the cell creationas well as the addition of the FPWS functionality.

Notes:

� You'll see another "Environment Selection" panel. Do the following:

Select "z/OS application server

with Feature Pack for Web Services"

1

Click "Next" 2




If you were creating a DMGR then you'd select the other option.Note:


Change the "Customization definition name" to something related to the cell and DMGR,

for instance: JHCELL_DMGR.1


For "Response file" see the note that follows this picture

3

Click "Next" 4

This "response file" field is a way to import the values for the variables so you don't haveto spend time setting them all. How do you create a "response file?" The "planningspreadsheet" offered under Techdoc PRS1331 at ibm.com/support/techdocs has

a worksheet tab that produces all the variables and values. Just copy out of there, pasteinto a notepad sesssion and save. Then point to that file here. See WP100999 atibm.com/support/techdocs for an example of using the spreadsheet to create a

response file for import into the zPMT.

Note:

� The next dozen or so panels are exactly identical to what the zPMT would show if youwere doing a normal DMGR creation without the FPWS. Exactly the same. We won'tshow those here because other documents cover that (WP100653 onibm.com/support/techdocs, for example).

You may need to bump the default size of the configuration HFS. Our tests seems toindicate the default of 420 might be too small when FPWS is included. You'll see thefailure in the WPROFILE step of the BBOWWPFA job with a message of "Insufficientdisk space." 500 cylinders ought to do it.

Note:

However, we urge you to pay attention and not click "Next" again and again too quicklybecause the key "Feature Pack for Web Services" panel will slip by you. It will appearjust before the "Job Statement" panel (where you get to set the JOB card).

� The "Feature Pack for Web Services" panel is where you tell the zPMT where you'veinstalled the FPWS code:




1

2

See notes below

3

Notes:

1. This field will be grayed out. It will contain the value for the mount point and "Applicationserver root directory," specified earlier in the zPMT. You can't change that value here.

2. For "Feature Pack for Web Services," specify the location where the Feature Pack productcode is installed. For example, /usr/lpp/zWebSphere_OM/V6R1/FPWS.

This will create symbolic links within your DMGR's configuration that point to this location. Forthat reason, you may wish to consider creating an intermediate symbolic link and use itbetween the node configuration and the product code, for example:

[node configuration] � /wasv61config/jhcell/jhnodec_wsfp �




symbolic link. It points to the Web Services Feature Pack HFS. The value you'dcode into the zPMT would be the intermediate link, not the actual Feature Packlocation.


Note:

3. For "Product File system directory," specify the location where the base WebSphere productcode is installed. For example, /usr/lpp/zWebSphere/V6R1.

This too will result in symbolic links being created within the node's configuration that point towhat you specify. For that reason, you may wish to consider using intermediate symbolic linkshere as well. For example:

[node configuration] � /wasv61config/jhcell/jhnodec_wassmpe �


In this example /wasv61config/jhcell/jhdmnode_wassmpe is the

intermediate symbolic link. It points to the WebSphere product code. The valueyou'd code into the zPMT would be the intermediate link, not the actual FeaturePack location.


Note:





� Now you'll see the "Job Statement Definition" panel. This gives you the opportunity tocustomize the JOB statement that will get generated on the jobs.

The jobs have different levels of authority needed ... some require RACF authority,others require the authority to do various UNIX things like chmod and chown. The

"instruction member" that's generated (BBOCCINS) will have the authority required by

each job.

See "Granting necessary UNIXPRIV privileges to ID" on page 40 for information on howto get around using a UID=0 ID. That involves granting another ID access to someUNIXPRIV profiles to give it just enough authority to do the work.


� At the "Customization Summary" panel, click the "Create" button.

� You'll see the "Operation in Progress" status bar window, then it'll return to the"Summary" panel but this time the "Finish" button will be available. Click the "Finish"button.





The zPMT has created the customized jobs and they are now ready to be uploaded to thez/OS system for execution. To upload them, do the following:






See notes below

1

2

3

4

5

6

Notes:

1. Make sure the "Target z/OS system" field correctly specifies the IP host name of the systemwhere you want the jobs to run. Provide the proper IP host name if the field is blank or thename is not correct.

2. The UserID and password fields are used by the zPMT to establish the FTP session andupload the files. This can be your personal userid.

3. Leave the port at the default 21 unless you know the FTP port on the target system issomething different. Leave the timeout value as the default.

4. The target data set fields are grayed out ... they are not open to modification. This is tellingyou where it'll put the files. If what is displayed here is not correct, you need to cancel out andgo back into the zPMT and correct the "Target Data Set" definition in the definition.

5. Select this checkbox if you want zPMT to allocate the data sets just prior to uploading thedata. Otherwise, leave it unchecked if you know the data sets already exist and have thecorrect allocation parameters (CNTL: FB 80; DATA: VB 255)



Then ...






At this point you're done with the zPMT. That is, unless you discover a problem with thecustomized jobs and you need to regenerate them. If you find you need to correct somesmall error, do the following:

� Make sure the definition is highlighted� Click on "Regen"

� Work through the panels just as you did originally, correcting what needs correcting

� Click "Create" and "Finish" to complete the process, just as you did before

� Upload the files again

But that's only if you find an error. If the jobs run fine, you don't need to do this. You canclose the AST whenever you wish.

Note:

The customized jobs that are generated

The number of generated jobs and the names of the jobs are exactly the same. Executethe jobs in the sequence specified in the "instruction member".

Federating the Standalone server into the Deployment Manager cell

This process is identical to how it was done before. The inclusion of the Feature Pack for WebServices functionality does not impact the act of federation. It does not impact the steps takento create the customized federation job (BBOWADDN), nor does it impact the running of that job.

The completed cell

Had you gone through the creation of the DMGR+FPWS and the Standalone+FPWS along withfederation, you'd have a cell that looks like this. It would have the FPWS built into both nodes(DMGR and the appserver node). You could now move on to validation (see "Validation of WebServices Feature Pack" on page 35).

CR

Daemon

CR SR

DMGR

Node

CR

Node Agnt

Node A

CR SR

AppSvr

MVS System Image A

An ND cell with FPWS incorporated into both nodes




Augmenting an Existing Deployment Manager

Imagine you just got done building a standalone server and you followed the steps we outlinedunder "Creating a Standalone Server node with the FPWS included" on page 21. Your intent wasto federate the standalone into an existing DMGR. So you configure up the BBOWADDN federation

job and discover that the federation fails.

What you would find is that WebSphere will not allow a standalone server that's been built withFPWS to be federated into a DMGR cell where the DMGR itself has not been updated with FPWSalso. Your existing DMGR is otherwise perfectly good, so you don't want to throw it away andrebuild it. What to do? You "augment" the existing DMGR with the Feature Pack for WebServices.

This involves using the zPMT to create the IWOCAUGD job. That job is what links your configuration

to the Web Services Feature Pack and "augments the profile," which is what provides the AdminConsole knowledge of the update.

Important Note

The DMGR to be augmented must be built using the "z/OS Deployment Manager" option of thezPMT and not the "z/OS cell (deployment manager and application server)" option.Augmentation fails if the DMGR was built using the "cell" option.




� When the "Select a Workspace" window appears, specify a location such asC:\ZPMT\aaaaa where aaaaa is the cell short name you'll be augmenting. Then click on

"OK."

This is just a folder location on your hard drive. The exact location doesn't matter. Whatdoes matter is that you not forget where you put this. We recommend creating a commonplace for all zPMT configurations: C:\ZPMT. Under that would be different folders for each

cell: C:\ZPMT\DBCELL, C:\ZPMT\JHCELL, C:\ZPMT\RTCELL, etc.

Note:







Configure the augmentation definition

� Click on the button labeled "Augment."


� On the "Environment Selection" panel, select the option for "z/OS Deployment Manager.Click the "Next" button.

� On the "Augmentation Selection" panel, select "z/OS Deployment Manager with FeaturePack for Web Services." Click the "Next" button.


Change the "Customization definition name" to something related to this Web Services Feature Pack update ... for example: WSFP

1


Leave "response file" blank 3

Click "Next" 4

� At the "Target Data Sets" panel, specify the high-level qualifier you wish to use when thecustomized jobs are uploaded to z/OS. They don't need to pre-exist ... zPMT is capable ofallocating them on the fly.

� Consider using a name something like this: JHCELL.WSFP, where in this example JHCELL

is the short name of the cell and WSFP stands for "Web Services Feature Pack."





� At the "Feature Pack for Web Services" panel, do the following:

See notes below1

2

3

Notes:

1. For "Deployment manager root directory," specify the location of the Deployment Manager youwish to update. This would include the mount point and the /DeploymentManager portion.

Example: /wasv61config/jhcell/jhdmnode/DeploymentManager

2. For "Feature Pack for Web Services," specify the location where the Feature Pack product code isinstalled. For example, /usr/lpp/zWebSphere_OM/V6R1/FPWS.

This will create symbolic links within your DMGR's configuration that point to this location. Forthat reason, you may wish to consider creating an intermediate symbolic link and use it betweenthe node configuration and the product code, for example:

[node configuration] � /wasv61config/jhcell/jhdmnode_wsfp �




symbolic link. It points to the Web Services Feature Pack HFS. The value you'd codeinto the zPMT would be the intermediate link, not the actual Feature Pack location.

For more information on the basic principle behind intermediate symbolic links, see thewhite paper WP100396 at ibm.com/support/techdocs.

Note:

For "Product File system directory," specify the location where the base WebSphere product codeis installed. For example, /usr/lpp/zWebSphere/V6R1.

3. This too will result in symbolic links being created within the node's configuration that point to whatyou specify. For that reason, you may wish to consider using intermediate symbolic links here aswell. For example:

[node configuration] � /wasv61config/jhcell/jhdmnode_wassmpe �


In this example /wasv61config/jhcell/jhdmnode_wassmpe is the intermediate

symbolic link. It points to the WebSphere product code. The value you'd code into thezPMT would be the intermediate link, not the actual Feature Pack location.

Note:




For more information on the basic principle behind intermediate symbolic links, see thewhite paper WP100396 at ibm.com/support/techdocs.


� Now you'll see the "Job Statement Definition" panel. This gives you the opportunity tocustomize the JOB statement that will get generated on the job.

At this point we want to draw your attention to the authority under which this job will run.You have two basic choices:

Note: See "Granting necessary UNIXPRIV privileges to ID" on page 40.

� No worries about files created or modified andleft with the wrong ownership

� The Admin ID needs the UNIXPRIV

authorities as outlined in the BBOCCINS

member in the CNTL data set used to create

the Deployment Manager.Note

� Will have all the authority it needs to createlinks, change ownerships and permissions

� It may leave some files owned by this UID=0ID. To be safe, you should run the BBODHFSB

job to "fix" any file ownership problems thatmay result from this.

Run under WebSphere Admin IDRun under UID=0 ID

Either way is fine ... just be aware of the pros and cons of each. Update the JOB card asyou see fit.


� At the "Customization Summary" panel, click the "Augment" button.

� You'll see the "Operation in Progress" status bar window, then it'll return to the "Summary"panel but this time the "Finish" button will be available. Click the "Finish" button.





The zPMT has created the customized job and it is now ready to be uploaded to the z/OSsystem for execution. To upload it, do the following:






See notes below

1

2

3

4

5

6

Notes:

1. Make sure the "Target z/OS system" field correctly specifies the IP host name of the systemwhere you want the job to run. Provide the proper IP host name if the field is blank or the name isnot correct.

2. The UserID and password fields are used by the zPMT to establish the FTP session and uploadthe files. This can be your personal userid.

3. Leave the port at the default 21 unless you know the FTP port on the target system is somethingdifferent. Leave the timeout value as the default.

4. The target data set fields are grayed out ... they are not open to modification. This is telling youwhere it'll put the files. If what is displayed here is not correct, you need to cancel out and go backinto the zPMT and correct the "Target Data Set" definition in the definition.

5. Select this checkbox if you want zPMT to allocate the data sets just prior to uploading the data.Otherwise, leave it unchecked if you know the data sets already exist and have the correctallocation parameters (CNTL: FB 80; DATA: VB 255)



Then ...






At this point you're done with the zPMT. That is, unless you discover a problem with thecustomized job and you need to regenerate it. If you find you need to correct some smallerror, do the following:

� Make sure the definition is highlighted� Click on "Regen"� Work through the panels just as you did originally, correcting what needs correcting� Click "Augment" and "Finish" to complete the process, just as you did before� Upload the files again

But that's only if you find an error. If the job runs fine, you don't need to do this. You canclose the AST whenever you wish.

Note:

Backup your configuration file systems

The customized job will make updates to your Deployment Manager's configuration HFS.There is no way to "un-augment" or backout the changes other than to restore a good copy ofthe file system.

The customized job will not make modification to the configuration file systems of any othernodes that are part of the cell. In theory you need only backup your DMGR configuration HFS.But there's a chance some part of the updates may be synchronized out to the nodes.

So we recommend you take a clean copy of your whole cell. That way if you need to revertback, you can revert back to a known checkpoint for the whole cell.

Use whatever backup utility you have in the past.

Stop the Deployment Manager server

The DMGR must be stopped when you make these updates against its configuration.

The other servers in the cell -- node agents, application servers, daemon servers -- may keeprunning. But the DMGR must be down.

Run the IWOCAUGD job

� Go to the CNTL target data set. This would be the data set the zPMT uploaded the files to.

There'll be two data sets -- CNTL and DATA. The job you'll run is in the CNTL data set.

� Submit the IWOCAUGD job. It'll be the only member in the CNTL data set.

� The job has four steps. It should take between 10 and 20 minutes to run. Successfulcompletion will look something like this:

Jobname Procstep Stepname CPU Time EXCPs RC

IWOCAUGD --None-- FPECSYM 00:00:00 55 00




IWOCAUGD --None-- WSFPSYM 00:00:00 54 00

IWOCAUGD --None-- AUGMENT 00:00:00 54 00

IWOCAUGD --None-- JOBLOG 00:00:00 62 00

$HASP395 IWOCAUGD ENDED

Restart the Deployment Manager

� Restart your Deployment Manager




Validation of Web Services Feature Pack

Visual validation in Admin Console

You can check in the Admin Console and see if it recognizes nodes and servers as enabled forthe feature pack.

Updated Admin Console

The first sign of success is an updated Admin Console. With the DMGR profile augmentedwith the Web Services Feature Pack updates, you'll now see this:

This "Services" section, and all the links within it, is new with the WSFP update to the

configuration

Check to see what nodes have been enabled for FPWS

� In the Admin Console, go to:

System Administration � Nodes

� Note the information provided there:

Provides version information for WebSphere itself, as well as any applied feature pack.

In this example, WS FEP 6.1.0.9 is the Web Services Feature Pack

The DMGR node (fzdmnode) and the application server node (fznodec) have been enabled with the Web Services Feature Pack

Check to see what servers are eligible to run applications that use FPWS function

� In the Admin Console, go to:




Servers � Application Servers

� Note the information provided there:

Version information, just like what was provided for the nodes as

shown previously.

The FPWS function is provided on a node-by-node basis. If a node has beenupdated with access to FPWS, then all servers in that node have access to theFPWS function. You can't "enable" or "disable" on a server-by-server basis.

What we're showing above is a quick way to see the servers in a cell and knowwhich ones have the FPWS applied ("WS FEP 6.1.0.9" in the picture above). Butwhat it's really saying is that the FPWS has been applied to the node. The serverjust happens to be in the node.

If this picture showed a server in another node which hadn't been given access toFPWS, then you'd see the server and "ND 6.1.0.9," but no "WS FEP 6.1.0.9."

Important:

If you don't have access to the Administrative Console

In a server's JES job log

Look for the string webservices. You should see something like this:

BBOJ0077I: com.ibm.ws.webservices.s

BBOJ0077I: tartup.wsdl.suppressMessages = INFO

It appears that message is associated with the presence of the FPWS.

By using the versionInfo.sh shell script

Each node in a cell has a shell script called versionInfo.sh which will report on the

installed products for that node.

The shell script is located in the node's /bin directory. Example:

/<mount>/DeploymentManager/bin

From Telnet or OMVS, invoke that shell script with no parameters. You should see itreport on the level of the installed WebSphere as well as any feature packs or otherproducts augmented into the node. Here's an example of a node with both the FPWSand WebSphere Process Server augmented:

Product List ------------------------------------------------------------------ND installed WEBSERVICES installed WBI installed




Installed Product ------------------------------------------------------------------Name IBM WebSphere Application Server for z/OSVersion 6.1.0.21 ID ND Build Level cf210845.06 Build Date 11/11/08 Installed Product ------------------------------------------------------------------Name WebServices Feature Pack Version 6.1.0.21 ID WEBSERVICES Build Level cf210844.03 Build Date 11/6/08 Installed Product ------------------------------------------------------------------Name IBM WebSphere Process Server Version 6.2.0.0 ID WBI Build Level o0847.13 Build Date 11/26/08 ------------------------------------------------------------------

End Installation Status Report

Sample applications

WSSampleServicesSei - simple ping and echo application

This is a relatively simple to install and use application that provides a service that canperform a ping or echo exercise, thus validating your Feature Pack for Web Servicesinstallation.

This application requires almost no prior knowledge of web services.

These instructions will have you FTP the sample EAR to your workstation then install it fromthere using the Admin Console. You may skip the FTP step and point the Admin Consoleto where the sample EAR is supplied in the FPWS HFS.

Note:

� Open up an FTP window and connect to your z/OS system.

� Set the transfer mode to binary

� Change directories so you're in the following directory:

/shared/zWebSphere_OM/V6R1/FPWS/samples/lib/WebServicesSamples

� FTP in binary the following two files from your z/OS system down to your workstation:

� WSSampleServicesSei.ear

� WSSampleClientSei.ear

The first one will be the web service deployed into your FPWS-enabled WebSphereapplication server. The second is a web services client with a browser interface. It canbe deployed anywhere, including the same server if you want to keep things simple.

Note:

� Go into the Admin Console and install both EAR files like you would any other EAR file.Install both into an application server in your cell that has access to the FPWS code.Take all other default values.

� Save and synchronize to the node.




� Start both applications and insure you get a "green arrow" for both.

� Open a browser window and point it at:

http://<host>:<port>/wssamplesei/demo

Supply the correct IP host and port for your application server.

� You should get something that looks like this:

Message type: one-way pingsynchronous echo, asynchronous echo with synchronous communicationasynchronous echo with asynch communication

The text string you want sent

The number of messages you want sent

Host and port where service is deployed

Response back from service displayed here

� For the first test, do the following:

� Message Type: Synchronous Echo

� Message String: My First Test

� Message Count: 1

� Service URL: http://<host>:<port>(where <host> and <port> match the server where WSSampleServicesSei.ear was deployed)

� Click the "Send Message" button. This will format up the web services request andsend it to the service provider, which is the WSSampleServicesSei.ear application youdeployed.

� You should see a response come back to the display window on the browser.




Other Information

Performing a local update of AST

If you find that the Rational Product Updater can't do the FTP download of the update filesbecause of firewall issue, you may need to perform a "local update". This really means that youmanually download the 6.1.1.3 update ZIP file, then point the Rational Product Updater at theZIP file on your hard drive. The update is done "locally."

The RPU product has the ability to configure proxy settings for HTTP, but not FTP. Browsers onthe other hand are quite configurable for proxy settings, both HTTP and FTP. So while RPUmay not be able to use FTP to fetch the files, your browser can.

Note:

Do the following:

� Point your browser at the following URL (all on one line ... it's split here):

ftp://ftp.software.ibm.com/software/websphere/appserv

/support/tools/AST/local/fixpacks/ast61/fp6113/

� Save the ast611fixpack3.zip file to your workstation's hard drive. The file is 580MB in

size, so it may take a few minutes.

� Unzip that file into some temporary folder, such as C:\temp\fixpack3 or whatever.

� Now go to Start � All Programs � IBM WebSphere �


� When RPU opens, select Preferences � Update Sites.

� Use the "Browse" button drill down into where you unzipped the downloaded ZIP file ...C:\temp\fixpack3 or whatever you called it.

� Drill down into the \update folder

� Select the policy_6113_fixpack3.xml file then click the "Open" button

� Click on "OK". You just told RPU where to look for updates. It'll "go" to that local folderstructure rather than out to the web.

When you're done, don't forget to clear this setting ... otherwise it'll keep going there for allfuture updates.

Note:

� Click on the "Find Updates" button. RPU will very quickly search through your "local site"and determine the one update available is FixPack 3 -- 6.1.1.3

� Once it's done that, click on "Install Updates". It'll then start updating AST to 6.1.1.3. Thisprocess will take 10 minutes or more.

� When it has completed, close RPU. Your AST is now at 6.1.1.3.

Performing a local update of Web Service Feature Pack optional code

This process is nearly identical to the one we just outlined for the 6.1.1.3 fixpack update, exceptthe file you download is different and the XML file you point to from RPU is different.

� Point your browser at the following URL (all on one line ... it's split here):

ftp://ftp.software.ibm.com/software/websphere/appserv

/support/tools/AST/local/fixpacks/ast61/wsfp/

� Save the ast611wsfp.zip file to your workstation's hard drive. The file is 76MB in size.




� Unzip that file into some temporary folder, such as C:\temp\wsfp or whatever.

� Now go to Start � All Programs � IBM WebSphere �


� When RPU opens, select Preferences � Update Sites.

� Use the "Browse" button drill down into where you unzipped the downloaded ZIP file ...C:\temp\wsfp or whatever you called it.

� Drill down into the \update folder

� Select the policy_wsfp.xml file then click the "Open" button

� Click on "OK". You just told RPU where to look for the feature. It'll "go" to that local folderstructure rather than out to the web.

When you're done, don't forget to clear this setting ... otherwise it'll keep going there for allfuture features.

Note:

� Click on the "Find Optional Features" button. RPU will very quickly search through your"local site" and determine the one update available is the Web Services Features Pack.

� Once it's done that, click on "Install Features". It'll then start installing the Web ServicesFeature Pack updates. This process will take a few minutes.

� When it has completed, close RPU. Your AST now has the Web Services Feature Packoptional feature installed.

Granting necessary UNIXPRIV privileges to ID

WebSphere for z/OS documents a way to have an ID other than a UID=0 ID run thecustomization jobs. In the past a UID=0 ID was suggested because it was guaranteed to havethe needed authority to create directories, and issue the chown and chmod commands. But

many people, very reasonably, requested information on how to give an ID just enoughauthority without having it be a full UID=0 ID. What follows are the commands that are neededto grant the UNIXPRIV authorities that would give it just enough:

PERMIT SUPERUSER.FILESYS CLASS(UNIXPRIV) ID(adminid) ACC(CONTROL)PERMIT SUPERUSER.FILESYS.MOUNT CLASS(UNIXPRIV) ID(adminid) ACC(UPDATE)PERMIT SUPERUSER.FILESYS.CHOWN CLASS(UNIXPRIV) ID(adminid) ACC(READ)PERMIT SUPERUSER.FILESYS.CHANGEPERMS CLASS(UNIXPRIV) ID(adminid) ACC(READ)PERMIT SUPERUSER.FILESYS.PFSCTL CLASS(UNIXPRIV) ID(adminid) ACC(READ)SETROPTS RACLIST(UNIXPRIV) REFRESH

If you wish, you may continue to use a UID=0 ID.




Document Change History

Check the date in the footer of the document for the version of the document.

Added information on verifying installation when access to the Administrative Console isnot available. Two methods offered: one is to search for the string "webservices" in thejob log; and the second is to run the versionInfo.sh shell script.

January 9, 2009

Further refinements to the minimum levels and PTFs on page 10. Also, included astronger statement about how managed nodes can't be augmented. See "Important -managed nodes can not be augmented to include FPWS" on page 5.

July 16, 2008

Updated information about minimum levels and PTFs on page 10. Prior informationsaid 6.1.0.11 should have included the referenced ++APAR, but it turns out it did not.

July 8, 2008

Note added regarding which option of zPMT used to create DMGR. Augmentationwon't work if DMGR created with the zPMT "cell" options (DMGR + federatedapplication server node in one set of jobs). The DMGR must be built using only the"Deployment Manager" option. See "Important Note" on page 28.

June 10, 2008

A few typos fixed, as well as a note provided about how the WPROFILE step of theBBOWWPFA job used when creating a standalone node with FPWS may fail due to"insufficient disk space." The default HFS allocation size is too small when FPWS isincluded. Setting the allocation cylinders to 500 ought to fix that.

August 3, 2007

The WP101084 number assigned to the Techdoc submission is updated in the paperand the paper is republished.

July 26, 2007

Original document.July 25, 2007

End of WP101084




feature pack for web services - ibm · 2019-06-19 · feature pack for web services, but not the...

Documents