This documentation supports an earlier version of BMC Helix IT Service Management on-premises deployment.

To view the documentation for the latest version, select 23.3.01 from the Product version picker.

Performing the postinstallation configurations

Review information in this topic to understand the configurations that a system administrator performs after the successful deployment of  BMC Helix Service Management.

Related topic

Accessing and navigating Developer Studio Open link

After you successfully perform the installation and activate the licenses, perform the following configurations to set up BMC Helix Service Management.

Important

When BMC Service Request Management is installed, the Request Entry console in Service Request Management is disabled by default. If you want to use the Request Entry console for service request management, enable the console in BMC Service Request Management.

To load foundation data

Applications use Foundation data that consists of common data elements, such as people, organization, locations, categorizations, and geography, that can be used by multiple applications in an organization to satisfy different requirements. The Foundation data can be used to drive business processes and rules. 

For steps on loading the foundation data in your system, see the topic  Setting up and modifying Foundation data by using Application Administration Console Open link  in the AR System documentation.

Back to top

To update the Survey URL in the SYS:Attachments form

  1. Open the SYS:Attachments form and search for Attachment Definition = Survey.
  2. Update the URL field in the following format:
    https://<MIDTIER_USER_INGRESS_HOST>.com/arsys/servlet/ViewFormServlet?form=SRM:Survey&view=RequesterAnswer&server=<MIDTIER_USER_INGRESS_HOST>-s

  3. If you have installed a language pack, update this URL for other language entries.

Back to top

To configure and validate the incoming and outgoing mailboxes

To configure the incoming and outgoing mailboxes

  1. Navigate to the AR System Email Mailbox Configuration form.
  2. To create an incoming mailbox, set the following parameters:
    • Mailbox Function - Incoming 
    • Polling Interval - 1
    • Email server Requires SSL - No
      Set the Email Server User and Email Server Password.
      Incoming Mailbox:


  3. On the Advanced Configuration tab, set the following values:
    •  Email Action -Parse 
    • Enable Modify Actions - Yes

  4. To create an outgoing mailbox, set the following parameters:
    • Mailbox Function - Outgoing
    • Polling Interval - 1
    • Email server Requires SSL - No
      Set the Email Server User and Email Server Password.
    Outgoing Mailbox:


  5. On the Advanced Configuration tab, set the following values:
    • Delete Outgoing Notification Messages - No
    • Enable Modify Actions - Yes
      In the Display Name and Organization, add the full name of the organization.

To validate the incoming and outgoing mailboxes

  1. Navigate to the AR System Email Messages form.
  2. Click New Request and update the following fields:
    1. Mailbox Name
    2. To
    3. Subject
    4. Body of the mail



  3. Click Send.
    You will receive an email in some time. This check validates that your outgoing mailbox is configured correctly.
  4. Reply to the email to test whether the incoming mailbox is configured correctly.
  5. After you reply to the mail, navigate to the AR System Email Messages form and select New Search > Select Message Type: Incoming > Search.
    Check if the reply mail is present.

Back to top

To validate the Configuration Manager Dashboard (CMDB Dashboard)

  1. Navigate to Applications > Atrium Core > Configuration Dashboard Manager
  2. Verify if you can see the dashboard correctly.

Back to top

To connect to Developer Studio

For Developer Studio to be able to connect with BMC Helix Innovation Suite server, you must use the External IP of the platform service.

  1. On the BMC Deployment Engine which is your Jenkins server, run the following command, and note the EXTERNAL-IP address of the platform-admin-ext service:

    kubectl get svc -n <namespace>

    If your Kubernetes or Openshift cluster is not in a cloud environment, look for the external IP address and use the value and port 46262 to connect to Developer studio. Example output of the command is as follows:

    NAME			TYPE 	CLUSTER-IP EXTERNAL-IP PORT(S)platform-admin-ext   ClusterIP   10.43.27.39     172.19.xxx.xx      46262/TCP,8008/TCP,20000/TCP,61617/TCP,7319/TCP,40001/TCP,9999/TCP,9556/TCP 16d

    If your Kubernetes or Openshift cluster is in a cloud environment, look for the load balancer hostname and use the value and port 46262 to connect to Developer studio. Example output of the command is as follows:

    NAME				TYPE 		CLUSTER-IP 		EXTERNAL-IP 										PORT(S)
    platform-admin-ext  LoadBalancer 10.100.233.202 xxxxxxxxx.us-east-2.elb.amazonaws.com,xx.xx.xxx.xxx 46262:31301/TCP,8008:31827/TCP,20000:30189/TCP,61617:30579/TCP,7319:30370/TCP,40001:31482/TCP,9999:31476/TCP,9556:30511/TCP   8d
  2. (Optional) Confirm that the platform-admin-ext service has the EXTERNAL-IP value configured by using the following command:

    kubectl get svc -n <BMC Helix Innovation Suite namespace>

    If the command output does not display any IP address for the platform-admin-ext service, the EXTERNAL-IP is not configured. Configure the EXTERNAL-IP by running the following command:

    kubectl patch service platform-admin-ext -n <namespace> -p '{"spec":{"externalIPs":["'<IP address of your Kubernetes cluster worker node>'"]}}'

    For example:

    kubectl patch service platform-admin-ext -n <namespace> -p '{"spec":{"externalIPs":["'172.10.101.123'"]}}'

Back to top

Where to go from here

Next task

To perform basic configurations such as configure set up users, and provide user permissions proceed with Onboarding and implementing Open link in AR System documentation.

Back to process

Return to Installing.



Was this page helpful? Yes No Submitting... Thank you

Comments