IBM Concert Operate

https://www.ibm.com/docs/en/concert-operate/5.1.0
Admin
IBM Concert Operate is a solution that provides capabilities for IT operations management, including...
Tokens:2,062,887
Snippets:25,592
Trust Score:10
Update:3 months ago
Show doc for...
Tokens:
Raw
### Install and Start MongoDB

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=administration-deployment-planning-guide

Installs the MongoDB server and configures it to use small files before starting the service.

```bash
# yum install mongodb-server
# sed -i '/--smallfiles/!s/OPTIONS="/OPTIONS="--smallfiles /' /etc/sysconfig/mongod
# service mongod start

```

--------------------------------

### Example Output of Installation Phase Check

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=installation-gitops

This is an example of the output you might see when checking the installation phase. It indicates the current status and age of the installation.

```text
NAME                  PHASE     LICENSE    STORAGECLASS   STORAGECLASSLARGEBLOCK   AGE
ibm-cp-aiops          Updating  Accepted   rook-cephfs    rook-ceph-block          3m
```

--------------------------------

### Example: Start ObjectServer

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=fips-enabling-support-netcool-integration

Example command to start an ObjectServer named 'AGG_P' using its properties file located in `$OMNIHOME/etc/`.

```bash
$OMNIHOME/bin/nco_objserv -name AGG_P -propsfile $OMNIHOME/etc/AGG_P.props &
```

--------------------------------

### Example Installation Output

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=integrations-connecting-premises-probes

This is an example of the output you might see when checking the status of your Concert Operate installation.

```text
NAME          PHASE    LICENSE   STORAGECLASS STORAGECLASSLARGEBLOCK AGE
ibm-cp-aiops  Running  Accepted  rook-cephfs  rook-ceph-rbd          34h


```

--------------------------------

### Example: Start Bidirectional Gateway

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=fips-enabling-support-netcool-integration

Example command to start the bidirectional gateway using its properties file named 'AGG_GATE.props'.

```bash
$OMNIHOME/bin/nco_g_objserv_bi -propsfile $OMNIHOME/etc/AGG_GATE.props &
```

--------------------------------

### Start Installation Manager GUI

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=probes-installing-gateways-tivoli-netcoolomnibus-v81

Command to launch the Installation Manager GUI. Ensure 'installer_path' points to your Installation Manager installation directory.

```bash
installer_path/IBMIM
```

--------------------------------

### Example Output of Identifying Installation Resource

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=control-creating-restriction-filters

This is an example of the output you might see when identifying your installation custom resource.

```text
NAME           PHASE    LICENSE    STORAGECLASS   STORAGECLASSLARGEBLOCK   AGE
ibm-cp-aiops   Running  Accepted   lvms-vg1       lvms-vg1                 12d
```

--------------------------------

### Example Installation Manager Repository Output

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=repository-validating-installation-manager

This is an example of the output you might see when listing available packages from a properly configured Installation Manager repository. It includes package IDs and versions for common IBM software offerings.

```text
com.ibm.cic.agent_1.8.6001.20170428_1156
com.ibm.java.jdk.v8_8.0.5000.20170906_1259
com.ibm.websphere.BASE.v90_9.0.4.20170523_1327
com.ibm.websphere.ND.v90_9.0.4.20170523_1327
com.ibm.websphere.IHS.v90_9.0.4.20170523_1327
com.ibm.websphere.PLG.v90_9.0.4.20170523_1327
```

--------------------------------

### Example IBM Concert Operate Installation Status Output

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=administering-restarting-environment

This is an example of the output from the `kubectl describe installations` command, showing the status of various components and the overall installation phase. Note that the Zookeeper component is specific to production deployments.

```yaml
Name:         aiops-installation
Namespace:    aiops
API Version:  orchestrator.aiops.ibm.com/v1alpha1
Kind:         Installation
Spec:
...
Status:
Componentstatus:
   Aimanager:                            Ready
   Aiopsanalyticsorchestrator:           Ready
   Aiopsedge:                            Ready
   Aiopsui:                              Ready
   Asm:                                  Ready
   Baseui:                               Ready
   Cassandra:                            Ready
   cluster.aiops-orchestrator-postgres:  Ready
   cluster.opensearch:                   Ready
   Commonservice:                        Ready
   Flinkdeployment:                      Ready
   Issueresolutioncore:                  Ready
   Kafka:                                Ready
   Lifecycleservice:                     Ready
   Lifecycletrigger:                     Ready
   Rediscp:                              Ready
   Zenservice:                           Ready
   Zookeeper:                            Ready
Phase:                   Running
```

--------------------------------

### Example: Run MustGather with k3s-install Alias

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=support-running-mustgather-tool

An example of running the MustGather tool with the 'k3s-install' alias to collect data for installation issues.

```bash
./waiops-mustgather.sh -O k3s-install
```

--------------------------------

### Example: Install SCOM SQL Scripts on Solaris

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=automation-enabling-automatic-acknowledgement-events

Example commands demonstrating the installation of update_scom_unix.sql and auto_acknowledge_trigger_unix.sql scripts on a Solaris system. Replace 'root' and 'NCOMS' with your actual OMNIbus username and server name.

```bash
cat $OMNIHOME/probes/solaris2/update_scom_unix.sql | $OMNIHOME/bin/nco_sql -user root -password "" -server NCOMS
```

```bash
cat $OMNIHOME/probes/solaris2/auto_acknowledge_trigger_unix.sql | $OMNIHOME/bin/nco_sql -user root -password "" -server NCOMS
```

--------------------------------

### Automate Workspace GET Request Example

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-automate-workspaces

Example of a GET request to retrieve a specific automate workspace by its GUID.

```http
GET /api/automate_workspaces/430a66a0-b564-4341-b9b2-85d6f467f26f
```

--------------------------------

### Set up All-in-One Appliance

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=management-installing-google-compute-engine-appliance

Configure an all-in-one appliance with a local database and messaging server, then start the MIQ Server.

```bash
# appliance_console_cli --internal --dbdisk /dev/sdb --region 0 --password smartvm --message-server-config --message-keystore-password smartvm --server=start

```

--------------------------------

### GET Integration Service URL with Epoch Seconds

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=integrations-custom

Include start and end epoch seconds in the service URL for GET integrations. Example: http://exampleurl.com/v1/export?to=<end-epoch-s>&from=<start-epoch-s>.

```text
http://exampleurl.com/v1/export?to=<end-epoch-s>&from=<start-epoch-s>
```

--------------------------------

### GET Integration Service URL with Epoch Milliseconds

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=integrations-custom

Include start and end epoch milliseconds in the service URL for GET integrations. Example: http://exampleurl.com/v1/export?to=<end-epoch-ms>&from=<start-epoch-ms>.

```text
http://exampleurl.com/v1/export?to=<end-epoch-ms>&from=<start-epoch-ms>
```

--------------------------------

### GET Integration Service URL with SimpleDateFormat

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=integrations-custom

Include start and end SimpleDateFormat timestamps in the service URL for GET integrations. Example: http://exampleurl.com/v1/export?to=<end-yyyy-MM-dd'T'HH:mm:ss.SSSXXX>&from=<start-yyyy-MM-dd'T'HH:mm:ss.SSSXXX>.

```text
http://exampleurl.com/v1/export?to=<end-yyyy-MM-dd'T'HH:mm:ss.SSSXXX>&from=<start-yyyy-MM-dd'T'HH:mm:ss.SSSXXX>
```

--------------------------------

### Retrieve Infrastructure Management Region Number

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=upgrading-migrate-from-appliance-based-kubernetes-based-infrastructure-management-installation

Get the region number for your Infrastructure Management setup. This value is needed when configuring the new Kubernetes installation.

```bash
vmdb && rails r "puts MiqRegion.my_region.region"
```

--------------------------------

### Install Webtop Tools on UNIX/Linux - Step 2.3

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=apt-installing-desktop-webtop-tools

Run this command to complete the Webtop tools installation on UNIX and Linux systems.

```bash
$WEBTOP_HOME/config/cgi-bin/UnixSCOMTools.cgi
```

--------------------------------

### Install Example Zip File on Standalone Server

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=analytics-example-configurations

Copy the example .zip file to the deployment directory on a standalone IBM Cognos Analytics server using the cp command.

```bash
cp ./<example>.zip /opt/ibm/cognos/analytics/deployment/<example>.zip
```

--------------------------------

### Example VM with Custom Buttons

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-custom-actions

This example shows a GET request for a specific VM to retrieve its custom actions and custom action buttons. The response includes details about the VM and its associated custom buttons.

```bash
GET /api/vms/173?attributes=custom_actions,custom_action_buttons
```

--------------------------------

### Install Example Zip File in OpenShift

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=analytics-example-configurations

Use kubectl cp to copy the example .zip file into the deployment directory of a Cognos Analytics pod running in Red Hat OpenShift.

```bash
kubectl cp "./<example>.zip" "<pod_name>:/data/deployment/<example>.zip"
```

--------------------------------

### Starting Multiple Instances

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-instance-management

Initiate the 'start' action for multiple instances by specifying their hrefs in the 'resources' array.

```json
{
  "action" : "start",
  "resources" : [
    { "href" : "http://localhost:3000/api/instances/101" },
    { "href" : "http://localhost:3000/api/instances/102" },
    ...
  ]
}
```

--------------------------------

### Install Webtop Tools on UNIX/Linux - Step 2.1

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=apt-installing-desktop-webtop-tools

Execute this command from the $OMNIHOME/probes/arch directory to install Webtop tools on UNIX and Linux systems.

```bash
$WEBTOP_HOME/waapi/bin/runwaapi -file
```

--------------------------------

### start

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-methods-available-automation

Starts the object. See Samples/PowerOn_DHOB for examples.

```APIDOC
## start

### Description
Starts the virtual machine or template object. Refer to Samples/PowerOn_DHOB for usage examples.

### Method
POST

### Endpoint
/vm_or_template/start
```

--------------------------------

### Helm Install Command Failure Example

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=oadp-backing-up-concert-operate

This is an example of the error message encountered when the Helm install command fails due to an admission webhook denial.

```bash
Error: admission webhook "trust.hooks.securityenforcement.admission.cloud.ibm.com" denied the request:
Deny "icr.io/cpopen/cp4waiops/cp4aiops-bcdr@sha256:294a42a851a2717ebbc68528ab3c6bcb1ba48114ff058f1c1b537dc6aa167355", no matching repositories in ClusterImagePolicy and no ImagePolicies in the "velero" namespace

```

--------------------------------

### Start a VM

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=management-start-vm

Initiates the startup process for a specified virtual machine. It accepts a JSON payload with the action 'start'.

```APIDOC
## POST /api/vms/1921

### Description
Starts a virtual machine with the specified ID.

### Method
POST

### Endpoint
/api/vms/1921

### Parameters
#### Request Body
- **action** (string) - Required - The action to perform, which must be "start".

### Request Example
{
  "action": "start"
}

### Response
#### Success Response (200)
- **success** (boolean) - Indicates if the operation was successful.
- **message** (string) - A message describing the VM status.
- **task_id** (string) - The ID of the task initiated for starting the VM.
- **task_href** (string) - The URL to query the status of the initiated task.
- **href** (string) - The URL of the virtual machine.

#### Response Example
{
  "success": true,
  "message": "VM id:1921 name:'aab_demo_vm' starting",
  "task_id": "610",
  "task_href": "http://localhost:3000/api/tasks/610",
  "href": "http://localhost:3000/api/vms/1921"
}
```

--------------------------------

### Automate Workspace GET Response Example

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-automate-workspaces

Example JSON response for a GET request to an automate workspace, showing its details, input parameters, and available actions.

```json
{
  "href": "http://localhost:3000/api/automate_workspaces/430a66a0-b564-4341-b9b2-85d6f467f26f",
  "id": "2",
  "guid": "430a66a0-b564-4341-b9b2-85d6f467f26f",
  "user_id": "1",
  "tenant_id": "1",
  "input": {
    "objects": {
      "root": {
        "var1": "a",
        "var2": "b"
      }
    },
    "method_parameters": {
      "arg1": "first_argument"
    }
  },
  "actions": [
    {
      "name": "edit",
      "method": "post",
      "href": "http://localhost:3000/api/automate_workspaces/430a66a0-b564-4341-b9b2-85d6f467f26f"
    },
    {
      "name": "encrypt",
      "method": "post",
      "href": "http://localhost:3000/api/automate_workspaces/430a66a0-b564-4341-b9b2-85d6f467f26f"
    },
    {
      "name": "decrypt",
      "method": "post",
      "href": "http://localhost:3000/api/automate_workspaces/430a66a0-b564-4341-b9b2-85d6f467f26f"
    }
  ]
}
```

--------------------------------

### Start Virtual Machine

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-virtual-machine-management

Initiates the startup process for a virtual machine.

```APIDOC
## Starting a Virtual Machine

```json
{
  "action" : "start"
}
```
```

--------------------------------

### Example Response for Get Edge Types

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=apis-probable-cause-customization-api

An example JSON response for a successful GET request to the `/customisation/edge_type` API, showing the structure of the edge type list.

```json
{
"edge_type_list": [
   {
      "edge": "string",
      "label": "AGGREGATION",
      "outdegree": 0,
      "indegree": 0
   }
]
}

```

--------------------------------

### Check Installation Phase

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=offline-bastion-host

Run this command to verify that the installation's PHASE is 'Updating'. The installation typically takes 60-90 minutes to complete and the PHASE will change to 'Running' upon success.

```bash
oc get installations.orchestrator.aiops.ibm.com -n ${PROJECT_CP4AIOPS}

```

--------------------------------

### Starting a Virtual Machine in Ruby

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=management-scripting-actions-in-infrastructure-stand-alone

Use the 'start' method to initiate a Virtual Machine container. This method is part of the available management actions for Ruby scripting.

```ruby
vm.start
```

--------------------------------

### Example GET Request to Infrastructure Management API

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=overview-prerequisites

This example demonstrates how to issue a GET request to the Infrastructure Management API to retrieve a list of providers. It uses the previously obtained bearer token and hostname.

```bash
curl  -H "Authorization: Bearer ${IM_BEARER_TOKEN}" \
     -k -i -X GET -H "Accept: application/json"   \
     "https://${IM_HOSTNAME}/api/providers"
```

--------------------------------

### Example Healthy Installation Status Output

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=linux-online-installation

This is an example of the expected output when IBM Concert Operate is installed successfully. It shows the status of control plane and worker nodes, and lists all AIOps components as 'Ready'.

```text
$ aiopsctl status
o- [12 Aug 24 08:40 PDT] Getting cluster status
Control Plane Node(s):
    test-server-1.acme.com Ready
    test-server-2.acme.com Ready
    test-server-3.acme.com Ready

Worker Node(s):
    test-agent-1.acme.com Ready
    test-agent-2.acme.com Ready
    test-agent-3.acme.com Ready
    test-agent-4.acme.com Ready
    test-agent-5.acme.com Ready
    test-agent-6.acme.com Ready
    test-agent-7.acme.com Ready

o- [13 Mar 26 08:40 PDT] Checking AIOps installation status

   17 Ready Components
    cassandra
    commonservice
    aimanager
    cluster.aiops-orchestrator-postgres
    aiopsui
    zenservice
    cluster.opensearch
    aiopsedge
    baseui
    lifecycletrigger
    lifecycleservice
    rediscp
    aiopsanalyticsorchestrator
    kafka
    issueresolutioncore
    zookeeper
    asm

  AIOps installation healthy

```

--------------------------------

### Starting a Host

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-host-management

Initiate the startup process for a specific host or multiple hosts.

```APIDOC
## POST /api/hosts/:id (Start Single Host)

### Description
Starts a specific host.

### Method
POST

### Endpoint
/api/hosts/:id

### Parameters
#### Path Parameters
- **id** (string) - Required - The ID of the host to start.

#### Request Body
- **action** (string) - Required - Must be "start".

### Request Example
```json
{
  "action" : "start"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation.

#### Response Example
{
  "status": "success"
}
```

```APIDOC
## POST /api/hosts (Start Multiple Hosts)

### Description
Starts multiple hosts in a single request.

### Method
POST

### Endpoint
/api/hosts

### Parameters
None

#### Request Body
- **action** (string) - Required - Must be "start".
- **resources** (array) - Required - A list of host resources to start.
  - Each object in the array must contain:
    - **href** (string) - Required - The URL of the host resource (e.g., "http://localhost:3000/api/hosts/101").

### Request Example
```json
{
  "action" : "start",
  "resources" : [
    { "href" : "http://localhost:3000/api/hosts/101" },
    { "href" : "http://localhost:3000/api/hosts/102" },
    { "href" : "http://localhost:3000/api/hosts/103" }
  ]
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the success of the operation.

#### Response Example
{
  "status": "success"
}
```

--------------------------------

### Starting a Single Instance

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-instance-management

Send a POST request to the instance's specific endpoint with the action 'start' to initiate the instance.

```json
{
  "action" : "start"
}
```

--------------------------------

### HTTP Location Example for Offline Installation

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=runtimes-offline-content-runtime-deployment

When installation packages are accessible via HTTP, provide the URL including the server IP and the path to the package, such as `http://<server_IP>/path/to/docker.deb`.

```text
http://<server_IP>/path/to/docker.deb
```

--------------------------------

### Get Installation Name

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=integrations-pagerduty

Retrieves the name of the current installation. This is a prerequisite step before configuring PagerDuty integration.

```bash
oc get installation

```

--------------------------------

### Example Output of Not Ready Components

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=installation-gitops

This example output shows components that are currently in a 'Not Ready' state, indicating potential problems with their deployment.

```text
lifecycleservice: Not Ready
zenservice: Not Ready
```

--------------------------------

### Get the status of a stopping or starting a virtual machine

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=apis-resource-specific

Retrieves the status of a virtual machine task, such as stopping or starting.

```APIDOC
## GET /cam/api/v1/iaasresources/{CAM_RESOURCE_ID}/tasks/{CAM_IAASTASK_ID}

### Description
Gets the status of a virtual machine task that is currently stopping or starting.

### Method
GET

### Endpoint
`https://${TSA_HOSTNAME}/cam/api/v1/iaasresources/${CAM_RESOURCE_ID}/tasks/${CAM_IAASTASK_ID}`

### Query Parameters
- **tenantId** (string) - Required - The tenant ID.
- **ace_orgGuid** (string) - Required - The organization GUID.
- **cloudOE_spaceGuid** (string) - Required - The space GUID.

### Request Body
- **task_name** (string) - Required - The name of the task (e.g., "stop").

### Response
#### Success Response (200)
- **cloud_resource_id** (string) - The ID of the cloud resource.
- **task_name** (string) - The name of the task.
- **status** (string) - The status of the task (e.g., "SUCCESS").
- **created** (string) - The creation timestamp of the task.
- **updated** (string) - The last updated timestamp of the task.
- **stack_id** (string) - The ID of the stack.
- **resource_id** (string) - The ID of the resource.
- **resource_name** (string) - The name of the resource.
- **message** (string) - Any additional message related to the task.
- **id** (string) - The unique ID of the task.

### Response Example
```json
{
  "cloud_resource_id": "421ac557-7793-fdd5-7b83-c3525571abfe",
  "task_name": "stop",
  "status": "SUCCESS",
  "created": "2017-11-13T16:47:58.298Z",
  "updated": "2017-11-13T16:48:03.728Z",
  "stack_id": "7d55d130-c239-11e7-b95f-c5cc4d245984",
  "resource_id": "59ff272d4ba47e0020cb6583",
  "resource_name": "vsphere_virtual_machine.vm_1",
  "message": "",
  "id": "5a09ccbe9fe5890020316467"
}
```
```

--------------------------------

### Example Output for Operator Verification

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=installing-starter-installation

This is an example of the expected output when verifying the IBM Concert Operate operator installation.

```bash
$ oc get csv -n ${PROJECT_CP4AIOPS} | egrep "ibm-aiops-orchestrator"
ibm-aiops-orchestrator.v5.1.0         IBM Concert Operate               5.1.0   Succeeded

```

--------------------------------

### Example PostgreSQL Configuration File

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=administration-deployment-planning-guide

This is a sample PostgreSQL configuration file for a dedicated appliance. It includes comments explaining various parameters and their default values. Specific MIQ values are provided for certain settings.

```postgresql
# -----------------------------
# PostgreSQL configuration file - MIQ Dedicated Appliance Configuration
# -----------------------------
#
# This file consists of lines of the form:
#
#   name = value
#
# (The "=" is optional.)  Whitespace may be used.  Comments are introduced with
# "#" anywhere on a line.  The complete list of parameter names and allowed
# values can be found in the PostgreSQL documentation.
#
# The commented-out settings shown in this file represent the default values.
# Re-commenting a setting is NOT sufficient to revert it to the default value;
# you need to reload the server.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal.  If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, or use "pg_ctl reload".  Some
# parameters, which are marked below, require a server shutdown and restart to
# take effect.
#
# Any parameter can also be given as a command-line option to the server, e.g.,
# "postgres -c log_connections=on".  Some parameters can be changed at run time
# with the "SET" SQL command.
#
# Memory units:  kB = kilobytes        Time units:  ms  = milliseconds
#                MB = megabytes                     s   = seconds
#                GB = gigabytes                     min = minutes
#                                                   h   = hours
#                                                   d   = days


#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------

# The default values of these variables are driven from the -D command-line
# option or PGDATA environment variable, represented here as ConfigDir.

#data_directory = 'ConfigDir'       # use data in another directory
                    # (change requires restart)
#hba_file = 'ConfigDir/pg_hba.conf' # host-based authentication file
                    # (change requires restart)
#ident_file = 'ConfigDir/pg_ident.conf' # ident configuration file
                    # (change requires restart)

# If external_pid_file is not explicitly set, no extra PID file is written.
#external_pid_file = '(none)'       # write an extra PID file
                    # (change requires restart)


#------------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#------------------------------------------------------------------------------

# - Connection Settings - 

listen_addresses = '10.132.50.128'  # MIQ Value;
#listen_addresses = 'localhost'     # what IP address(es) to listen on;
                    # comma-separated list of addresses;
                    # defaults to 'localhost', '*' = all
                    # (change requires restart)
#port = 5432                # (change requires restart)
max_connections = 1600          # MIQ Value increased
#max_connections = 100          # (change requires restart) Note:  Increasing max_connections costs ~400 bytes of shared memory per connection slot, plus lock space (see max_locks_per_transaction).
#superuser_reserved_connections = 3 # (change requires restart)
#unix_socket_directory = ''     # (change requires restart)
#unix_socket_group = ''         # (change requires restart)
#unix_socket_permissions = 0777     # begin with 0 to use octal notation
                    # (change requires restart)
#bonjour = off              # advertise server via Bonjour
                    # (change requires restart)
#bonjour_name = ''          # defaults to the computer name
                    # (change requires restart)

# - Security and Authentication - 

#authentication_timeout = 1min      # 1s-600s
#ssl = off              # (change requires restart)
#ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'  # allowed SSL ciphers
                    # (change requires restart)
#ssl_renegotiation_limit = 512MB    # amount of data between renegotiations
#password_encryption = on
#db_user_namespace = off

# Kerberos and GSSAPI
#krb_server_keyfile = ''
#krb_srvname = 'postgres'       # (Kerberos only)
#krb_caseins_users = off

# - TCP Keepalives - 
# see "man 7 tcp" for details

tcp_keepalives_idle = 3         # MIQ Value;
#tcp_keepalives_idle = 0        # TCP_KEEPIDLE, in seconds;
                    # 0 selects the system default
tcp_keepalives_interval = 75        # MIQ Value;
#tcp_keepalives_interval = 0        # TCP_KEEPINTVL, in seconds;
                    # 0 selects the system default
tcp_keepalives_count = 9        # MIQ Value;
#tcp_keepalives_count = 0       # TCP_KEEPCNT;
                    # 0 selects the system default


#------------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#------------------------------------------------------------------------------

# - Memory - 


```

--------------------------------

### LIKE Operator - Start Anchor

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-advanced-filter-language-syntax

Example of the LIKE operator using '^' to anchor the pattern to the start of the string.

```filter-language
abcd LIKE '^a'
```

--------------------------------

### Rego Starts With Filter Example

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=control-creating-redaction-policies

Use this snippet to filter entities where the 'name' attribute starts with the prefix 'del'.

```rego
output := input.entity if {
    startswith(input.entity.name, "del")
}

```

--------------------------------

### Example PA Configuration File

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=probe-running-under-process-agent-control

This is an example PA configuration file demonstrating how to define processes for the ObjectServer and the probe, along with service and routing table configurations.

```ini
# List of processes
#
nco_process 'MasterObjectServer'
{
	Command '%OMNIHOME%\\bin\\nco_objserv -name NCOMS -pa NCO_PA' run as 0
	Host		= 	'host_ip'
	Managed		= 	True
	RestartMsg	= 	'${NAME} running as ${EUID} has been restored on ${HOST}'.
	AlertMsg	= 	'${NAME} running as ${EUID} has died on ${HOST}'.
	RetryCount	= 	0
	ProcessType	= 	PaPA_AWARE
}

nco_process 'WineventlogProbe'
{
	Command '[CWD=C:\\IBM\\Tivoli\\Netcool\\omnibus\\probes\\win32]
	%OMNIHOME%\\probes\\win32\\nco_p_nonnative.exe 
nco_p_wineventlog.exe' run as 0
	Host		= 	'host_ip'
	Managed		= 	True
	RestartMsg	= 	'${NAME} running as ${EUID} has been restored on ${HOST}'.
	AlertMsg	= 	'${NAME} running as ${EUID} has died on ${HOST}'.
	RetryCount	= 	0
	ProcessType	= 	PaPA_AWARE
}

# List of Services
#
nco_service 'Core'
{
	ServiceType	= 	Master
	ServiceStart	= 	Auto
	process 'MasterObjectServer' NONE
	process 'WineventlogProbe' 'MasterObjectServer'
}

# ROUTING TABLE
#
nco_routing
{
	host 'host_ip' 'NCO_PA' 'user' 'password'
}
```

--------------------------------

### Verify Tiller Installation

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=template-deploying-helm-tiller-cloud-kubernetes-service

Use kubectl to get pods in the 'kube-system' namespace that are labeled with 'app=helm' to verify if Tiller is installed.

```bash
kubectl get pods -n kube-system -l app=helm
```

--------------------------------

### Install Webtop Tools on Windows

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=apt-installing-desktop-webtop-tools

Run this command from the %OMNIHOME%\probes\win32 directory to install Webtop tools on Windows.

```bash
"%WEBTOP_HOME%\waapi\bin\runwaapi" -file WindowsSCOMTools.xml
```

--------------------------------

### Restart a Physical Server to System Setup

Source: https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=reference-physical-server-management

Restarts a specified physical server and boots into the system setup utility.

```APIDOC
## POST /api/physical_servers/action

### Description
Restarts a physical server to system setup.

### Method
POST

### Endpoint
/api/physical_servers/action

### Request Body
- **action** (string) - Required - Must be "restart_to_sys_setup"
```
Tokens:
Raw