切爾斯基

Using Optimizeit with WebSphere 4.0 Advanced Edition

This tutorial explains how to integrate Optimizeit with IBM WebSphere 4.0 Advanced Edition. These instructions are for both Windows and Unix machines. Once you have integrated Optimizeit, you can attach to any Optimizeit tool without further integration.

Note: In this document <OptIt_Dir> is the directory where Optimizeit has been installed (for example on Windows, C:\Optimizeit\OptimizeitSuite), and <WebSphere_Dir> is the directory where the WebSphere application server has been installed (for example on Unix, /opt/sfw/websphere).

Note on using JDK 1.3 on Solaris machines with WebSphere 4.0: On Solaris machines, IBM WebSphere 4.0 is packaged with and uses by default JDK 1.3. But JDK 1.3 does not support the profiling interface (JVMPI) and so cannot be used with Optimizeit. In order to use Optimizeit with your WebSphere application server, you need JDK 1.3.1 or above. If you do not have JDK 1.3.1 installed, download the software from the Sun java website.

The following instructions explain how to configure WebSphere to work with Optimizeit.

1. On Windows machines only, copy the <OptIt_Dir>\lib\oii.dll file to the <WebSphere_Dir>\bin directory.
2. On Unix machines only, copy the <OptIt_Dir>/lib/liboii.so and <OptIt_Dir>/lib/libpri.so files to the <WebSphere_Dir>/bin directory.
3. Start the WebSphere Admin Service and then the WebSphere Administrative Console.
4. In the Administrative Console, select the node of the Application Server you want to profile with.
5. Select the server that you want to use (for example, Default Server). You will notice several tabs on the panel to the right.
6. Select the JVM Settings tab, and add <OptIt_Dir>\lib\optit.jar in the Classpaths field.

7. Scroll down and click Advanced JVM Settings to open the Advanced JVM Settings dialog box.
8. In the Command Line Arguments field, type -Xrunoii:filter=<OptIt_Dir>\filters\Websphere.oif
9. Check Disable JIT and type <OptIt_Dir>\lib\oibcp.jar in the Boot Classpath (Prepend) field.
10. Click OK to close the Advanced JVM Settings dialog box.

11. Click Apply to update the changes to WebSphere.

1. For Windows machines only: Using the Optimizeit Audit System selector from the Windows tray, select which of the Optimizeit tools (Profiler, Thread Debugger or Code Coverage) you currently wish to use with WebSphere.

Note: If you have previously installed Optimizeit products, you must quit the Audit System Selector supplied with those products, and start the Optimizeit Audit System Selector supplied with this tool.

2. For Unix machines only: Using the Optimizeit Audit System selector, select which of the Optimizeit tools you currently wish to use with WebSphere. The Optimizeit Audit System selector is a command located under <OptIt_Dir>/oiselector. It allows you to choose which Audit system should be run and which options should be used. In order to quickly configure, enter:
   <OptIt_Dir>/ oiselector -config
   This command starts an interactive configuration. More information is available when you type:
   <OptIt_Dir>/ oiselector -help
   Important: The configuration specified through the Audit System selector is stored in a file located under the HOME directory of the current user. For that reason, the oiselector command should be run as the same user as the one used to run the application server.
3. Once you have selected the Audit System to be used, restart your Application Server.

Once WebSphere is running with the Optimizeit Audit System, you can launch Optimizeit and attach to the virtual machine.

1. Ensure your application server is running, and that the application you want to profile is deployed and running.
2. On Windows machines only, right-click the Audit System Selector icon on the taskbar, and choose Open the Audit System Selector.

Select the tab for your chosen tool, and click Start.

3. On Unix machines, start Optimizeit.
4. Optimizeit opens the Edit Settings dialog box. Click OK.
5. Choose Program|Attach to open the Attach dialog box.
6. Verify the host name and port number, and click Attach.

The default values for host name (localhost) and port number (1470 for Profiler, 1471 for Thread Debugger, and 1472 for Code Coverage) will work in most instances.

7. When you are done monitoring activity with the application, detach Optimizeit from the application server (Program|Detach).

The application server is not affected by attaching and detaching Optimizeit.

1. Database configure

    Because you want to use JDB2 type2 driver, so you must have a DB2 client on the same machine with the websphere.

    If you want to connect to a remote DB2 database, you need configure a local database which reference to the remote database using DB2 client tool.

2. Start WebSphere

Because you used the JDBC2 driver, you need to run a script named db2profile to configure some environment parameter before you start the WebSphere.

 Normally you can find that script at the {$db2-user-home}/sqllib folder.  After you have run that script, you can start the WebSphere

3. Configure Database

       When you create JDBC providers, you should choose DB2 Legacy CLI-based Type 2JDBC Driver.    

   Ok, that all.

1. DB2 Driver version can't be lower than 8.1.6
2. set DB2_HOME\bin as lib path

1, “Servers” -> “Application Server” ->"server_name"->“Server Infrastructure”-> “Java and Process Management”->“Process Definition”-> “Java Virtual Machine”->   Add value “-Duser.language=en” to property “Generic JVM arguments”.->restart WebSphere.

2, Change IE to show English UI of WebSphere, open IE, and go to “Tools” -> “Internet Options” -> “General”-> “Language”.-> “Add”.a new item “en-us”, and move it on the top of the list.

Default JMS Provider: WebSphere Application Server V6 supplies a preconfigured J2EE Connector Architecture resource adapter implementation that can be used to communicate with a service integration bus. This resource adapter is installed as a fully-integrated component of WebSphere Application Server V6, at all levels of the WebSphere cell, and needs no separate installation steps. The administered objects for this resource adapter also implement the corresponding interfaces of version 1.1 of the JMS specification. This enables them to the be used by JMS clients for both the point-to-point and Publish/Subscribe messaging models.

Default JMS Provider Configuration UI: A user friendly configuration tool to help you avoid directly configuring the JMS JCA resource adapter for JMS; yeah, you can configure JMS JCA resource adapter directly for your application

SIB: A service integration bus, or bus, within WebSphere Application Server V6 is simply an architectural concept. It gives an administrator the ability to group a collection of resources together that provide the messaging capabilities of the bus. At runtime, the bus presents these cooperating messaging resources to applications as a single entity, hiding from those applications the details of how the bus is configured and where on the bus the different resources are located. yeah, SIB holds physical resource located for JMS and some other Service.

Provider is interface, SIB is implementaton

   ↓                                                         ↓

   ↓                                                         ↓

1. Using WebSphere Default JMS Provider with foreign bus connected to MQSeries, which illustrated above.
2. Using WebSphere MQ JMS Provider

Unlike the default messaging JMS provider, the WebSphere MQ JMS provider is not a J2EE Connector Architecture version 1.5 compliant resource adapter. It simply provides an implementation of version 1.1 of the JMS API, enabling JMS clients to communicate directly with WebSphere MQ.

Corbaname: corbaname::myhost1:9812/NameServiceServerRoot#ejb/webbank/Account

java.naming.provider.url=corbaloc:iiop:myhost.mycompany.com:2809 java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory

env.put(Context.INITIAL_CONTEXT_FACTORY, "com.somecompany.naming.TheirInitialContextFactory");
env.put(Context.PROVIDER_URL, "corbaname:iiop:myhost.mycompany.com:2809/NameServiceServerRoot");

boothost1:7278:BootstrapBasicMessaging

Servers -> Application Server -> server name -> Web Container -> Session Management: By default the value is 30. You can change it to -1(never time out) or 10000.

1. Stop WAS
2. Run “$WAS_HOME\cloudscape\bin\embedded\cview.bat”
3. Open the database in“$WAS_HOME\profiles\default\databases\EJBTimers\server1\EJBTimerDB”
4. delete data in table EJBTIMER_TASK
5. Restart WAS

By default, an application will start when the server starts. However, you may not want all the applications to start immediately, because the applications you no longer use consume resources, or you may not need to run them. The only way to prevent this is to disable the application from running on the server.

a. Select Applications -> Enterprise Applications

b. Click the application to open the configuration.

c. Select Target Mappings in the Additional Properties table.

d. Select the server for which you want to disable the application.

e. Deselect the Enable option and click OK.

f. Save the configuration.