Before using this information and the product it supports, be sure to read the general information under Notices.
This edition applies to IBM WebSphere Studio Asset Analyzer for Multiplatforms Version 4 Release 1 (Program Number 5655-M22).
This edition also applies to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters.
You can order publications online at www.ibm.com/shop/publications/order, or order by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. Eastern Standard Time (EST). The phone number is (800)879-2755. The fax number is (800)445-9269.
You can find out more about WebSphere Studio Asset Analyzer for Multiplatforms by visiting the IBM Web site for the product at: www.ibm.com/software/awdtools/wsaa/.
A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
This guide is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the procedures associated with the configuration of WebSphere Studio Asset Analyzer for Multiplatforms and migration from earlier releases. This publication provides detailed instructions on how to create, configure, and load the DB2 database. It also gives instructions for specifically configuring your HTTP Server and WebSphere Application Server for use with WebSphere Studio Asset Analyzer.
It contains a sample installation verification procedure to ensure that the database loads correctly and instructions on how to set up the sample applications.
You use two interfaces to configure WebSphere Studio Asset Analyzer: ISPF on the host and Internet Explorer on the workstation. Therefore you need Microsoft Internet Explorer 5.5 or later installed on your workstation.
Each user of WebSphere Studio Asset Analyzer must have a TSO userid on the MVS system, and that userid must have the authority to connect to the product database to INSERT, UPDATE, DELETE, and SELECT rows from the database tables. If WebSphere Studio Asset Analyzer is being accessed from Windows, any userid connecting to the database must have the authority to create remote connections.
Because some administrative WebSphere Studio Asset Analyzer requests create jobs that access the database, any userid that has administrative authority must also have the authority to access DB2 from a batch job, even if such a job is not submitted directly.
You can install WebSphere Studio Asset Analyzer with one of the following configurations:
The following tables show where the related software and the components of WebSphere Studio Asset Analyzer are installed for each of these configurations.
See the WebSphere Studio Asset Analyzer Program Directory for the versions and releases for the above related software that is required for this release of WebSphere Studio Asset Analyzer. You can find the Program Directory on the product Library Web page.
The tasks that you perform to configure WebSphere Studio Asset Analyzer and the supporting products depends on both of the following situations:
Some of the sections and steps in these configuration instructions apply to only one of the two configurations or apply only if your users are going to use the distributed asset support of WebSphere Studio Asset Analyzer. Perform the configuration tasks in the order given in this guide, skipping the sections and steps that do not apply to your situation.
This publication refers to WebSphere Studio Asset Analyzer for Multiplatforms as WebSphere Studio Asset Analyzer and refers to either the z/OS or the OS/390 system as MVS.
If your order contains the Japanese feature FMID J2A1411, ensure that you complete the installation for that feature before configuring WebSphere Studio Asset Analyzer. Member DMHVERSN in data set yourHLQ.SDMHDATA should show 'Version 4.1.0 JPN' instead of 'Version 4.1.0 ENU'.
The following material provides information that you need to configure WebSphere Studio Asset Analyzer and to verify a successful installation. Before you start these tasks, ensure that each companion product is working properly and that it works properly with the other products. For example, ensure that the verification and IVP process for the HTTP Server was successful, that JDBC is properly configured to access DB2, and that WebSphere Application Server (WAS) is configured to support DB2 access using JDBC. Otherwise you might encounter problems with DB2 interacting with WebSphere Studio Asset Analyzer and not be certain of the cause of the problem.
Before configuring WebSphere Studio Asset Analyzer, you need to update IBM HTTP Server and WebSphere Application Server (WAS) to work with WebSphere Studio Asset Analyzer. After updating these companion products, you use both the WebSphere Studio Asset Analyzer ISPF panels and the browser-based user interface to complete the installation verification program (IVP) for WebSphere Studio Asset Analyzer.
WAS V4 vs. V5: You use the native deployment of ear files to configure WebSphere Studio Asset Analyzer for use with WAS 5. In contrast, you use the plugin method to configure WebSphere Application Server (WAS) Version 4 to access WebSphere Studio Asset Analyzer. This plugin method is known as the Alternate Configuration Option in WAS V4.
Before proceeding:
To configure WebSphere Studio Asset Analyzer, complete these tasks in the order shown:
IBM HTTP Server is a prerequisite product and must be installed and configured on your system. Before proceeding, ensure that HTTP Server is working properly and that it works properly with the other required products. Before you can use WebSphere Studio Asset Analyzer, you need to make additional configuration changes to IBM HTTP Server so that it can access the HTML files of WebSphere Studio Asset Analyzer and display them in your browser window.
To configure IBM HTTP Server, edit the server configuration file as follows:
EDIT /etc/httpd.conf Columns 00001 00072 # ServerInit /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:init_exit /usr/lpp/WebSphere/etc/was400.conf |
If your site guidelines require each user to log on with his or her own userid, then use the directive 'UserId %%CLIENT%%', which tells the server to require that the requester has a local MVS userid and password.
EDIT /etc/httpd.conf # # Default: %%CLIENT%% # Syntax: UserId (user name) # Example: # UserId PUBLIC UserId %%CLIENT%% # UserId %%CERTIF%% # UserId %%SERVER%% # UserId %%CLIENT%% |
If your site guidelines specify that all users share access with a single userid, such as UserId PUBLIC, then you must establish additional protection scheme directives for the WebSphere Studio Asset Analyzer application. Add these additional protection scheme directives to the configuration file preceding any Service directives that reference WebSphere Studio Asset Analyzer Web addresses.
EDIT /etc/httpd.conf
# ===============================================================
# Protection scheme for access to WebSphere Studio Asset Analyzer
# ===============================================================
Protection DMH_Prot {
UserId %%CLIENT%%
ServerId "WebSphere Studio Asset Analyzer"
AuthType Basic
PasswdFile %%SAF%%
Mask All
}
# If you are using WAS 4, add the following line:
Protect /dmh* DMH_Prot
# If you are using WAS 5, add the following line:
Protect /dmh-cgi* DMH_Prot |
# Exec /dmh-cgi/* /usr/lpp/dmh/bin/* # |
EDIT /etc/httpd.conf Columns 00001 00072 # Service /dmh /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:service_exit Service /dmh/* /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:service_exit Service /dmh2/* /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:service_exit # |
EDIT /etc/httpd.conf Columns 00001 00072 # AddType .svg image/svg ebcdic 1.0 # |
Use this section only if your installation configuration includes WAS for MVS. WAS for Windows is configured by the WebSphere Studio Asset Analyzer installation program on Windows.
WAS is a prerequisite product and must be installed and configured on your system. Before proceeding, ensure that WAS is working properly and that it works properly with the other required products. Before you can use WebSphere Studio Asset Analyzer, you need to make additional configuration changes to WAS, so that it can access the data in your database. You need to have the proper authority to edit the WAS configuration file.
Authority: The WAS userid might not have the authority to create and write to the /usr/lpp/dmh/log directory, or to write to the /usr/lpp/dmh/config/Common.cfg file.
The userid under which the WAS job runs must have write access to the /usr/lpp/dmh/log directory and to the /usr/lpp/dmh/config/Common.cfg file. The easiest solution is to change the owner of the directory and the file to the WAS userid by using the following commands:
chown WAS userid /usr/lpp/dmh/log chown WAS userid /usr/lpp/dmh/config/Common.cfg.
You might need to create the /usr/lpp/dmh/log directory if it does not exist.
To configure WAS V4, edit the configuration file (/usr/lpp/WebSphere/was.conf by default) as follows:
Ensure that the jdbcconnpool.dmh_jdbcpool.datasourcename property matches the datasource name from the JDBC DATASOURCE Name" field of the ISPF panel on page ***. The datasourcename property value should be of the form: jdbc/your-datasource-name. The figure below shows the default datasourcename of jdbc/DMHDB.
EDIT /usr/lpp/WebSphere/was.conf Columns 00001 00072 ################################################################ # Define the WSAA connection pool and datasource ################################################################ jdbcconnpool.dmh_jdbcpool.jdbcdriver=ibm.sql.DB2Driver jdbcconnpool.dmh_jdbcpool.connectionidentity=thread # # Change DB_LOC_NAME to the DB2 location name for the database jdbcconnpool.dmh_jdbcpool.databaseurl=jdbc:db2os390:DB_LOC_NAME # # "JDBC DATASOURCE Name" from the "Set up" option of "DMHINSTL" # If you specified DMH in the "Set up" option, the value for # the datasource property should be jdbc/DMHDB. jdbcconnpool.dmh_jdbcpool.datasourcename=jdbc/DMHDB |
WAS 5.1 or later is required.
Restriction: The application server must have Java 2 security disabled.
To configure WAS V5, do the following steps from the WAS Admin Console:
After you have completed the required configuration updates for IBM HTTP Server and WebSphere Application Server, as described in Configuring companion products, you need to perform the following tasks:
You configure WebSphere Studio Asset Analyzer and set up the database by using the WebSphere Studio Asset Analyzer installation configuration utility. Comprehensive F1 help is available for all product ISPF panels. You must run the Setup Option 0 step regardless of whether your install configuration includes WAS for MVS or WAS for Windows. Fill in the appropriate values for your configuration on MVS and during the Windows product install.
Start the utility by doing the following steps:
EX 'yourHLQ.SDMHREXX(DMHINSTL)'
Here is an example; assuming DMH.STUDIO is yourHLQ:
EX 'DMH.STUDIO.SDMHREXX(DMHINSTL)'
To set up WebSphere Studio Asset Analyzer and to create and configure the DB2 database, complete the following tasks in the order shown:
Ensure that DB2 is started before proceeding.
To define the defaults for your site, use the Set up panel on the WebSphere Studio Asset Analyzer ISPF interface. Select Option 0 (Set up) on the Install panel. On the Set up panel, enter values for each field as appropriate for your site.
Help: To view help that is specific to each field, position your cursor on a field and press F1.
WebSphere Studio Asset Analyzer supports limited customization of the ISPF data set names that it uses. When you use the Set up panel, you can specify the high-level qualifier of these ISPF data sets. By default, the data sets have the following names:
where &hlqispf is the high-level qualifier for your ISPF data sets.
You must update source files for any other customization of the ISPF data set names. To use some other set of ISPF data sets, edit the following files:
yourHLQ.SDMHCNTL(DMHPRCQU)
In this file, locate the statements that contain DD definitions for ISPMLIB, ISPSLIB, ISPPLIB, and ISPTLIB, and then make the appropriate changes to data set names.
The following help panels show the fields filled in:
------------------- WebSphere Studio Asset Analyzer -------------
Set up: HELP
More: +
High-level qualifier of user DSN . : USERTMP
This is a qualifier to which all users of WebSphere Studio Asset
Analyzer need CREATE access. Temporary files are created under
this qualifier.
High-level qualifier of ISPF. . . . : ISP
HFS base directory . . . . . . . . : /usr/lpp/dmh
This is the directory on Unix System Services where the WebSphere
Studio Asset Analyzer files are stored. All users should have READ
access to this directory and its sub-directories. The access
permissions are created by SMPE during installation.
HFS temporary directory . . . . . . . . .: /usr/lpp/dmh
This is the directory on Unix System Services where the WebSphere
Studio Asset Analyzer logs and temporary files are stored. All users
should have READ/WRITE access to this directory and its sub-directories.
If the directory does not exist, it will be created.
If you do not specify a value, the HFS base directory is used.
DB2 run-time library . . . . . . . : DSN710.SDSNLOAD
LE run-time library . . . . . . . : CEE.SCEERUN
HLASM library . . . . . . . . . . . :
Required only if assembler source is to be scanned. |
--------------Server settings----------------
WebSphere Server Host Name. . . . . . . . . . . : ipname
Name or IP address of the HTTP Server under which
WebSphere Studio Asset Analyzer runs.
WebSphere Server Port . . . . . . . . . . . . : 80
Port number of the HTTP Server under which
WebSphere Studio Asset Analyzer runs.
Is the WebSphere Server a secure server ? N
Whether or not the HTTP Server under which WebSphere Studio Asset Analyzer
runs is using SSL (Secure Socket Layer).
JDBC DATASOURCE Name. . . . . . . . : DMHDB
Name under which data is accessed through JDBC. This value
must match the value defined in the WebSphere Application
Server configuration file in the statement:
jdbcconnpool.default_jdbcpool datasourcename=jdbc/DMHDB
Administrator userids . . . . . . . :
TSO userids given the authority to perform administrative
functions, such as deleting definitions. Specify * to
allow all users to access these functions.
--------CGI settings------------------------
CGI Host Name . . . . . . . : ipname
Name or IP address of the Server under which the CGI runs
CGI Port. . . : 80
Port number of the server under which the CGI runs
Is the CGI Server a secure server ? N
Whether or not the CGI Server is using SSL (Secure Socket Layer).
Server CGI alias Name . . . . . . . : dmh-cgi
Alias name associated with the CGI files (normally "dmh-cgi"), as defined
in the HTTP server configuration file. For example, if the httpd.conf
has this entry:
Exec /dmh-cgi/* /usr/lpp/dmh/bin/*
you must set the value to this string:
dmh-cgi
--------Distributed data settings-----------
Scanning Distributed Assets . . . . : Y
Whether or not you are planning to scann "distributed assets" that are
located on machines other than this machine.
Distributed Scanner Host Name. . . : NTservIP
Name or IP address of the Server where the distributed assets will be
scanned. If your leave this blank, it will not be possible to view the
source files for the distributed assets from within
WebSphere Studio Asset Analyzer.
Distributed Scanner Port. . . : 80
Port number of the server where the distributed assets will be
scanned.
Is the Distributed Server a secure server? N
Whether or not the server where the distributed assets will be
scanned is using SSL (Secure Socket Layer). |
cobolOptions = DTR,PGMN(LU),NOADV,ARITH(EXTEND)If you use the Common.cfg fields to provide options, do not specify any options on the ISPF panel fields. If you do, only the options that you specify on the panel are used.
Database name . . . . . . . . . . . . . . . . : DMHDB
Name of the database that is associated with WebSphere Studio Asset
Analyzer.
Buffer pools:
Buffer pools that are used for the database indexes, table spaces, and
temporary database.
Indexes . . . . . . . . . . . . . . . . . : BP1
Table spaces . . . . . . . . . . . . . . : BP2
Database and Temporary Database . . . . . : BP7
LOB Table spaces . . . . . . . . . . . . : BP8
DB2 table space prefix . . . . . . . . . . . : DMHTS
The prefix for the table spaces that are created by WebSphere Studio
Asset Analyzer. A three-character suffix is appended to this prefix
value.
High-level qualifier for the tables . . . . . : DMH
The qualifier for tables.
DB2 subsystem name . . . . . . . . . . . . . : DSN1
Name of the DB2 subsystem where the database resides.
DB2 location name . ..... . . . . . . . . : STLEC1
Location of the DB2 database subsystem on the host machine
DB2 plan prefix . ..... . . . . . . . . : DMH
The prefix for DB2 plans
Create global temporary database? . . . . . . : Y
Specify whether a global temporary database needs to be created ("Y")
or whether one already exists ("N"). Only one temporary database can
be created on a DB2 subsystem, but one must exist for WebSphere Studio
Asset Analyzer to be configured correctly. You must set this value to
"Y" if no global temporary database exists.
Global temporary database name . . . . . . . : DMHTMPDB
The name of the temporary database to create if it is
necessary to create one, or the name of the database
if one already exists. This value is mandatory if
you set the flag above to "Y", or if it is necessary
to create a new temporary table space.
Create global temporary table space? . . . . . . : Y
Specify whether a global temporary table space needs to be
created ("Y") or whether one already exists ("N"). If you
have an existing temporary table space in an existing
temporary database, you can set this value to "N";
if you do not, you must enter "Y", so that WebSphere Studio Asset
Analyzer can create a new temporary table space.
Global temporary table space name . . . . . . . : DMHTMPTS
The name of the temporary table space to create, if it is
necessary to create one. This field is mandatory if
you set the flag above to "Y". |
Press F3 to process and save the settings.
Before you create the database, you must have the JDBC environment variables set properly. If the default setup for the userid that you are using is not already set up to access JDBC from the command line, do the following steps to set the environment variables:
This is an example of completed export commands in the file:
export STEPLIB=DSN710.SDSNLOD2:DSN710.SDSNLOAD:WAS401.SBBOLOAD export LIBPATH=/usr/lpp/db2/db2710/lib export CLASSPATH=/usr/lpp/db2/db2710/classes/db2j2classes.zip export DB2SQLJPROPERTIES=/etc/db2sqljjdbc.properties
The DB2 userid and password are not captured by the ISPF set up panels. You must manually update the configuration file with this information. To make this update, do the following steps:
username = DBUSER password = DBPW
username = adminid password = adminpassword
Hint: Use a userid that has SELECT, UPDATE, DELETE, and INSERT authority for the WebSphere Studio Asset Analyzer tables and has SELECT authority to various catalog tables, such as SYSIBM.SYSTABLES and SYSIBM.SYSSYNONYMS. The DB2 password is encoded when you save the file.
Tip: When the web server is started, the WebSphere Studio Asset Analyzer servlet encrypts any password stored in the Common.cfg file. Therefore, the userid for the web server must have the proper authority to update Common.cfg. To allow the web server to write to the file, change the permissions for the file by using the chmod command or some other method.
Follow the instructions in this section only if you do not have an existing WebSphere Studio Asset Analyzer database. If you have an existing database, you need to upgrade it, as described in the following chapters:
Ensure that you stop the HTTP Server before proceeding. To create the database, follow these steps:
A JCL stream is presented in an editor. The JCL uses program DMHTEP2 to submit the DDL to create the database with all associated tablespaces, tables, and indexes. There are database COMMIT statements at regular intervals in the input stream. You might need to change some of the following entries on the input stream:
Thus the only time that DB2 will use the FREEPAGE setting is if the database is REORGed. As a result, the CREATE INDEX . . . FREEPAGE value might never get used. If, however, there is a policy to REORG all DB2 tables at regular intervals and you have very limited DASD space, the DBA might want to change this value to 0 or 20. In addition, in an environment of constrained memory, the DBA might want to set the SECQTY to 20 percent of the primary quantity.
DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=0
***INPUT STATEMENT: CREATE DATABASE DMHDB DMHSTOGR SYSDEFLT
BUFFER POOL BP0;
RESULT OF SQL STATEMENT:
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
CREATE SUCCESSFULTo customize and submit a job to bind the DB2 packages and plans, do the following steps:
| Unedited Version | Edited Version |
|---|---|
BIND PLAN(DMHP0700)
QUALIFIER(DMH) -
PKLIST(*.DMH.DMHDCOM -
*.DMH.DMHDROL -
*.DMH.DMHD233 -
. . . |
BIND PLAN(DMHP0700) -
QUALIFIER(DMH) -
PKLIST(DMH.DMHDCOM -
DMH.DMHDROL -
DMH.DMHD233 -
. . . |
When you create a DB2 database, only you have access to it. To make it accessible to other users, you need to grant them the privilege to access its tables, packages, and plans. The job that you submit in this task grants public access to the database to all users, unless you choose to modify the job to restrict access to certain users. The permissions that you grant persist even if you later drop and recreate the database, because DB2 keeps its own record of access rights. Therefore, you need to resubmit this job only if you need to modify privileges.
To customize and submit a job to grant DB2 privileges, do the following steps:
***INPUT STATEMENT: GRANT ALL ON PACKAGE DMH.DMHDCOM TO PUBLIC;
SQLWARNING ON GRANT COMMAND, EXECUTE FUNCTION
RESULT OF SQL STATEMENT:
DSNT404I SQLCODE = 562, WARNING: A GRANT OF A PRIVILEGE
WAS IGNORED BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM
THE GRANTOR
DSNT418I SQLSTATE = 01560 SQLSTATE RETURN CODE
You can ignore this condition.
Source Configuration Management (SCM) products manage the complete lifecycle of components used to create a software application. WebSphere Studio Asset Analyzer supports the following SCMs:
If you want your users to be able to take an inventory of source that is under an SCM, you must first configure the SCM by using the WebSphere Studio Asset Analyzer ISPF interface. Each SCM that you configure will appear on the inventory wizard (from the browser interface) as a scan type. The SCMs that you choose not to configure will not appear as a choice for a scan type, and your users will not be able to scan source from those SCMs. To configure the SCMs appropriate for your system, do the following steps:
SERENA.CMNZMF.V5R3M3.LOAD
SERENA.SERCOMC.V5R4M7.LOAD
Restriction: WebSphere Studio Asset Analyzer currently supports only the RPC ChangeMan interface, not the XML interface.
| Return code | Meaning |
|---|---|
| 0 | The job ran without errors. |
| 8 | Check the SQL code. If the SQL code is -803, the SCM was already configured |
Computer Associates International Inc. (CA) provides AllFusion CA-Panvalet for z/OS and OS/390 (Panvalet(R)). Panvalet is a software change and configuration management solution. If you use Panvalet to manage your source assets, you can configure WebSphere Studio Asset Analyzer to interface with your Panvalet libraries through a combination of installation parameters and user-supplied access routines.
The access routines that you need to supply to have WebSphere Studio Asset Analyzer interface smoothly with Panvalet libraries provide the following functions:
You must construct these routines to meet the specifications described in the following sections. Any deviation from these specifications can cause problems with the interface.
The access routine that retrieves a file list, referred to as EXIT-1, is used to retrieve a list of files that reside in a given Panvalet library. It must adhere to the following specifications:
The following example shows the REXX invocation that WebSphere Studio Asset Analyzer uses to invoke EXIT-1:
memberCount = DMHPANX1('USER.PANLIB, DMH.USER.T074720.M092256.D0125')
The access routine that retrieves the source in file for viewing, referred to as EXIT-2, is used to retrieve the source records from a single file in a given Panvalet library. It must adhere to the following specifications:
The following example shows the REXX invocation that WebSphere Studio Asset Analyzer uses to invoke EXIT-2:
recordCount = DMHPANX2('USER.PANLIB, MEMB01, DMH.USER.T085310.M150403.D0125')
The access routine that retrieves the source of a file and the source of included files for analysis, referred to as native library access, is used to directly read the contents of one or more files in one or more Panvalet libraries. It is invoked by the WebSphere Studio Asset Analyzer analyzers to efficiently access the source of a file and the source of any included files. It is invoked as metadata about the first file is gathered.
While the WebSphere Studio Asset Analyzer analyzers are collecting metadata about source assets, they periodically need to perform the following functions against Panvalet libraries. This access routine implements the logic to perform these functions.
This access routine must adhere to the following specifications:
The following COBOL example shows a typical dynamic CALL invocation that WebSphere Studio Asset Analyzer would use to invoke this access routine:
01 DMHPAN PIC X(06) VALUE "DMHPAN".
01 PARM-DATA.
05 PARM-LENGTH PIC S9(04) COMP.
05 PARM-IN-FUNCTION PIC X(01).
05 PARM-IN-DDNAME PIC X(08).
05 PARM-IN-FILE PIC X(10).
05 PARM-OUT-RECORD PIC X(80).
MOVE SPACE TO PARM-DATA
MOVE "O" TO PARM-IN-FUNCTION
MOVE "PANDD1" TO PARM-IN-DDNAME
MOVE"MEMB01" TO PARM-IN-FILE
CALL DMHPAN USING PARM-DATA
Panvalet ++INCLUDE statements are automatically handled during inventory scans, if the concatenation sets are generated automatically or if you construct them by using the WebSphere Studio Asset Analyzer user interface. However, if you construct the concatenation sets manually by editing members in the &UHLQ.INCL2 library on MVS, then you must add two, otherwise optional, space-delimited, parameters to the concatenation set records. The two parameters are RM= and RMDD=, which specify the resource manager and the resource DD name, respectively. The following parameter values are valid for an MVS installation of WebSphere Studio Asset Analyzer:
The following example shows a valid concatenation set content. It indicates that the first and third libraries to be searched are PDS libraries, while the second and fourth are PAN libraries.
DMH.APPL.COPYLIB1 DMH.APPL.PANLIB1 RM=PAN RMDD=PANINCL1 DMH.APPL.COPYLIB2 RM=PDS DMH.APPL.PANLIB2 RM=PAN RMDD=PANINCL2
Once you have satisfied these requirement and selected Panvalet for inventory scans, your users will process Panvalet libraries the same as they do PDS libraries.
To complete configuration of ChangeMan or SCLM, you need to edit the member yourHLQ.SDMHCNTL(DMHPRCQU), shown below, and remove the comment character from the appropriate DD statements. Use the comments in the JCL as your guide. TEMPLC is used for both ChangeMan and SCLM. The other DD statement apply only to one of the SCMs, as noted in the JCL comments.
//*-----------------------------------------------------------------* //* Uncomment the following DD for ChangeMan and/or SCLM support //*-----------------------------------------------------------------* //*TEMPLC DD DSN=&&TEMPLC,DISP=(MOD,PASS), //* SPACE=(133,(5000,10000)),UNIT=SYSDA, //* DCB=(DSORG=PS,RECFM=FB,LRECL=133) //*-----------------------------------------------------------------* //* Uncomment the following DD for ChangeMan support //*-----------------------------------------------------------------* //*RPCTRACE DD DUMMY //*-----------------------------------------------------------------* //* Uncomment the following DDs for SCLM support //*-----------------------------------------------------------------* //*ISPCTL1 DD DISP=NEW, //* SPACE=(CYL,(1,1)),UNIT=SYSDA, //* DCB=(LRECL=80,BLKSIZE=800,RECFM=FB) //*ISPLOG DD SYSOUT=*, //* DCB=(LRECL=120,BLKSIZE=2400,DSORG=PS,RECFM=FB) //*ISPMLIB DD DSN=&DMHISHLQ..SISPMENU,DISP=SHR //*ISPSLIB DD DSN=&DMHISHLQ..SISPSENU,DISP=SHR //*ISPPLIB DD DSN=&DMHISHLQ..SISPPENU,DISP=SHR //*ISPPROF DD DSN=&&TEMPLIB3,DISP=(NEW,PASS), //* SPACE=(CYL,(1,1,5)),UNIT=SYSDA, //* DCB=(LRECL=80,BLKSIZE=19040,DSORG=PO,RECFM=FB) //*ISPTLIB DD DSN=&&TEMPLIB1,DISP=(NEW,PASS), //* SPACE=(CYL,(1,1,5)),UNIT=SYSDA, //* DCB=(LRECL=80,BLKSIZE=19040,DSORG=PO,RECFM=FB) //* DD DSN=&DMHISHLQ..SISPTENU,DISP=SHR //*-----------------------------------------------------------------*
There might be situations and conditions in your shop that necessitate your making changes to the default configuration of the analyzers that WebSphere Studio Asset Analyzer uses to scan and analyze your assets. You can use the instructions in this section to update the settings for the indicated analyzers.
By default JCL analysis uses the libraries in an associated concatenation set to resolve INCLUDE and PROC statement references. The analyzer handles JCLLIB ORDER=(library1 [ [ ,library2 ] ... ] ) statements in the same manner as JES. To wit, the libraries listed are prepended to the concatenation set list, and the resulting list is used to resolve references.
However, if you have security requirements that deny users access to the JCLLIB members, the JCL analyzer fails. To address this situation, you need to configure the JCL analyzer to allow your users to analyze a JCLLIB ORDER statement but ignore the library list, thus using only what is specified in the associated concatenation set to resolve included statements.
To configure the JCL analyzer (DMH4000) to ignore the libraries found, set the ignore JCLLIB parameter (-i) by following these steps:
This change affects all JCL scans.
All source scanning performed by WebSphere Studio Asset Analyzer is processed as batch jobs created through the browser and submitted by the HTTP server. The default job card that is provided to the browser clients resides in the file yourHLQ.SDMHREXX(DMHPARMS). You should edit this file and update the DMHJBDF1 through DMHJBDF4 lines with appropriate parameters and settings. The following job card is the initial default:
/***** Job Cards for building JCL ***/ DMHJBDF1 = "00000000,'WEBSPHERE STUDIO AA'," DMHJBDF2 = "// CLASS=A,MSGCLASS=H,MSGLEVEL=(1,0)," DMHJBDF3 = "// REGION=4M" DMHJBDF4 = "//* DEFAULT JOB CARD"
To edit the job card and have your changes preserved, do the following steps:
//FOO1 JOB ,MSGLEVEL=(1,1),CLASS=K,use the following for DMHJBDF1:
DMHJBDF1 = ",MSGLEVEL=(1,1),CLASS=K,"The job name and JOB keyword are implied.
If you find that DMHPARMS does not exist, you have done the configuration steps out of order. Setup option 0 must be the first step in configuring WebSphere Studio Asset Analyzer.
Restart the HTTP Server before performing the next task. Verify that WAS starts correctly and that there are no WebSphere Studio Asset Analyzer exceptions in the WAS and HTTP logs.
Use this section only if you are installing WebSphere Studio Asset Analyzer on a machine on which you had previously installed an earlier version of WebSphere Studio Asset Analyzer.
Starting with version 4.1, WebSphere Studio Asset Analyzer no longer uses Net.data. If you are replacing a version earlier than 4.1 with version 4.1 or later, you should remove old WebSphere Studio Asset Analyzer Net.data macros by doing the following steps:
Use this section only if you have previously installed a version of the distributed scanner or WebSphere Studio Asset Analyzer runtime.
If you have previously installed a version of the distributed scanner or WebSphere Studio Asset Analyzer runtime on Windows or on AIX, you must uninstall that version before you can reinstall or install a newer version. Uninstall only the components that you have installed previously.
To uninstall your Windows server component, run the WebSphere Studio Asset Analyzer Windows uninstall program.
To uninstall your AIX server component, perform the following steps, where install_location refers to the location where you have installed WebSphere Studio Asset Analyzer, usually /usr/lp/dmh:
Use this section only if your users are going to work with distributed assets, or if your installation configuration includes WAS for Windows.
Windows NT: Follow these notes and instructions for WAS for Windows V5.1.
To enable the distributed asset support of WebSphere Studio Asset Analyzer or if your configuration is WAS on Windows, you must download, install, and configure the Windows server component by performing the following tasks:
To access the host database from Windows, you need to define an alias for the remote database. To define the alias, do the following steps:
After you define the alias, ensure that you can connect to the database by doing the following steps:
Restriction: If you are using DB2 UDB Runtime Client V8.1 for Windows, you must install fixpack 6 to avoid communication problems with WAS.
You can access WebSphere Studio Asset Analyzer at this point only if your installation configuration includes WAS for MVS. If your installation configuration includes WAS for Windows, you must install the Windows component of WebSphere Studio Asset Analyzer before using the browser interface.
To access WebSphere Studio Asset Analyzer, do the following steps:
http://<hostname>/dmh
where
<hostname> is your server's name such as www.ibm.com or www.ibm.com:9080
You are prompted with a system logon.You might be prompted twice.
The WebSphere Studio Asset Analyzer interface opens at the Home page. Verify that there is a timestamp, such as Wednesday, August 13, 2003 5:30:28 PM PDT, in the bottom right corner of this page. If no timestamp appears, WebSphere Studio Asset Analyzer is not accessing the database properly and other WebSphere Studio Asset Analyzer operations will fail. The most likely cause of this problem is with JDBC. To determine the cause of the problem, check the logs that were produced when you started WAS and the HTTP Server. In particular, look for DB2 connection errors in those logs, such as messages indicating that JDBC is not mounted, is not configured properly, or is otherwise not communicating properly with DB2. Correct any errors before proceeding.
To download the Windows Server Component installation code, do the following steps. Use the WAS from which you plan to run the scanner for distributed assets.
The Windows machine to which you download the install program must be one that has access to the distributed source code that you would like to scan.
After you have downloaded the InstallShield executable, do the following steps to install the component:
Tip: The installation path cannot have any blanks in the name, such as c:\Program Files\dmh.
To configure the Windows Server Component, you need to edit the Admin.cfg configuration file located in the assetloc/config subdirectory. It is strongly recommended that you create a backup copy of this configuration file before you open it in an editor. For in-depth configuration information for Admin.cfg, refer to the help topic titled "Setting the schedule and scanning roots". You can access this help topic by clicking Taking an inventory ->Taking an inventory of distributed assets ->Setting up scanners to take an inventory ->Setting the schedule and scanning roots.
If you install a new version of the Windows server component, you must customize the new version of the configuration files, just as you did for the previous version. Do not overwrite the new version with an old version. Use caution: if the you make a mistake in this customization process, you can cause existing artifacts, those that were previously scanned, to be deleted.
WebSphere Studio Asset Analyzer initially sets the maximum heap size used by the Java virtual machine to 500Mb. Out-of-memory errors can occur while scanning distributed assets, if the Windows virtual memory page size is set to a value less than 500Mb. If the Java virtual machine attempts to allocate more than the page size, it returns a C++ error indicating an abnormal program termination. The solution is to set the Windows virtual memory page size to a value greater than 500Mb. The recommended size is equivalent to 1.5 times the amount of RAM on your system. To change the Windows virtual memory page size, do the following steps. You must be logged on to Windows as an administrator to perform this procedure.
The WebSphere Studio Asset Analyzer distributed file system scanner supports the scanning of AIX file systems through the use of any network directory mapping technology, such as SAMBA, to map an AIX directory onto a Windows NT drive.
On AIX file systems, you can define a soft link in a directory to some other directory. WebSphere Studio Asset Analyzer scans the mapped directory as it does any other directory. When an AIX file system contains cyclic soft links, the file system scanner scans the same code over and over (for up to 1000 levels). For example, if directory A has a soft link to Directory B and B has a soft link to A, then the file system scanner will scan A then A/B then A/B/A then A/B/A/B, and so on.
When scanning AIX, verify that soft links have no cyclic referencing.
Use this section only if your users are going to work with distributed assets, or if your installation configuration includes WAS for AIX.
Prerequisites:
The files that are provided for the AIX configuration are the following installation files:
After you have completed the steps in the following subsections, you can run the WebSphere Studio Asset Analyzer distributed scanner by doing the following steps:
Ensure that you have the proper access to the product database on MVS by doing the following steps to connect to MVS from DB2:
DB2 CATALOG TCPIP NODE name REMOTE host SERVER 446 OSTYPE MVSFor example:
db2 catalog tcpip node v33ec104 remote v33ec104.svl.ibm.com server 446 ostype mvs
DB2 CATALOG DB name [AS alias] AT NODE node_name AUTHENTICATION SERVERFor example:
db2 catalog db STLEC1 as STLEC4 at node v33ec104 authentication server
Copy and install the provided files by doing the following steps:
Install the proper JVM properties in WAS by doing the following steps:
Install the JDBC provider by doing the following steps:
Install the WebSphere Studio Asset Analyzer Web application into WAS by doing the set of steps that is appropriate for your installation.
If you are installing the scanner only, doing the following steps:
If you are installing the run time, doing the following steps:
To install the online help for the product, do the following steps:
To start the distributed scanner, do the following steps:
alrun.sh
Tip: The shell that you use to run the distributed scanner must contain the environment setting that is required for DB2 access. These settings are located in the db2profile script that is located in the DB2 user home-directory/sqllib. The default DB2 user, usually called db2inst1, has this setting in its profile. You can move to this user by using the command su - db2inst1, or by importing the settings of the db2inst1 user shell to your own shell.
You need WAS 5.1 or later to use WebSphere Studio Asset Analyzer Web Services; older versions of WAS are not supported.
If you require external programmatic client access to the WebSphere Studio Asset Analyzer inventory, you need WebSphere Studio Asset Analyzer Web Services to be available. To make these services available, install an additional enterprise application that is provided with WebSphere Studio Asset Analyzer by doing the following steps:
With WAS on Windows: Set the local or server path, depending on whether your downloaded the ear file to your local workstation or server, respectively.
To verify that WebSphere Studio Asset Analyzer was successfully installed and configured, you run an installation verification program (IVP) that uses a sample PDS library and a sample CICS region, both of which are provided with the product.
First, you work with WebSphere Studio Asset Analyzer ISPF panels to load a logical CICS region. If you have installed the Windows server component, you must use the Crawler to load an EAR file. Then you access WebSphere Studio Asset Analyzer from your workstation browser to complete the IVP. During verification, you complete the following steps:
To help you verify that WebSphere Studio Asset Analyzer recognizes CICS regions and includes associated transactions in the database inventory, WebSphere Studio Asset Analyzer provides a logical CICS region. Use the DMHINIT utility by running the TSO command EX 'yourHLQ.SDMHREXX(DMHINIT)' to load the logical system into the database.
To access the main options panel and load the logical CICS region, do these steps:
EX 'yourHLQ.SDMHREXX(DMHINIT)'
You will verify that the CICS components loaded successfully when you complete section Verifying component counts.
To take an inventory of PDS members, you use the WebSphere Studio Asset Analyzer browser interface and a sample PDS library.
To access WebSphere Studio Asset Analyzer, do the following steps:
http://<hostname>/dmh
where
<hostname> is your server's name such as www.ibm.com or www.ibm.com:9080
You are prompted with a system logon.
You might be prompted twice.
If you do not see the Inventory menu, the userid that you used does not have administrator authority.
To complete taking the inventory, do these steps:
For IVP, WebSphere Studio Asset Analyzer provides a sample library yourHLQ.SDMHSSRC that includes COBOL, Assembler, PL/I, and JCL members. During the inventory phase, WebSphere Studio Asset Analyzer performs the following operations:
To take an inventory of the library yourHLQ.SDMHSSRC, complete the following steps in the Inventory wizard:
The inventory scan takes several minutes to complete.
To check the progress of your scan, click Database -> Analysis queue. The Database status - Information page opens. This page contains the status of assets that have been scanned into the inventory database.
The highlighted line labeled Inventory collection requests in-progress shows how many members are yet to be scanned into the inventory database. By refreshing this window, you see the values for this line change.
If you monitor the status of this job and check the return code value on MVS, it should complete with RC=0. In general however, any job that you submit that generates a return code value greater than zero has encountered a problem. You should investigate and correct the error.
To view the assets that you scanned during the IVP, click Explore -> MVS assets.
When you take an inventory of the verification sample, the information about the sample CICS region and PDS members is loaded into the product DB2 database. To verify that the information in the database is correct, you need to check the counts for the sample components.
Tip: Your counts will differ from those shown here if you have performed any scans besides exactly what was outlined in the previous section. For example, if you have scanned any Distributed assets, your counts will not be the same as those shown here.
To check the counts, do the following steps:
| Common assets | Total |
|---|---|
|
|
| Run time | Total | Program | Total | Data | Total |
|---|---|---|---|---|---|
|
|
|
|
|
|
If you have installed the Windows server components, give your Windows administrator the following instructions:
When you take an inventory of the verification sample, the information about the sample components is loaded into the product DB2 database. To verify that the sample information in the database is correct, you need to check the counts for the sample components. To further check the counts after you finish scanning the verification sample, do the following steps:
| Common assets | Total |
|---|---|
|
|
| Containers | Total | Java | Total | Web | Total |
|---|---|---|---|---|---|
|
|
|
|
|
|
| Other | Total | WebSphere | Total |
|---|---|---|---|
|
|
|
|
The information that you scanned into the database during verification is intentionally retained. After you successfully complete the IVP, you should reset the database to its original installation state. Otherwise, information about the sample library is included in results when WebSphere Studio Asset Analyzer is used in production.
To reset the database to its initial state, use the Database Clean Utility (a DB2 batch job that runs program DSNTEP2) to process dynamic SQL DELETE statements for all IVP-generated rows in the database tables. Do the following steps:
***INPUT STATEMENT: DELETE FROM DMH.DMH_CMPNT_NUM_ATTR;
SQLWARNING ON DELETE COMMAND, PREPARE FUNCTION
RESULT OF SQL STATEMENT:
DSNT404I SQLCODE = 100, NOT FOUND: ROW NOT FOUND FOR FETCH,
UPDATE, OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE
DSNT418I SQLSTATE = 02000 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXRSTD SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = -160 0 -1 -1 0 0 SQL DIAGNOSTIC
INFORMATION
DSNT416I SQLERRD = X'FFFFFF60' X'00000000' X'FFFFFFFF'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
You can ignore this condition.
The default configuration for WebSphere Studio Asset Analyzer allows all users to access all functions. If you want to limit which users have the ability to perform administrative tasks, such as deleting components, deleting the projects of other users, and taking inventory, specify their TSO userids in the "Administrator userids" field of the Set up panel.
After saving your changes, you must restart WebSphere for the changes to take effect.
This concludes the configuration and installation verification for WebSphere Studio Asset Analyzer. See the following chapter for information on migrating from earlier releases of WebSphere Studio Asset Analyzer. See the softcopy manuals and online help for further information on how to use the product.
The version of this configuration and migration guide from the Web is more up-to-date than the copy that is installed as part of the online help system for WebSphere Studio Asset Analyzer. If you have the proper authority, you can replace the copy in the online help with the copy from the Web. See the product readme file for instructions.
Use this section to solve problems that you might encounter while working with WebSphere Studio Asset Analyzer. Many problems can be attributed to an incorrect or incomplete installation or configuration of prerequisite products. Use the following tips to ensure that you have eliminated the cause of common problems:
Tips:
In the following descriptions, the bold, underlined text identifies the general area of the problem.
A compatible JVM could not be found on the machine where you are attempting to run the WebSphere Studio Asset Analyzer installation.
You need to install one of the compatible JVMs on the machine where you are installing WebSphere Studio Asset Analyzer by performing the following steps:
DB2 UDB V8.1 for Windows cannot communicate with WAS.
Install DB2 UDB V8.1 for Windows fixpack 6.
The JVM system property wsaaHome is not being set.
Reboot your computer. If rebooting does not solve the problem, do the following steps:
When the Java virtual machine attempts to allocate more than the page size, it returns this error.
Is your Windows virtual memory page size set to a value less than 500Mb? See Increasing the Windows virtual memory page size and the online help for more detail.
You are using a userid that is not identified as a WebSphere Studio Asset Analyzer administrator.
Identification is made via the dmhAdministrators property, which is configured during WebSphere Studio Asset Analyzer Windows installation and via theyourHLQ.SDMHREXX(DMHINSTL) step on MVS.
You might have to specify an HTTP port other than 80 when you configure WAS. Be sure to include that port number in the address that you use in the browser.
The AIX file system contains cyclic soft links.
See the description of cyclic soft links in Scanning distributed assets on AIX file systems from Windows.
One possible problem is that the Web Server Plugin has not been registered with HTTP Server. This is the case if you can access WebSphere Studio Asset Analyzer by the following address (with an port other than 80):
http://hostname:9080/dmh/DmhPageServlet?pagetype=searchall.
Do the following steps:
When you click Start -> Programs -> IBM WebSphere Studio -> Asset Analyzer -> Distributed Scanner, nothing happens. (You might see a command window for a fraction of second.) You probably have a problem with the Java path in your system.
To verify this problem, do one of the follow steps in a command window:
If you see a message similar to the above message or the following message, then Java is not installed correctly in your system: Error occurred during initialization of VM java/lang/NoClassDefFoundError: java/lang/Object.
To correct this problem, do one of the following steps:
java -jar ..\lib\wsaaconfigmgr.jar createBatchEnvFile -searchPath ..\config -configFile Common.cfg -batchPathname CommonEnv.bat
to
JDK_installdir/jre/bin/java -jar ..\lib\wsaaconfigmgr.jar createBatchEnvFile -searchPath ..\config -configFile Common.cfg -batchPathname CommonEnv.bat
where JDK_installdir can be WAS_INSTALL_DIR/java.
If you are installing WebSphere Studio Asset Analyzer Version 4.1.0 and have a product database that was loaded with Version 2, you need to instantiate a new database and rescan your existing inventory into the new database.
Before you drop your existing WebSphere Studio Asset Analyzer database, you should consider reviewing the data in particular areas. This review is optional; you need to consider the volume of data in your WebSphere Studio Asset Analyzer database. But a review can provide valuable information for future rescanning and baseline setup.
The following inventory components are those Recommended to review:
You can use screen prints and spreadsheets to capture information for reloading the database. If you have Microsoft Excel installed and available, you can capture results table data into spreadsheets by doing the following steps:
The spreadsheet provides a checklist of Container (called "Library" under earlier releases of WebSphere Studio Asset Analyzer) inventory candidates for the new WebSphere Studio Asset Analyzer 4.1.0 database.
This migration process is necessary due to schema changes in the design of the product database. The new schema provides substantial benefits, including the following new function and enhancements:
In addition, when you move to Version 4, you can take advantage of the following new enhancements:
Thus, moving to Version 4 gives you improved performance, better support for distributed assets, new function, and improvements to existing function.
After you have completeded your migration, return to Creating the database and follow the instructions. Ensure that the DROP DATABASE statement to remove the Version 2 database is activated before you create the Version 4 database.
If you are installing WebSphere Studio Asset Analyzer Version 4.1.0 and have Version 3.1.0 already installed, you need to use the Version 4.1 migration utility. (If you are migrating from Version 2, follow the instructions in Migrating from WebSphere Studio Asset Analyzer Version 2 before using the utility.)
To download the utility and the associated documentation, do the following steps:
After you complete these migration steps, you need to complete several configuration steps. Go to Configuring inventory analyzers and follow the instructions in that section and the sections that follow it to complete WebSphere Studio Asset Analyzer configuration.
References in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the responsibility of the user.
To obtain current service recommendations and to identify current product service requirements, always contact the IBM Customer Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket".
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the
IBM Director of Licensing IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1099 USA
For online versions of this book, we authorize you to:
You are responsible for payment of any taxes, including personal property taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you.
Your failure to comply with the terms above terminates this authorization. Upon termination, you must destroy your machine readable documentation.
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
ClearCase is trademark of Rational Software Corporation in the United States, other countries, or both.
Domino is a trademark of Lotus Development Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Panvalet is a registered trademark of Computer Associates International.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product and service names may be trademarks or service marks of others.