#ManagedInstances type identifier column headers
Use the #ManagedInstances type identifier to handle bulk upload of application services.
The following list describes the type identifier column headers that you can use.
| Attribute column header | Description | Required |
|---|---|---|
| MANAGED_SERVICE_NAME | Specifies the common name that is used for the managed application service. | Required. |
| HOST | Specifies the host of the managed application service. | Required. |
| TARGET_UNIQUE_NAME | Specifies the short name that associated with the service. This name must match the service name of the Windows service. | Required. |
| TARGET_DISPLAY_NAME | Specifies the displayed name associated with the service. This field is a descriptive name for the service. | Required. |
| CREDENTIAL_RESOURCE_UID | Identifies the UID of the resource that is associated with the managed application service. | Optional. |
| NOTIFY_EMAIL | Specify recipients of the notification email. Separate multiple recipients with a comma (,), enclosing recipients in double quotes (""). Notifications will always be sent to the person who registered the service manager regardless of whether the field is populated or not. For example: "abc@example.com,def@example.com" | Optional. |
| RESTART | Specifies whether to restart the service after a reconfiguration. Acceptable values are true or false. If true, the service is restarted after configuration. | Optional. |
| MANAGED_SERVICE_TYPE | Specifies the type of service that you are managing. The types are windows-service for Windows services and windows-scheduled-task for Windows scheduled tasks. The default value is windows-service. | Optional. |
| CREDENTIAL_USER_NAME | Specifies the credential that is associated with the managed application service. | Optional. |
| ACTIVE | Specifies whether the service is managed by the service management agent. Acceptable values are true or false. If set to true, the service managed by the agent. If set to false, the service is not managed. Default value: true | Optional. |
Each CSV entry represents one managed application service instance. If the managed application service instance does not exist, the application service is created. If an application service exists, the application service is updated.
The system uses the HOST and TARGET_UNIQUE_NAME to determine if an application service instance exists.
Example 1
The following sample CSV file contains information about the managed application services:
#ManagedInstances
MANAGED_SERVICE_NAME,HOST,TARGET_UNIQUE_NAME,TARGET_DISPLAY_NAME,
NOTIFY_EMAIL,RESTART,MANAGED_SERVICE_TYPE,CREDENTIAL_USER_NAME,CREDENTIAL_RESOURCE_UID,ACTIVE
DB2 - DB2COPY1 - DB2-0,192.0.2.5,DB2-0,DB2 - DB2COPY1 - DB2-0,,false,windows-service,user1,IBM-PK06KHY,true In this example, the Windows service (DB2 - DB2COPY1 - DB2-0) is added.
If HOST and TARGET_UNIQUE_NAME already exists in the system, the existing application service will be updated.
The CSV file column headers are an unordered list. You can change the order of these column headers. However, do not change the name of these column headers.
The uploaded service belongs to the current Admin domain and are assigned to the current application manager of the bulk upload session.
Credential bulk upload
You can bulk upload credentials in the same CSV file.
If you are specifying related credentials in the same CSV file, use the #Credentials_v2 type identifier format. For more information, see #Credentials_v2 type identifier column headers. The ACCESS_MODE must be set to 1.
Example 2 - Specifying managed instances with credentials in the same CSV file
#Credentials_v2
ACCOUNT_UID,PASSWORD,ACCESS_MODE,RESOURCE_UID
user1, secret, 1, PIMQA
#ManagedInstances
MANAGED_SERVICE_NAME,HOST,TARGET_UNIQUE_NAME,TARGET_DISPLAY_NAME,
NOTIFY_EMAIL,RESTART,MANAGED_SERVICE_TYPE,CREDENTIAL_USER_NAME,
CREDENTIAL_RESOURCE_UID,ACTIVE
DB2 - DB2COPY1 - DB2-0,192.0.2.5,DB2-0,DB2 - DB2COPY1 - DB2-0,,false,
windows-service,user1,PIMQA,true