Service Modeling Toolkit version 2.0 XLSX to CMDB using Atrium … · 2020-06-05 · SERVICE...

FIELD DEVELOPED SOLUTION

Author: Karlis Peterson, Software Consultant, BMC Software

Version: 2.0 Date: June 10, 2013

DISCLAIMER NOTICE

The free integration provided may be freely distributed, provided that no charge above the cost of distribution is levied, and that the disclaimer below is always attached to it.

The integration is provided as is without any guarantees or warranty.

Although the author has attempted to find and correct any bugs in the integration, the author nor BMC Software is not responsible for any damage or losses of any kind caused by the use or misuse

of the integration contents.

Service Modeling Toolkit version 2.0 – XLSX to CMDB using Atrium Integrator

SERVICE MODELING TOOLKIT V2.0 – AI INTEGRATION

2 SERVICE MODELING TOOLKIT

CONTENTS

Overview ........................................................................................................................................................................ 4

What’s New in Service Modeling Toolkit Version 2.0 .................................................................................................... 5

Service Modeling Toolkit Requirements ........................................................................................................................ 8

ITSM Configurations ...................................................................................................................................................... 8

Setting Up ServiceModel.AI Import dataset ......................................................................................................... 8

Import Service Modeling Toolkit XML Files........................................................................................................... 9

Creating the Atrium Integrator 8.x User ............................................................................................................. 13

Mapping Jobs and Transforms ............................................................................................................................ 15

Testing Service Modeling Toolkit ................................................................................................................................. 18

Run the Job ......................................................................................................................................................... 18

XLS – Meta Data........................................................................................................................................................... 26

Step1_BMC_ComputerSystem............................................................................................................................ 26

Step1a_BMC_Cluster .......................................................................................................................................... 27

Step2_BMC_VirtualSystemEnabler ..................................................................................................................... 29

Step3_BMC_SoftwareServer............................................................................................................................... 30

Step4_BMC_Application ..................................................................................................................................... 32

Step5_EdgeSwitch............................................................................................................................................... 34

Step7_SAN .......................................................................................................................................................... 35

Step8_BMC_Organization – No current Transforms ........................................................................................... 35

Appendix A - Troubleshooting ..................................................................................................................................... 37

Remedy Application Service (User) ..................................................................................................................... 37

XLS Column Names ............................................................................................................................................. 37

Errors when running Job ..................................................................................................................................... 37

Importing the Integration in ITSM 7.6.04 (AI 7.6.04) .......................................................................................... 41

Deleting the records in ServiceModel.AI Dataset ............................................................................................... 41

Feedback and Enhancements ...................................................................................................................................... 43

CI Alias ................................................................................................................................................................. 43



OVERVIEW

The purpose of this Field Developed Integration is to automatically create CIs/CI Attributes and Dependencies that

make up a Business Service Model. This toolkit can be used quickly “bulk” load/build large number of Service

Models in Day 1 Operations. The toolkit can be used as a way to validate the functional components of a Service

Model without needing to reconcile to BMC.ASSET. The source of the data is a multi-tabbed XLS spreadsheet.

The concept is to sit down with a customer or SME and fill in the “meta data” of the Service Model. The Service

Modeling Toolkit is intended to accelerate the process for building Service Models.

The following diagram shows the data flow from XLS to an Import data set within the CMDB:

The Service Modeling Toolkit includes the following CIs and dependencies:

Logical CIs such as Transaction and Business Service

Virtual Server

Server Clusters

Load Balancer Resource Pools (e.g. Web Pool)

SAN – Importing Disk Arrays and LUN Mappings (CI Relationships) to physical servers

Edge Switch – Network Relationships

And others ..



WHAT’S NEW IN SERVICE MODELING TOOLKIT VERSION 2.0

In this Release (version 2.0), Simple and Advanced Service Models are supported. Simple Service Models typically

include the following CI classes: BMC_ComputerSystem, BMC_Application, BMC_Transaction (optional) and

BMC_BusinessService CIs. The benefit is to quickly build out more Business Services (Day 1) which can be

consumed by BPPM (for PCA/correlation) and ITSM Applications such as Change Management.

The following Table is a summary of the XLS tabs that are required (or optional) for Simple and Advanced Service

Models:

XLS Tabs Simple Service Models Full Service Models

Step1_BMC_ComputerSystem Required Required

Step1a_BMC_Cluster N/A Optional

Step2_BMC_VirtualSystemEnabler Optional Optional

Step3_BMC_SoftwareServer N/A Required

Step4_BMC_Application Required Required

Step5_EdgeSwitch Optional Optional

Step6_LoadBalancerPools N/A Optional

Step7_SAN Optional Optional

Step8_BMC_Organization *Next Release *Next Release

Below is a screenshot of a Simple Service Model (in Atrium Explorer):

Note: Simple Models do supporting including SAN, Clusters and EdgeSwitch connections.



Below is a screenshot of an Advanced Service Model (in Atrium Explorer):

Other new features for Service Modeling Toolkit:

CI Alias support for all CIs in a Service Model. This is primarily for event mapping from BPPM. For

BMC_ComputerSystem CIs, an Alias is automatically created based on the following format:

o BMC_ComputerSystem:<hostname>:<domain_name>

o The CI Alias (BMC_ComputerSystem) can be over-ridden by typing in a value or CI_Alias column

in the XLS worksheet.

XLSX format – moved the spreadsheet from XLS to XLSX format. Spreadsheet now supports drop down

menus and pivot tables which allows for easier entry. An example is seen below:



Color coding of columns for easier entry. Red columns are required. Yellow columns are optional.

Marked As Deleted – you can now update the MarkedAsDeleted attribute for soft deleting the CI in the

CMDB.

Reconciliation ID – if you want to force “matching” CIs without using Reconciliation Rules, you can now

use a tool that is shipped with the integration to pull out CIs from BMC.ASSET to an Excel Spreadsheet.

You can then manually copy the ReconciliationID to force the matching. This could be beneficial to clean

up existing CIs in the CMDB that, for example, are not in FQDN format.

Transaction CI – the Transaction CI is not required to be part of the Service Model. Logic has been added

to IGNORE transaction CI as seen below:

Name Attribute for BMC_ComputerSystem and BMC_Cluster using FQDN

SoftwareServerType Attribute – added to the BMC_SoftwareServer transform as seen below:

Other CI Attributes have been added to various transforms …



SERVICE MODELING TOOLKIT REQUIREMENTS

The following are required:

Atrium Integrator 7.6.04 or Atrium Integrator 8.0

BPPM Extensions installed (requirement even if BPPM is not deployed)

Service_Model_Toolkit.zip

Pentaho Data Integration Steps (Use this as a Reference for steps in a Kettle Transform)

http://wiki.pentaho.com/display/EAI/Pentaho+Data+Integration+Steps

ITSM CONFIGURATIONS

This section describes the steps for configurations required on ITSM.

SETTING UP SERVICEMO DEL.AI IMPORT DATASET

1. Login to ITSM Mid-Tier with an Administrator role

2. Atrium Core Atrium Core Console Reconciliation

3. Select the icon below to add a dataset:

4. Create a dataset named “ServiceModel.AI” (make sure to use the name ServiceModel.AI since the

transforms use this dataset name. If you use another name then each transform will need to be updated)

http://wiki.pentaho.com/display/EAI/Pentaho+Data+Integration+Steps



IMPORT SERVICE MODELING TOOLKIT XML FILES

The following steps are configured for ITSM 8.0, but applicable for ITSM 7.6.04. Later when configuring Transforms and Jobs, the steps will be slightly different. These steps will be documented in later steps.

1. Create a directory c:\Data\ServiceModel_AI *Note – make sure there are Read/Write rights on the primary C partition. If not, then select another drive such as D:\ Data\ServiceModel_AI

2. Extract the XML and XLS files from Service_Model_v3a.zip to c:\ Data\ServiceModel_AI



3. Login to Atrium Integrator (Spoon) client:

4. File Import from an XML file

5. Select the directory that was created in Step #1. Select the file “ServiceModel_to_CMDB_AI.kjb”



6. Select Open 7. Once the transform is imported, select File Save As:

8. Select the folder icon to browse within the Repository:



9. From the root (/), right click and add sub-directory and name the directory “ServiceModel_AI”

And select OK.

10. Review and select OK to save to Repository:



11. Repeat Steps #4 – 10 (skipping step #9) for the remainder XML files:

Sub_ServiceModel_to_CMDB_AI.kjb Sub2_ServiceModel_to_CMDB_AI.kjb BMC_Application_Relationship_ServiceModel.ktr BMC_Application_ServiceModel.ktr BMC_Cluster_ServiceModel.ktr BMC_ClusterRelationships_ServiceModel.ktr BMC_ComputerSystem_ServiceModel.ktr BMC_Simple_Application_ServiceModel.ktr (NEW) BMC_Simple_Application_Relationship_ServiceModel.ktr (NEW) BMC_ComputerSystem_VirtualRelationships_ServiceModel.ktr BMC_EdgeSwitch_Relationship_ServiceModel.ktr BMC_LoadBalancerPool_Relationship_ServiceModel.ktr BMC_SAN_Relationship_ServiceModel.ktr BMC_SoftwareServer_ServiceModel.ktr BMC_TraverseRelationship_ServiceModel.ktr BMC_VirtualSystemEnabler_ServiceModel.ktr

CREATING THE ATRIUM INTEGRATOR 8.X USER

This section is for setting up the Remedy Application User for Atrium Integrator 8.0. If you are running Atrium Integrator 7.6.04, then skip to the Appendix for steps on configuring ITSM 7.6.04.

1. Login to Mid-Tier 2. Atrium Integrator Atrium Integrator Console 3. Select icon to Manage Data Stores



4. Click New Data Store icon

5. Fill out the details for the connection: Data Store Type: ARSYSTEM Data Store Name: CMDB AR Server Name: <type in the hostname of the AR server where AI is installed> Port: <type in specific TCP port or 0 for port mapper is enabled> Remedy App Service Password: <type in password>

6. Click the “Test Connection” button to validate configurations:

Note: if the TEST connection fails, then check the Appendix for resetting the Remedy Application User password.

7. Click OK. You should see the following Data Store named “CMDB”:



MAPPING JOBS AND TRANSFORMS

This section requires you to validate the references to other Kettle Jobs and Transforms. 1. Log back into Atrium Integrator or Spoon console. 2. File Open ServiceModel_AI ServiceModel_to_CMDB_AI (job)

3. Right-click on the referenced Job (step) as seen below:



4. You may see the following error, but ignore the message and select OK:

5. Select Repository: specify by name and browse to the referenced Job – the name should be the name of

the step.

Browse to the ServiceModel_AI directory and select the name (name of the step):



6. Click OK

7. Save the transform

8. Now “test” the referenced step by right-clicking the step and selecting Open Job (or Transform) as seen

below:



9. This should now open the referenced Job or Transform.

10. Continue with the following 2 Kettle Jobs and complete the same steps for each referenced Transform or Job (repeat steps #3-9) for:

Sub_ServiceModel_to_CMDB_AI.kjb Sub2_ServiceModel_to_CMDB_AI.kjb

TESTING SERVICE MODELING TOOLKIT

This section provides steps for testing the Service Modeling Toolkit with the sample data provided. Once the data is validated then use CMDBDiag.exe to delete all CIs in the Import dataset and replace XLS tabs with customer related meta data.

RUN THE JOB

1. Open the Job named “ServiceModel_to_CMDB_AI”:



2. Execute the Job:

3. Watch logging (you may want to consider lowering the level of logging). If errors are reported, please

refer to the Appendix for Troubleshooting steps.

4. Login to Mid-Tier

5. Go to Atrium Core Atrium Core Applications Explorer:



6. Select the green button top and choose ServiceModel.AI dataset:

7. On left pane, go to Find and select the ServiceModel.AI dataset:



8. Now select Query Services Business Services and type in % for Name:

9. From the results found in ServiceModel.AI, drag and drop to the right pane:



10. Select pull down from the CI and select Expand Parents:

11. Choose from top right menu Hierarchic and Bottom to Top:



12. Select show all items from consolidated folder:



13. Validate model:



Once validated, if problems then revisit the meta data in the XLS. If the model looks as designed, then create a

Standard Merge Job for the ServiceModel.AI dataset. Please refer to the Remedy documentation



XLS – META DATA

This section provides some information on the XLS tabs.

STEP1_BMC_COMPUTERSY STEM

All fields do not need to be filled. The mapping is based on the default mappings from ADDM to Common Data Model (CMDB). The following is a description of the columns within the sheet of the XLS:

Step1_BMC_ComputerSystem

Column Required Comment

Hostname Y Physical or virtual server, network device, disk array, load balancer …

Domain Y

This is critical to prevent duplicates from being created in BPPM. There may be existing devices in BPPM created from BPPM adapters such as Patrol.

Device_Type Y

This will map to the Primary Capability attribute. The following values are provided in a drop down menu:

Server HyperVisor Switch Router Firewall LoadBalancer Storage SANSwitch

CI_Alias N

This will over-ride the auto generated ALIAS. The transform will auto generate the following format for ALL BMC_ComputerSystem CIs: BMC_ComputerSystem:<hostname>:<domain>

Impact_Status_Model N

Select from the drop-down for: DIRECT

INCREASING

DECREASING

JUST_WARNING

JUST_INFO (**see BMC ProactiveNet Service Modeling and Publishing Guide for details)

Simple_Only_BAI Y

This is required for Simple Models only. Type in the Application CI (equal to BAI) name in the column. This MUST match the Simple_Only_BAI column in Step4_BMC_Application tab.

MarkedAsDeleted N

This will perform a soft delete for the specific CI in BMC.ASSET. For permanent deletion, create a Purge Job in Reconciliation (Atrium Core Applications).

Company Y Replace “Calbro Services” with customer Company Name.

HomeCell Y Type in the BPPM cell name.



HomeCellAlias Y Type in the BPPM cell name.

Server_Cluster N If host is a part of a cluster (MSCS, VCS, ..) then type “yes”

Server_Cluster_Name N This is the virtual hostname for a server cluster.

Server_Cluster_ImpactWeight N Impact Weight for servers in cluster.

Virtual_Server N If host is a Virtual Guest (VMWare, HyperV, Citrix Xen, ..) then type “yes”.

VM_Hosted_on N Type the Hypervisor (e.g. ESXi) server hostname.

LoadBalanced N If the host is part of a Load Balancer resource pool, then type “yes”.

LoadBalancer_Hostname N The Load Balancer or virtual Load Balancer hostname that host participates in a resource pool.

Managed_IP_Address N This is the Primary Managed IP Address of device. This is not used in the current toolkit, but could easily be extended to BMC_IPEndPoint class.

SerialNumber N Serial number of physical device.

Category N Category – used same as ADDM mapping.

Item N Item – used same as ADDM mapping.

Model N Device model.

ManufacturerName N Device manufacturer name

Room N Optional to type in rack/elevation and datacenter room location. This information could be used in Dynamic CI Enrichment.

Priority N This will set the priority for the CI.

ImpactPropagationModel N This sets the relationship – use either DIRECT, INCREASING, DECREASING, JUST_WARNING, and JUST_INFO

ReconciliationID N

Force matching of CIs. Check the Integration link on Communities for a tool to extract CIs/Attributes from BMC.ASSET. You can then use the Reconciliation Identity (ID) to force matching CIs that are already in the CMDB. The AI integration will update attributes – therefore you may want to REVIEW the attributes in the CMDB Output step for the associated transform.

STEP1A_BMC_CLUSTER

All fields do not need to be filled. If there are no Clusters, then delete all rows, EXCEPT the column headers. The mapping is based on the default mappings from ADDM to Common Data Model (CMDB). The following is a description of the columns within the sheet of the XLS:



Step1a_BMC_Cluster


Cluster_Hostname Y Virtual cluster name.

Domain Y


Cluster_Type

Cluster_Type Y

The default value is Software Cluster, but you can select from the following values:

Software Cluster Hardware Cluster SoftwareServerCluster ApplicationInstanceCluster J2EE Cluster


Impact Propagation model is calculated from the following values provided in the drop down menu:

Standard Standard Unknown Cluster Weighted Cluster Self-Preferred

CI_Alias N

Type in an ALIAS value which then can be matched to an incoming event from BPPM. See the Appendix for Alias format and use ALIAS formulas in BPPM.

MarkedAsDeleted N





Cluster_IP_Address N This is the IP Address of the virtual cluster or VIP.

Category N Category – no sample data provided.

Type N Type – no sample data provided.

Item N Item – no sample data provided.

Model N Device model.

ManufacturerName N Device manufacturer name





ReconciliationID N


STEP2_BMC_VIRTUALSYSTEMENABLER

All fields do not need to be filled. If there are no virtual servers, then delete all rows, EXCEPT the column headers. The mapping is based on the default mappings from ADDM to Common Data Model (CMDB). The following is a description of the columns within the sheet of the XLS:

Step2_BMC_VirtualSystemEnabler


Hostname Y Virtual host or hypervisor.

Domain Y





CI_Alias N


MarkedAsDeleted N





OS_Model N Model information. For example, VMWare ESXi.

OS_Manaufacturer N Manufacturer information. For example, VMWare.

OS_Version N Version information. For example, VSphere 5.1.







ReconciliationID N


STEP3_BMC_SOFTWARESERVER

All fields do not need to be filled. For applications, Software Server tab becomes a critical component for creating CIs and dependencies. The mapping is based on the default mappings from ADDM to Common Data Model (CMDB). The following is a description of the columns within the sheet of the XLS:

Step3_BMC_SoftwareServer


Hostname Y Physical or virtual server that software server is running on. If Cluster then LEAVE BLANK.

Domain Y


Server_Cluster_Name N If the Hostname is BLANK then this becomes a required field. This would be the cluster name.

LoadBalanced N Type in “yes” if the server is part of a load balancer resource pool.

LoadBalancer_Hostname N

If LoadBalanced column is set to “yes”, then you will need to type in the hostname of the Load Balancer. This version does not support a clustered LB. If you have a clustered LB, then use the Load Balanced Hostname or VIP for both BMC_ComputerSystem and other transforms that reference LB.

Software_Server Y

This is equivalent to the SI that ADDM discovers. You may want to review what ADDM discovers and use that SI name. In the example, a JVM named “Oracle WebLogic Application Server 11gR1 identified as prodServer2, domain: prod_domain”



Software_Server_Type N

Select the Software Server type from the Drop down list:

DatabaseServer CommunicationServer MessageServer SecurityServer TransactionServer ResourceServer FTPServer MailServer DNSServer UDDIServer LDAPServer WEBServer ConfigurationMngAgent WebServicesServer BusinessProcessServer J2EEServer SAPMessageServer SAPEnqueueServer SAPDispatchServer SAPGatewayServer SAPCMServer SAPJ2EEDispatcher SAPSDMServer SAPXIIntegrationEngine SAPXIAdapterEngine OracleTNSListener




CI_Alias N


MarkedAsDeleted N







Category N Category – used same as ADDM mapping.

Type N Type – used same as ADDM mapping.

Item N Item – used same as ADDM mapping. In the example, Application Server Software Platforms.

Model N Device model. In the example, Oracle WebLogic Application Server.

ManufacturerName N Device manaufacturer name. In the example, Oracle.

Software_Server_MarketVersion N Software Server version.

BAI Y

This in the logical name of the Application CI or in ADDM the Business Application Instance. This MUST match the Application or BAI column name in the Step4_BMC_Application tab.

Software_Server_Traverse_To Y

For BAI, there are relationships between Software Instances (SIs). For example, Middlware communicates with a backend database instance. Type in the Name of the SI. In the example, the SI named “Oracle WebLogic Application Server 11gR1 identified as prodServer2, domain: prod_domain” communicates to a MS SQL DB instance “Microsoft SQL Server 2008 R2 identified as SQLServer”.

Software_Server_Traverse_Hostname Y Type in the name of the hostname to SI that previous column is communicating to.



ImpactWeight N

Set the numeric value which represents a percentage. For example, a Clustered JVM would be 50% for each participating JVM in cluster.

MarkedAsDeleted N


STEP4_BMC_APPLICATIO N

All fields do not need to be filled. These are the logical CIs and Relationships that are created as “children” to the Application or BAI CI. The following is a description of the columns within the sheet of the XLS:

Step4_BMC_Application




BAI Y BAI or Application name. This is ONLY used for Advanced Service Models.

Simple_Only_BAI Y BAI or Application name. This is ONLY used for Simple Service Models.

BAI_Impact_Status_Model N



BAI_Alias N


BAI_ReconciliationID N


BAI_MarkedAsDeleted N


Transaction_Monitoring Y

If yes is selected, then a Transaction CI will be included in the Service Model. Otherwise, BMC_Application CI will be mapped to BMC_BusinessService CI.

End_UserTransaction Y

This is a Transaction CI that would be mapped to events from solutions like EUEM or TMaRT. ** If Transaction_Monitoring is set to <null> (no) – then nothing needs to be in this field (leave blank).

Transaction_Alias N


Transaction_ReconciliationID N


Transaction_MarkedAsDeleted N This will perform a soft delete for the specific CI in BMC.ASSET. For permanent deletion, create a



Purge Job in Reconciliation (Atrium Core Applications).

Business_Service Y This is the Business Service (or Technical Service) CI. This could be an existing CI in the Service Catalog.

Business_Service _Alias N


Business_Service _ReconciliationID N


Business_Service_Type Y Select from drop down:

Business Technical

Business_Service _MarkedAsDeleted N






STEP5_EDGESWITCH

All fields do not need to be filled. This tab will build relationships from the Edge Switches to physical servers. The following is a description of the columns within the sheet of the XLS:

Step5_EdgeSwitch


Source_Switch Y This is the Edge Switch name that should be listed in Step1_BMC_ComputerSystem.

Domain Y


Destination_PhysicalHost Y This is the physical server or hypervisor name that should be listed in Step1_BMC_ComputerSystem.

MarkedAsDeleted N This will perform a soft delete for the specific CI in BMC.ASSET. For permanent deletion, create a Purge Job in Reconciliation (Atrium Core



Applications).

ImpactPropagationModel N

This sets the relationship – use either DIRECT, INCREASING, DECREASING, JUST_WARNING, and JUST_INFO. In the server or hypervisor has multiple or redundant connections, then you may want to consider using JUST_INFO.

ImpactWeight N Set the numeric value which represents a percentage.

STEP7_SAN

All fields do not need to be filled. This tab will build relationships from the Disk Arrays or Filers to SAN switch then to physical servers. The following is a description of the columns within the sheet of the XLS:

Step7_SAN


Source_SAN Y This is the Disk Array or Filer name that should be listed in Step1_BMC_ComputerSystem.

Domain Y


WWN N Type in the WWN.

LUN N Type in LUN name.

Destination_SANSwitch Y This is the SAN switch name that should be listed in Step1_BMC_ComputerSystem.

Desitnation_Server Y This is the physical server name that is connected to the SAN switch and should be listed in Step1_BMC_ComputerSystem.

MarkedAsDeleted N


ImpactPropagationModel N

This sets the relationship – use either DIRECT, INCREASING, DECREASING, JUST_WARNING, and JUST_INFO. In the server or hypervisor has multiple or redundant connections, then you may want to consider using JUST_INFO.

ImpactWeight N Set the numeric value which represents a percentage.

STEP8_BMC_ORGANIZATION – NO CURRENT TRANSFORMS

If you would like to add impacted Organizations to Service Model, then an additional Transform would be required to be created. The following is a description of the columns within the sheet of the XLS:

Step8_BMC_Organization




Organization Y This is name of Organizations (within ITSM) that would be impacted by Business Service availability.

Business_Service Y Type in the name of the Business Service.

MarkedAsDeleted N





MarkedAsDeleted N




APPENDIX A - TROUBLESHOOTING

This section provides some troubleshooting steps.

REMEDY APPLICATION SERVICE (USER)

This section is intended for re-setting the UDM:RAppPassword. This does not need to be accomplished, unless you used the Suite Stack Installer.

1. In the current browser session, navigate to the form: http://hostname:8080/arsys/forms/hostname/UDM:RAppPassword

2. For the Server Name, enter % (percent sign). 3. Click Search.

Note that a single entry for localhost is present. The password for this entry was set to password during installation.

4. Click New Request. 5. Set Server Name to ten. 6. Set RApp Password to password. 7. Click Save. 8. Click New Search. 9. For the Server Name, enter % (percent sign). 10. Click Search.

Note that the new entry for the server ten is now listed. 6. Click Home. 7. This will open a new browser tab.

You may close the other browser tabs.

XLS COLUMN NAMES

If you change the names of the Column headings, then you will need to modify the transforms where the original names were referenced. Typically this will be in the first Transform Step (XLS input) and CMDB Output step.

ERRORS WHEN RUNNING JOB

If you run the Job for the first time and see errors, then follow the error to the first transform and then try to execute transform separately. As seen below, the Job reports an error with the transform named “BMC_ComputerSystem_ServiceModel”.

http://hostname:8080/arsys/forms/hostname/UDM:RAppPassword



Open the transform and try to execute the transform individually:



Then check the logs. In this case the problem is the connection to AR.



Edit the step and configure the Connection using Remedy Application Server user:

Once Test connection is successful, select OK and re-run the transform.



IMPORTING THE INTEGRATION IN ITSM 7.6.04 (AI 7.6.04)

You may need to validate each of the following steps in every imported Transform: XLS input CMDB Lookup CMDB Output

Step to success – run each transformation separately and use logging to troubleshoot. Logs are your friend!

DELETING THE RECORDS IN SERVICEMODEL.AI DATASET

After you run

For example: E:\Program Files\BMC Software\BMCServiceLevelManagement\rik\cmdbdriver

Create a short-cut to the desktop

Run cmdbdiag

Authentication string: <hit return>

User (Demo): <admin user>

Password: <admin user password>

Server (localhost): <hit return>

Select 2

Select 2



All datasets [y, n] (n): <hit enter – defaults to no>

Dataset id: ServiceModel.AI

So you want to continue? [y, n] (n): y

Once you see below, the deletion is complete:



FEEDBACK AND ENHANCEMENTS

Please provide feedback or enhancements to [email protected]

CI ALIAS

Special thanks in advance to Marc Stephens, Tim Bocardo and and George Klarmann for pushing innovative ideas! Based on their development, you can follow manually entering the CI_Alias Column in the XLS to match the following guidelines. Attached to the integration is a SAMPLE Alias formula that can be imported into BPPM using MPOSTER.

Attached Alias formula that matched format below: HIG ALIAS FORMULAS.txt

Object Description

CI Class and Type Alias format Example

VERITAS

Cluster

BMC_Cluster,

ClusterType=Software

ServerCluster

<ClusterVirtualName>

ISDORAPRD1

VCenter

Cluster

BMC_Cluster,

ClusterType=SoftwareServerCluster

<ClusterVirtualName> atospvhe01

Microsoft

Cluster BMC_Cluster <ClusterVirtualName> atospvhe01

Sun Cluster BMC_Cluster,

ClusterType=SoftwareServerCluster


Red Hat

Cluster

BMC_Cluster,

ClusterType=Software

ServerCluster


Sybase DB

Cluster BMC_Cluster <ClusterVirtualName> sybdb01

IBM HACMP

Cluster BMC_Cluster <ClusterVirtualName> atospvhe01

HP ServiceGuar

d Cluster

BMC_Cluster <ClusterVirtualName> atospvhe01

Citrix Server

Farm BMC_Cluster <ClusterVirtualName> atospvhe01

Load

Balancer

VIP

BMC_SystemResourc

e,

Primary Capacity = LoadBalancerVIP

<VIP> webserver.bmc.com

127.257.45.127

Load

Balancer

URL

BMC_SoftwareServer

SoftwareServerType=ResourceServer

LB::URL::<url> LB::URL::claimbpm.bmc.com

mailto:[email protected]



Oracle App

Server

BMC_SoftwareServer,

SoftwareServerType=AppServer

<host>::<service_short_type>::<instance> Gbdorhp001::

ORA_APP_SVR::Prod_edm_claim_bpmui_04

Oracle

Database

In a VERITAS Cluster:

BMC_ApplicationServi

ce

Else BMC_Database

<host>::<service_short_type:<DB instance> Dctmbph001::

ORA_DB::dbdctmp2

Oracle TNS

Listener

In a VERITAS Cluster:

BMC_ApplicationService

Else

BMC_SoftwareServer

<host>::<service_short_type>::<DB instance> dctmbph002::ORA_LSTR::dbdc

tmp2

Oracle RAC

DB BMC_Database <virtualNode>::<service_short_type:<DB

instance>

dctmbph002::ORA_RAC::dbdct

mp2

Microsoft SQL Server

DB

BMC_Database <host>::<service_short_type:<DB instance> dctmbph002::MSSQL_DB::dbdctmp2

IBM DB2 BMC_Database <host>::<service_short_type:<DB instance> dctmbph002::DB2_DB::dbdctm

p2

Sybase ASE

DB BMC_Database <host>::<service_short_type:<DB instance> dctmbph002::SYB_DB::dbdctm

p2

Sun One

HTTP Server BMC_SoftwareServer <host>::<service_short_type>::<instance> hfwhp01::SUN1_HTTP:: https-

edm

IBM

Websphere App Server

BMC_SoftwareServer,

SoftwareServicerType=AppServer

<host>::<service_short_type>::<instance> hfwhp01:: IBM_WAS:: https-

edm

Microsoft IIS

Service BMC_SoftwareServer <Virtual Instance Name>

Microsoft IIS

Server BMC_SoftwareServer <host>::<service_short_type>::<blank>

Apache

HTTP Server BMC_SoftwareServer <Virtual Instance Name>

IBM HTTP

Server BMC_SoftwareServer <Virtual Instance Name>

JBoss Server BMC_SoftwareServer <host>::<service_short_type>::<instance>

Tomcat

Server BMC_SoftwareServer <host>::<service_short_type>::<instance>

Weblogic

App Server

BMC_SoftwareServer,

SoftwareServerType=AppServer

<host>::<service_short_type>::<instance> Ibsrdy01::WebLogic_AS::Prod_

edm_claim_bpmui_04

WebMethod

s Broker

Server

BMC_SoftwareServer <host>::<service_short_type>::

WebMethod

s Broker Monitor

BMC_SoftwareServer <host>::<service_short_type>::



IBM

WebSphere MQ Queue

Manager

BMC_SoftwareServer,

SoftwareServerType=TransactionServer

<host>::<service_short_type>::<QueueManag

er>

Qymmthn32::IBM_QMGR::HIG

CNP2

IBM

WebSphere MQ Queue

Manager (in a VERITAS

Cluster)

BMC_ApplicationServi

ce

<service_short_type>::<QueueManager> IBM_QMGR::HIGCNP2

WebSphere

MQ Queue

BMC_SystemResourc

e <service_short_type>::<instance name> IBM_Q::HIG.PC.CL00.EDM.BU

NDLER.REQ

Microsoft

Exchange Server

BMC_SoftwareServer <host>::<service_short_type>:: mailsrv1:: MSEXCHANGE::

RIM

BlackBerry

Enterprise Server

BMC_SoftwareServer <host>::<service_short_type>:: bessrv1::RIM_SVR::

RIM

BlackBerry

Enterprise Router

BMC_SoftwareServer <host>::<service_short_type>:: bessrv1::RIM_RTR::

RIM

BlackBerry

Enterprise Dispatcher

BMC_SoftwareServer <host>::<service_short_type>:: bessrv1::RIM_DSP::

Microsoft

SQL Server

Analysis Services

BMC_SoftwareServer <host>::<service_short_type>:: bessrv1::MSSQL_SAS::

Microsoft

SQL Server

Reporting Services

BMC_SoftwareServer <host>::<service_short_type>:: bessrv1::MSSQL_SRS::

Documentum

Content

Server

BMC_SoftwareServer,

SoftwareServerType=

Documentum Content Server

<host>::<service_short_type>:: dctmcsph002::

EMC_DOC_SVR::

Documentum

DTS

BMC_SoftwareServer,

SoftwareServerType=

Documentum DTS Server

<host>::<service_short_type>:: ad1hfdcts003:EMC_DOC_DTS

Documentum

Docbase

BMC_SoftwareServer,

SoftwareServerType=

Documentum Docbase

<host>:: <service_short_type>::<instance> dctmcsph001::DOCUMENTUM

::claimsp

Batch Job BMC_ApplicationServi

ce

<service_short_type>::BusinessService

Name> BS::Claim_Auto



URL BMC_ApplicationServi

ce <url> www.myapp.com/index.jsp

TM ART Transactions

BMC_Transaction tran::<project>::<location>::<monitor>

tran::<project>::<location>

tran::<project>::<monitor>

tran::Claim_Handling::Dallas::View Claim

tran::Claim_Handling::Dallas

tran::Claim_Handling::View

Claim

Service Modeling Toolkit version 2.0 XLSX to CMDB using Atrium … · 2020-06-05 · SERVICE...

Documents

Transcript of Service Modeling Toolkit version 2.0 XLSX to CMDB using Atrium … · 2020-06-05 · SERVICE...