Tip:
Highlight text to annotate it
X
IBM Tivoli Composite Application Manager for J2EE V6.1, Manually
configuring a managed WebLogic server version 10.3.
Before you proceed, you must have these skills and knowledge:
- Basic skills for WebLogic Application Server and its directory structure
- A WebLogic server that runs with a JRockit Java virtual machine
- Knowledge of the ITCAM Data Collector GUI configuration tool
- Ability to configure the administrative instance by using the
ITCAM Data Collector GUI configuration tool
- Knowledge of Windows or Linux/UNIX operating system
When you complete this module, you should be able
to configure a data collector for any managed instance of a WebLogic Application Server manually.
For example, you can configure the data collector without
running the standard ITCAM configuration tool.
You must start from a clean state.
For example, the administrative instance must not be initially configured by ITCAM.
In this module, the instance is named AdminServer.
Also, ensure that no managed server is configured by ITCAM.
The server in this module is named managedserver1.
Start the AdminServer by using the script startWebLogic.cmd.
Try to configure AdminServer with ITCAM by using the standard script config_dc.bat.
If the script completes successfully, stop the AdminServer and
proceed with step two on the next slide.
If the standard script does not complete successfully, stop
the AdminServer and use the technote to manually create its ITCAM runtime directory.
The address of the technote is listed on the slide.
A template runtime directory is provided in the technote.
Afterward, you can proceed to the next step.
Do not start the AdminServer yet.
First, verify the current files of your AdminServer runtime directory.
In this example, the AdminServer runtime directory is <
DCHOME>\runtime\wls10.base_domain.myhostname.AdminServer\.
The initial listing of that directory looks like the 10
files in the screen capture, plus a custom subdirectory
that contains two more files, for a total of 12 files.
Now, back up the directory that is created in step two as a template.
You can use this directory for your future runtime configurations.
For example, you can archive it and back it up for future needs.
Duplicate this directory in the same location and rename it
by replacing AdminServer with managedserver1.
An example of a final directory name and location is
\runtime\wls10.base_domain.myhostname.managedserver1.
In this step, you work on the newly created runtime directory to adapt it for a managed server.
Go to the new managedserver1 runtime directory and rename the
only three files whose names contain the string AdminServer,
by replacing AdminServer with managedserver1.
Now, you must edit the contents of six files, the ones that are listed in this slide.
Replace all the internal occurrences of AdminServer with managedserver1.
Finally, update the file dc.properties with the JMX_PORT value that is used by your managed server.
In this step, you customize the startup script.
Identify the ITCAM section for the AdminServer.
It is located just before the line @REM START WEBLOGIC.
You can now duplicate it by appending the new,
duplicated section after the original one and replacing all the
occurrences of AdminServer with managedserver1.
Here is an example of an ITCAM section for an
AdminServer that you have to duplicate and customize for managedserver1,
as explained in the previous slide.
In the last step, edit the config.xml file by
ensuring that AdminServer and managedserver1 are listed in both AM Shutdown and AM Startup stanzas.
You can start the AdminServer by using the startWebLogic.cmd script.
You can start managedserver1 by using the script startManagedWebLogic.cmd with
the option managedserver1.
Now that you completed this module, you can configure
a data collector for any managed instance of a WebLogic
Application Server without running the standard ITCAM configuration tool.
You can help improve the quality of IBM Education Assistant content by providing feedback.