![]() ![]() ![]() ![]() ![]() ![]() |
This section describes how to create and configure a custom SSM.
A custom SSM can be created by making a copy of an existing SSM and then making a few modifications before running the ConfigTool. This is a fairly straight-forward process, because all configuration information is stored in modifiable text files. Once the custom SSM is created, the same files can be used to replicate it across multiple systems.
The out-of-box SSMs that can be copied for this purpose are the following:
For example, copy BEA_HOME
\ales30-ssm\java-ssm
to BEA_HOME
\ales30-ssm\custom-ssm
.
custom-ssm\config\java-ssm
directory to custom-ssm\config\custom-ssm.
BEA_HOME\ales30-ssm\custom-ssm\config\custom-ssm\ales-policies
directory and modify the default policies as follows:BEA_HOME\ales30-ssm\custom-ssm\config\custom-ssm
directory and add the following line to all-params.properties
:
my.custom.user = string, Enter the name of the custom user
BEA_HOME\ales30-ssm\custom-ssm\adm\myssm_config.properties
. Then make the following changes to myssm_config.properties.
ConfigTool.bat -check myssm_config.properties
to check the properties file.ConfigTool.bat -process myssm_config.properties
.
After creating a custom SSM as described above, perform the following steps to replicate it on another system:
custom-ssm
directory from the source to the destination system.myssm_config.properties
with the domain name, the correct path, and other variables.
![]() ![]() ![]() |