2.2 WSAA system or product administrator

---

The WSAA system or product administrator has the most responsibility when it comes to the successful deployment of WebSphere Studio Asset Analyzer.

You may have been selected (or even volunteered) to be the WSAA system or product administrator at your site. Irrespective of how you came to hold this job, this chapter will help you undertake your responsibilities with greater ease.

During the planning and installation phase, you work with a variety of groups to learn how WSAA will be installed at your site. We describe some of the basic tasks involved with installation in Appendix D, “WSAA installation notes” on page 195.

You are responsible for three major tasks:

• Planning for inventory collection

• Ongoing database maintenance

• Application support

You load the WSAA DB2 database once for each of the production source code libraries, CICS regions, and IMS subsystems at your site. After the database is populated with your site’s application portfolio, you can determine — along with your Change Management group — an appropriate schedule by which you can update the component information.

You work with your DB2 database administrator (DBA) to ensure the DB2 tables are tuned for optimal performance and response time.

You can read about the details involved with inventory collection, including database maintenance, in Chapter 3, “Collecting inventory” on page 51.

If you wish, you can expand your role to include application support. After all, who knows more about what was loaded into the WSAA database than you?

This familiarity gives you the ability to cross-train application development team members in the use of the product.

We describe each of these tasks in the following sections.

2.2.1 Planning for inventory collection

You must scan all of the components, and resolve any errors before the application development teams can use the contents of the database. You use the product’s Web interface to collect inventory for source code, including JCL and procs. You use ISPF panels to scan online resources, like CICS regions and IMS subsystems.

Planning and installation

When you collect inventory, you perform the following tasks:

• Determine libraries to scan and load the database

• Create a JCL job card used when submitting MVS jobs

• Scan PDS libraries of source, CICS, IMS, and JCL

• Scan CICS region information from the CSDs and load the results

• Scan IMS subsystems, datasets, transactions and control blocks

Post-installation activities

Afterwards, you look at the results of the various scans. You interpret the results of inventory collection with the help of the Database status pages. In the course of doing so, you:

• Find and fix scanning problems

• Modify inventory collection settings

• Rerun inventory collection to correct some problems

After this work is complete, you can turn the WSAA database over to the application development team members so they can begin to explore the inventory and analyze the impact of code changes.

2.2.2 Ongoing maintenance

Your secondary responsibility is to maintain the health of the database and to ensure it responds to the needs of the application development community in a timely and efficient manner.

Because the initial load of the WSAA database is merely a snapshot of your site’s application portfolio, you must make arrangements to update the contents of the database on a periodic basis.

Also, after you load the contents of any production source code library or online (CICS or IMS) resource, you must make sure your perform the necessary DB2 table maintenance. We describe these tasks in 3.9, “How and when to perform database maintenance” on page 107.

2.2.3 Application support

You can spend up to several weeks tracking down the information you need to load the database. You will spend several more days (or weeks) loading the WSAA DB2 database with your site’s production source code and online resources. During that time, you will find and fix various problems. You will undoubtedly encounter some anomalous behavior that will require the resources of others in your organization to help you correct. After all is said and done, your database will be loaded and it will reflect your site’s production application portfolio.

Whether you realize it or not, you have become an expert in most of the functions in WSAA. You now have the ability to cross-train application development managers (or project leaders) so that they can learn how to quickly explore the contents of the database.

You can develop the necessary handouts so that these team leaders can provide information about their applications to their development teams.

Tip 

Set up the appropriate form of communication (using a mechanism that is officially sanctioned at your location) to allow you to more quickly and easily handle problem detection and resolution.

---