This appendix shows the configurations of the different platform environments that are used during this project and the DayTrader application workload.

This appendix covers the following topics:

This section describes the environment in which we performed our tests. Figure B-1 shows our starting z/OS configurations. We used a DB2 10 for z/OS data sharing configuration that contains two members, D0Z1 and D0Z2, on LPARs SC63 and SC64. The processors on WTSCPLX2 were shared across all LPARs. We also built a WebSphere Application Server V 8.5 network deployment cell across these two LPARS and a cluster named MZSR014.

This section provides a description of the DayTrader application workload, which was used for our tests.

The IBM DayTrader performance benchmark sample provides a suite of IBM-developed workloads for characterizing the performance of the WebSphere Application Server. The workloads consist of an end-to-end web application and a full set of primitives. The applications are a collection of Java classes, Java servlets, JavaServer Pages, web services, and Enterprise beans that are built to open Java Platform, Enterprise Edition APIs. Together, these provide versatile and portable test cases that measure aspects of scalability
and performance.

Figure B-2 provides an overview of the DayTrader application workload.

The environment consists of the following elements:

Download your copy of the DayTrader application from the following web page:

Extract the files from the downloaded package.

Create the DayTrader database by completing the following steps. The skeleton JCL is prepared in the DayTrader package.

The DayTrader application installation script defines and installs the necessary resources in your installation of WebSphere Application Server. The script provides the following
installation options:

This is the user ID that is used to install the DayTrader application; in our example, we
used “mzadmin”.

This is the password for the user name.

If you are using global security or cluster installation, you are prompted by this option.

Now, you have lists of nodes to choose from. In our example, we used a cluster that is named “mzsr014””. You have the following options:

Choose from db2, oracle, or db2zos. You must choose “db2zos” when running against DB2 for z/OS server.

Enter the path for your type 4 driver path. In our installation, we used /usr/lpp/db2/d0zg/jdbc/classes/db2jcc.jar and /usr/lpp/db2/d0zg/jdbc/classes/db2jcc_lisence_cisuz.jar.

The location name of DB2 for z/OS. In our installation, “D0ZG” is the location name for our DB2 data sharing group.

The user ID that is used to connect to DB2 for z/OS. In our installation, we used “Rajesh”.

The password that is associated with the DB username.

After you are done with running scripts, go to your WebSphere Application Server administrative console. The DayTrader application should be installed, but it might not be started, as shown in Figure B-3, after the installation. You do not need to start the DayTrader
application now.

After running the scripts, the administration console of WebSphere Application Server opens. Click Resources → JDBC → JDBC Provider. You should see a new JDBC provider that is defined, as shown in Figure B-4.

Customize your data source settings so you can connect to DB2 for z/OS through the network, where the default installation for “db2zos” is the type 2 driver. In our example, we also performed the setup for sysplex workload balancing and a type 4 connection.

In the administration console of WebSphere Application Server, click Resources → JDBC → JDBC Provider. You see lists of data sources that are defined in your installation. You should see “TradeDataSource”; if not, check your scope match with a node that you specify at script or “All scopes”.

Figure B-5 shows the data source for our example.

Click TradeDataSource to access the settings for your DayTrader application data source. At the bottom, you find the Driver type, Server name, and Port number. Change Driver type to “4”, Server name to an IP address or the domain name for your DB2 for z/OS, and change the Port number to the DRDA service port. In our example, the settings are the ones that are shown in Figure B-6. In addition, we added two properties that are related to sysplex workload balancing in the data source custom properties.

Go to Servers → Application servers, and restart the application server in which the DayTrader application is installed. After restarting, navigate to Applications → Enterprise Application to verify that the DayTrader application started.

Your DayTrader application should be accessible from your browser. You must access your installation of the DayTrader application to finish your installation.

Navigate to Configuration (Re)-populate Trade Database to finish your installation. This populates your DayTrader database with fictitious users and stocks, as shown in Figure B-7. This step takes some time. You can close your browser, but you cannot see the status if you
do so.

In this section, we briefly explain how the DayTrader application works.

Click Go Trade! from the left menu pane of the window shown in Figure B-8.

The window that is shown in Figure B-9 opens. Click Log in (the Username and Password are already entered) to get started, or create an account by clicking Register With Trade.

After you log in to the DayTrader application, you see the DayTrader Home window (Figure B-10). Click Portfolio to start trading.

After you verify your installation (by clicking all the menus), you can start your workload by using the Test Trade Scenario.

Click Configuration in the left menu pane (shown in Figure B-8 on page 519) and then click Test Trade Scenario, as shown in Figure B-11. A new window opens. In that window,
click Reload.

You can use any load testing tool to create a workload to run by clicking Test Trade Scenario. For our test, we used Apache JMeter. This is a Java -based application that tests functional behavior and measures performance. It is available from the following web page:

Apache JMeter can load and performance test various server types, but because the DayTrader application provides the Test Trade Scenario, you can use it to test a scenario by using an HTTP request.