Export the HCL Compass Web
MBean configuration before you modify the MBean attributes. This practice
is important in case you make MBean configuration changes that produce
undesirable results and you must roll back to a known working configuration.
Before you begin
The HCL Compass Web
server components must be running to export the MBean configuration
settings.
About this task
The following variables are used in path names:
- CompassHome
- Directory where HCL Compass is
installed
- CQWebWASprofileHome
- Directory where your HCL Compass Web
server profile is installed
Procedure
- In a command prompt window, set the default directory to
the location of the HCL Compass Web
server support scripts for the wsadmin tool.
- Set the WAS_BIN variable to the location
of the wsadmin tool by using the syntax appropriate for your
shell.
- Start the wsadmin tool by specifying the HCL Compass Web
server profile name. The default profile name is cqwebprofile.
For example:
- %WAS_BIN%\wsadmin -profileName cqwebprofile
-
- $WAS_BIN/wsadmin.sh -profileName cqwebprofile
- Load the HCL Compass Web
server Jacl support scripts, which include the exportToFile and importFile commands,
into your wsadmin command shell:
wsadmin> source
teamAdminUtils.jacl
- Export the MBean configuration to a file that is outside
the HCL Compass Web
server installation directory.
Important: When you
run a Jacl script from the wsadmin command shell on Windows™, you can use forward
slashes /
in a path specification that you pass to the script.
Alternatively, if you choose to use backslashes \
, you must
escape each backslash character with an extra backslash.
You
can specify the same path specification and file name each time you
run the exportToFile command. The exportToFile command
detects when the file name exists in the directory and creates a new
version by appending the date and time to the file name.
What to do next
You can automate the procedure of periodically backing up the MBean configuration by creating an
AT job on Windows or a
cron job on the UNIX™ system or Linux™. For information about using the WebSphere® administrative scripting program, wsadmin, see the WebSphere Application Server Information Center.