This documentation supports the 1.5 version of Remedy with Smart IT.

To view the latest version, select the version from the Product version menu.

Integrating BMC Remedy ITSM with the Social Server for Smart IT

The information shown on timelines and feeds is uploaded from BMC Remedy IT Service Management (BMC Remedy ITSM) and processed by the Social Server. To import the existing BMC Remedy ITSM data into the Social Server, use the BMC Remedy with Smart IT onboarding utility.

Before you begin

Ensure that MongoDB is installed.

Click the following link to view a quick video about importing Smart IT social data to the BMC Remedy ITSM database.

To run the onboarding utility

  1. Extract the onboarding.zip file from the /SmartIT/SmartITOnboardingTool folder to a local folder on the SmartIT server (for example, c:\utility\).

  2.  Using the parameters listed in the following table, run the onboarding.bat Windows command or onboarding.sh Linux command as shown in this example:

     c:\utility\onboarding.bat -x itsmServer.calbro.com -u Demo -p "Apassword" -t 0 -T 000000000000001 -ssn localhost -ssp 27017 -ssd social -ssdu DBAdmin -ssdp DBPassword -o all


    Parameters for running the onboarding utility

    ParameterDescriptionExample value
    xBMC Remedy ITSM server host name
    itsmServer.calbro.com
    uBMC Remedy ITSM server admin user
    Demo
    pBMC Remedy ITSM server admin user password
    password
    tBMC Remedy ITSM server TCP port
    0
    TTenant ID (example value is the default value)
    000000000000001
    ssnSocial mongodb host name
    localhost
    sspSocial mongodb port
    27017
    ssdSocial mongodb database name (see the installation worksheet for the name of the database specified during Smart IT server installation
    social
    ssdu(Optional) If the database has a user/password set, specify the Social mongodb username
    DBAdmin
    ssdp(Optional) If the database has a user/password set, specify the Social mongodb password
    DBPassword
    d1(Optional) To migrate data from a specific date range, specify the start date in yyyy-mm-dd format
    2014-06-30
    d2(Optional) To migrate data from a specific date range, specify the end date in yyyy-mm-dd format
    2015-05-30
    type(Optional) Type is equivalent to the status in BMC Remedy ITSM. Ticket types to migrate are open, closed, resolved, completed, and cancelled. If a value is omitted, the default value of open is used.
    open
    o

    (Optional) Comma-separated list of object types to import are all, incident, user, workorder, request, knowledge, change, userasset, companyasset, and allcsv. If a value is omitted, the default value of all is used. Note that all includes incident, user, workorder, request, knowledge, and change.

    Companyasset imports all assets from a specified company.

    Userasset imports all assets related to people and support groups.

    Allcsv specifies records in CSV files for all record types (incident, user, workorder, request, knowledge, and change).

    all
    csv(Optional) CSV file that specifies the records to import. -o allcsv indicates the folder location containing the CSV files that specify the records to import. Example CSV files are provided with the utility.
    CSV folder
    company(Optional) When you import an object type of companyasset, specify the company name. Assets for that company are migrated.
    Calbro Services
    h(Optional) Use this parameter on its own to display usage help for the onboarding utility.Not applicable
    C(Optional) Chunk size when retrieving from the BMC Remedy ITSM database.No example provided
    info(Optional) Displays information about onboarded records and the approximate time taken to onboard them.Not applicable
    v(Optional) Use this parameter on its own to display the onboarding version number, and exit without migrating data.Not applicable

The relationships between -o (object), -type (open, closed, resolved, or completed), and status are listed in the following table:

-o parameter value-type parameter valuestatus values
request

open

< 6000
closed9000
completed6000
incidentopen0, 1, 2, 3
closed5
resolved4
workorderopen0, 1, 2, 3, 4
closed8
completed5
knowledgeopenPublished, Draft
closedClosed
changeopenAny value except Closed'or Cancelled
closedClosed
cancelledCancelled

 

Parameter examples

DescriptionExample

Import open records—Imports incidents, work orders, requests, and knowledge articles that have a status of open in BMC Remedy ITSM.

BMC recommends that you run this example the first time you run the onboarding utility.

-x itsmServer.calbro.com -u Demo -p "" -t 0 
-ssn localhost -ssp 27017 -ssd social_db_name
-ssdu DBAdmin -ssdp DBPassword
Import only open incidents and work orders.
-x itsmServer.calbro.com -u Demo -p "" -t 0 
-ssn localhost -ssp 27017 -ssd social_db_name
-ssdu DBAdmin -ssdp DBPassword -o incident, workorder
-type open
Import completed requests.
-x itsmServer.calbro.com -u Demo -p "" -t 0 
-ssn localhost -ssp 27017 -ssd social_db_name
-ssdu DBAdmin -ssdp DBPassword -o request
-type completed
Import assets using a CSV of GUIDs.
-x itsmServer.calbro.com -u Demo -p "" -t 0 
-ssn localhost -ssp 27017 -ssd social_db_name
-ssdu DBAdmin -ssdp DBPassword -o assetcsv
-csv c:\utility\asset.csv

Import open records for a new tenant on a multitenancy system—In this example, incidents, work orders, requests, and knowledge articles for the tenant Calbro IT, with a status of open in BMC Remedy ITSM, are imported.

-x itsmServer.calbro.com -u Demo -p "" -t 0 
-T CalbroIT -ssn localhost -ssp 27017
-ssd social_db_name -ssdu DBAdmin -ssdp DBPassword
Tickets (incidents, work orders, requests, and knowledge articles) can be imported by using a .csv file containing the ticket IDs. The sample is attached to the .csv build folder.
-x itsmServer.calbro.com -u Demo -p "" -t 0 
-ssn localhost -ssp 27017 -ssd social_db_name
-ssdu DBAdmin -ssdp DBPassword -o allcsv
-csv c:\utility\csv\

Tickets (incidents, work orders, requests, and knowledge articles) show information about records and the approximate time taken.

-x itsmServer.calbro.com -u Demo -p "" -t 0 
-ssn localhost -ssp 27017 -ssd social_db_name
-ssdu DBAdmin -ssdp DBPassword -info
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Jamie Boley

    I think this documentation needs to be updated to include onboarding of problem and known errors.  Also, are there additional types for the asset module now that it's included?

    Jun 28, 2016 11:31
  2. Earl Edwards

    Where do you find the tenant id for multi tenancy?

    Aug 04, 2016 06:53
  3. Dmitry Baryshnikov

    I would agree with Jamie Boley comment - shouldn't the documentation be updated? I heard there's some -o companyasset parameter, and also in the text you're mentioning -o assetcsv parameter, where the CSV example would be great to have. May be there're more - could you refine please?

    Dec 05, 2016 09:40
  4. Roshan Shinde

    Team, 

    Is there any anti-onboarding utility available ? i.e negate the onboarding utility that has been previously executed successfully.

    Jan 03, 2017 08:20
    1. Rakhi Rathod

      Hi Roshan,

      Thank you for the comment. I discussed it with Smart IT SME. We need addition info from you about the use case where you want to negate the onboarding utility. What are you trying to do, where did you get blocked, do you want to delete tickets and users or archive them, and other relevant info.

      Let us know.

       

      Thanks,

      Rakhi

      Jan 09, 2017 02:36
      1. Roshan Shinde

        Hi Rakhi,

        I have asked about the nullification of the onboarding utility with regards to the case where SmartIT has to be upgraded to a newer version. Is it not required ?

        Or lets assume another case where I want to completely uninstall the Smart IT application from the server and later perform a fresh installation of a newer version. Under this scenario too, should we not undo the changes done by the onboarding utility ?

         

        Regards,

        Roshan.

        Jan 09, 2017 05:54
        1. Rakhi Rathod

          Thanks, Roshan. I forwarded the details to the SME.

          We are working towards resolving the issue.

          I'll keep you updated.

           

          Regards,

          Rakhi 

          Jan 09, 2017 08:42
          1. Roshan Shinde

            Hi Rakhi,

            Have you received any update from the SMEs yet? 

             

            Regards,

            Roshan.

            Jan 23, 2017 06:59
            1. Rakhi Rathod

              Hi Roshan,

              I'm extremely sorry for my late reply. I had a discussion with the SME.

              In both the scenarios there isn't any tool to delete the data that is on-boarded.

              The work around is:

              • Identify the tickets and users then delete using deteleTickets.js and deleteUsers.js script.
              • Or archive based on the date.
              • Or delete the social (mongo db) db and restart social service (which will delete on-boarded and current data)

               I'm updating this topic to add all these details.

              Hope this info helps you.

              Thanks,

              Rakhi

               

              Jan 23, 2017 08:58
              1. Roshan Shinde

                Hi Rakhi, 

                Thanks for your response.

                Regarding the 3rd option, can you please guide us with the exact steps on how to delete the social (mongo db) db ? I am a newbie to MongoDB and I have least knowledge on the same.

                 

                Regards,

                Roshan.

                Feb 19, 2017 11:26
              1. Sumeet Das

                what is the location of the deteleTickets.js and deleteUsers.js scripts ?

                Aug 21, 2018 11:21