Custom profiles
You can use the manageprofiles.bat or manageprofiles.sh command to create or augment custom profiles.
This command is found in the app_server_root/bin directory.
To
install or run the manageprofiles command on Windows,
you must elevate your Microsoft Windows user account privileges by
using the runas command. Remember to put double
quotation marks around the manageprofiles command
and all parameters. For example:
runas /env /user:MyAdminName "manageprofiles.bat -create -profileName WBMON01 -templatePath C:\Program Files\IBM\WebSphere\AppServer\profileTemplates\wbmonitor\managed -wbmDBJDBCClasspath C:\Program Files\IBM\WebSphere\AppServer\jdbcdrivers\DB2" Purpose
This command creates IBM® Business Monitor custom profiles, which are managed by a deployment manager. It can also be used to augment existing custom profiles for each node you plan to add to the IBM Business Monitor server cluster. For examples, see the Examples section.Parameters
To create or augment a custom profile, use the manageprofiles command with the following parameters.| Parameter and value | Required? | Description | Comments |
|---|---|---|---|
| -create | Required for profile creation | Create a profile. | Do not use for profile augmentation. |
| -augment | Required for profile augmentation | Augment an existing profile. | Do not use for profile creation. Restriction: You cannot augment an IBM Business
Process Manager profile
with IBM Business Monitor.
|
| -templatePath app_server_root/profileTemplates/wbmonitor/managed | Required | The location of the IBM Business Monitor template for custom profiles. | |
| -profileName profile_name | Required for profile augmentation | The name of the profile. | A default name is supplied for profile creation if you do not provide one. |
| -cellName cell_name | Optional | The cell name of the profile. | The default is the cell name of the profile as defined by WebSphere® Application Server. |
| -nodeName node_name | Optional | The node name of the profile. | The default is the node name of the profile as defined by WebSphere Application Server. |
| Federating a custom profile | |||
| -federateLater true | false | If you set this parameter to true, you can federate the node later using the add_node command. | See "Add managed nodes" in the WebSphere Application Server information center for more information. | |
| -dmgrAdminUserName user_name | Required if you are federating the profile now and administrative security is enabled on the deployment manager | If administrative security is enabled on the deployment manager, specify a valid user name. | |
| -dmgrAdminPassword password | Required if you are federating the profile now and administrative security is enabled on the deployment manager | If administrative security is enabled on the deployment manager, specify a password for the user name. | |
| -dmgrHost dmgr_host_name | Required if you are federating the profile now | The machine where the deployment manager is running. The host name can be the long or short DNS name or the IP address of the deployment manager machine. | The default value is localhost. Specify a properly formed host name containing no special characters. Specifying this parameter directs the manageprofiles command to attempt to federate the custom node into the deployment manager cell as it creates the custom profile with the -templatePath parameter. The -dmgrHost parameter is ignored if you are creating a deployment manager profile or a stand-alone profile. If you federate a custom node when the deployment manager is not running or is not available because of security being enabled or for other reasons, the installation indicator in the logs is INSTCONFFAIL to indicate a complete failure. The resulting custom profile is unusable. You must move the custom profile directory out of the profile repository (the profiles installation root directory) before creating another custom profile with the same profile name. |
| -dmgrPort dmgr_port_number | Required if you are federating the profile now | The SOAP port of the deployment manager. | The default value is 8879. The value must be a positive integer. Specify this parameter and the -dmgrHost parameter to federate a custom profile as it is created. The deployment manager must be running and accessible. A connection to the deployment manager must be available in conjunction with the -dmgrHost parameter. |
| --isFederatedProfile true | false | Optional | Whether the system is a single server or network deployment. | This value sets the isFederated flag for the profile as defined by WebSphere Application Server. |
| Monitor Database configuration | |||
-wbmDBType DB2_DATASERVER | DB2UDBOS390 | Oracle11g | |
Optional | The type of database. | Use DB2_DATASERVER for connecting to DB2®. Use Oracle11g for connecting to either Oracle 10g or Oracle 11g. Use DB2UDBOS390 for connecting to DB2 for z/OS®. Use MSSQLSERVER_MICROSOFT for connecting to Microsoft SQL Server. |
| -wbmDBJDBCClasspath database_JDBC_classpath | Optional | The path to the JDBC driver for the database. | If wbmDBType is set to DB2_DATASERVER or DB2UDBOS390,
the default value is monitor_root/jdbcdrivers/DB2. If wbmDBType is set to Oracle11g, the default value is monitor_root/jdbcdrivers/Oracle. If wbmDBType is set to MSSQLSERVER_MICROSOFT, the default value is monitor_root/jdbcdrivers/SQLServer. |
manageprofiles.bat -create -templatePath "IBM\WebSphere\MonServer\profileTemplates\wbmonitor\managed" -profileName MyCustom1 -profilePath "IBM\WebSphere\MonServer\profiles\MyCustom1" -nodeName myNode01 -federateLater false -dmgrAdminUserName DMGR_USER -dmgrAdminPassword DMGR_PW -dmgrHost DMGR_HOST -dmgrPort DMGR_PORT -wbmDBType DB2_DATASERVER -wbmDBJDBCClasspath "IBM\WebSphere\MonServer\jdbcdrivers\DB2"manageprofiles.bat -create -templatePath "IBM\WebSphere\MonServer\profileTemplates\wbmonitor\managed" -profileName MyCustom1 -profilePath "IBM\WebSphere\MonServer\profiles\MyCustom1" -nodeName myNode01 -federateLater false -dmgrHost DMGR_HOST -dmgrPort DMGR_PORT -wbmDBType Oracle11g -wbmDBJDBCClasspath "IBM\WebSphere\MonServer\jdbcdrivers\Oracle"manageprofiles.bat -create -templatePath "IBM\WebSphere\MonServer\profileTemplates\wbmonitor\managed" -profileName MyCustom1 -profilePath "IBM\WebSphere\MonServer\profiles\MyCustom1" -nodeName myNode01 -federateLater false -dmgrAdminUserName DMGR_USER -dmgrAdminPassword DMGR_PW -dmgrHost DMGR_HOST -dmgrPort DMGR_PORT -wbmDBType MSSQLSERVER_MICROSOFT -wbmDBJDBCClasspath "IBM\WebSphere\MonServer\jdbcdrivers\SQLServer" manageprofiles.bat -augment -templatePath "IBM\WebSphere\AppServer\profileTemplates\wbmonitor\managed" -profileName MyCustom1 -federateLater false -dmgrHost DMGR_HOST -dmgrPort DMGR_PORT -dmgrAdminUserName DMGR_USER -dmgrAdminPassword DMGR_PW -wbmDBType DB2_DATASERVER -wbmDBJDBCClasspath "IBM\WebSphere\AppServer\jdbcdrivers\DB2" manageprofiles.bat -augment -templatePath "IBM\WebSphere\AppServer\profileTemplates\wbmonitor\managed" -profileName MyCustom1 -federateLater false -dmgrHost DMGR_HOST -dmgrPort DMGR_PORT -wbmDBType Oracle11g -wbmDBJDBCClasspath "IBM\WebSphere\AppServer\jdbcdrivers\Oracle"manageprofiles.bat -augment -templatePath "IBM\WebSphere\AppServer\profileTemplates\wbmonitor\managed" -profileName MyCustom1 -federateLater false -dmgrHost DMGR_HOST -dmgrPort DMGR_PORT -wbmDBType MSSQLSERVER_MICROSOFT -wbmDBJDBCClasspath "IBM\WebSphere\AppServer\jdbcdrivers\SQLServer" 