User Tools

Site Tools


msp_manage_customers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
msp_manage_customers [2018/09/13 11:02]
robyn.lin
msp_manage_customers [2018/12/26 11:29] (current)
robyn.lin
Line 7: Line 7:
 The following update sets should be installed: The following update sets should be installed:
  
-1. Perspectium for ServiceNow ​patch2 ​update set <WRAP round info>be sure to  Finish Install, configure ​the Perspectium ​Propertiesand Test Connection</​WRAP>​+1. (Latest) ​Perspectium for ServiceNow update set <WRAP round info>Make sure to **Finish Install** (found under** Perpectium** > **Control and Configuration** > **Finish Install**). Configure ​the **Properties** (found under **Perspectium** > **Control ​and Configuration** > **Properties**). Run **Test Connection** to make sure the instance is properly set.</​WRAP>​
  
-2. Perspectium Common Endpoint ​patch1 ​update set+2. Perspectium Common Endpoint update set
  
 3. Perspectium Common Incident update set 3. Perspectium Common Incident update set
Line 15: Line 15:
 4. Perspectium SIAM Mapping UI update set 4. Perspectium SIAM Mapping UI update set
  
-5. Perspectium MSP Base update set+5. Perspectium MSP Gateway ​update set
  
  
-Once the update sets have been installed:+**Once the update sets have been installed:**
  
 1) Navigate to the Perspectium MSP application menu and click Finish Install (this process may take several minutes to complete). 1) Navigate to the Perspectium MSP application menu and click Finish Install (this process may take several minutes to complete).
Line 30: Line 30:
 {{:​msp_new_customer.png|}} {{:​msp_new_customer.png|}}
  
-Company (lookup field): populate with the company reference. Active checkbox: indicates whether the Company is Active or not (defaults to Active).+Company (lookup field): populate with the company reference. 
 + 
 +Active checkbox: indicates whether the Company is Active or not (defaults to Active).
  
 3) To see a list of all customers, go to the Manage Customers tab under the Perspectium MSP application menu.  3) To see a list of all customers, go to the Manage Customers tab under the Perspectium MSP application menu. 
Line 40: Line 42:
  
 ==== Creating a New Customer Endpoint (ServiceNow) ==== ==== Creating a New Customer Endpoint (ServiceNow) ====
 +
 +To create a new customer endpoint. Click the **New** button from the **MSP Customer Endpoints** table list. Complete the form below by filling in all required fields.
  
 {{:​msp_new_cust_endpoint.png|}} {{:​msp_new_cust_endpoint.png|}}
Line 45: Line 49:
 **Company**:​ will be pre-populated with the current company name. **Company**:​ will be pre-populated with the current company name.
  
-**(Endpoint) ​Type**: a dropdown with the choices of ServiceNow and Remedy. If ServiceNow is selected, the fields User, Password, and Requires Repeater Agent will not appear as ServiceNow does not use these fields. ​+**Type (Endpoint)**:​ a dropdown with the choices of ServiceNow and Remedy. If ServiceNow is selected, the fields User, Password, and Requires Repeater Agent will not appear as ServiceNow does not use these fields. ​
  
 **ITSM Module**: a dropdown with one choice of Incident Management. **ITSM Module**: a dropdown with one choice of Incident Management.
Line 51: Line 55:
 Currently Incident Management will be the only supported module in MSP Version 1. Currently Incident Management will be the only supported module in MSP Version 1.
 </​WRAP>​ </​WRAP>​
- 
-**Replication Group**: represents the assignment group for triggering replication of incidents. 
  
 **Integration User**: this field is automatically populated with a generated user based on company name. You can also use the dropdown menu to change the integration user. **Integration User**: this field is automatically populated with a generated user based on company name. You can also use the dropdown menu to change the integration user.
 +
 +*In order to trigger replication of incidents, the domain of the incident (based on caller'​s company) and the customer endpoint domain must match.
  
 **Active**: a checkbox indicating if the endpoint is active or not. **Active**: a checkbox indicating if the endpoint is active or not.
  
-**Endpoint ​URL**: the customer/​target endpoint URL or instance name (for ServiceNow endpoints). If an Endpoint Alias is not specified, this field will be used as the Source/​Target System display name when generating the MSP Mappings table.+**URL or Instance (Endpoint)**: the customer/​target endpoint URL or instance name (for ServiceNow endpoints). If an Endpoint Alias is not specified ​(below), this field will be used as the Source/​Target System display name when generating the MSP Mappings table.
  
-**Endpoint ​Alias**: this field is optional; if you choose to give this endpoint an alias it  will be used as the Source/​Target System display name when generating the MSP Mappings table (instead of the Endpoint URL).+**Alias ​(Endpoint)**: this field is optional; if you choose to give this endpoint an alias it  will be used as the Source/​Target System display name when generating the MSP Mappings table (instead of the Endpoint URL).
  
-Once you click Save (or Save and Exit)the MSP Endpoint Table with the newly added endpoint will be generated. In addition, the Table Map, Transform Map, Dynamic Share, and Shared Queue will automatically be generated for this newly created endpoint configuration. If you click on the "Edit Dynamic Share" link, it will direct you to the generated dynamic share. If you click on the "View Import Set Table" link, it will direct you to a list view of the dedicated import set table for this customer endpoint+Once all required fields are filled in, click **Submit**
  
-In addition, the MSP Mappings table will automatically be generated below the endpoint table (see screenshot below). ​+The MSP Endpoint Table with the newly added endpoint will be generated. The Table Map, Transform Map, Dynamic Share, and Shared Queue will automatically be generated for this newly created endpoint configuration. If you click on the "Edit Dynamic Share" link, it will direct you to the generated dynamic share. If you click on the "View Import Set Table" link, it will direct you to a list view of the dedicated import set table for this customer endpoint.  
 + 
 +<WRAP round info> 
 +***Note**: The Dynamic Share will be created with Base64 Encode Only cipher. If you wish to use another cipher type, the encryption/​decryption keys on the MSP Gateway and Customer Endpoint systems must match. 
 +</​WRAP>​ 
 + 
 + 
 +Additionally, the MSP Mappings table will automatically be generated below the endpoint table (see screenshot below). ​
  
 {{:​msp_mappings.png|}} {{:​msp_mappings.png|}}
  
  
-====MSP Mappings ​table====+====MSP Mappings ​Table====
  
-Describes the bidirectional flow of messages from the Source to Target system. *The rows on the Mappings table cannot be edited.+Describes the bidirectional flow of messages from the Source to Target system.
  
-**Source system**: indicates where the message originated ​from. As mentioned ​before, if an Alias was provided in the endpoint configuration it will be used as the Source system value, otherwise it will default to the Endpoint URL.+Note: The rows on the Mappings table cannot be edited. 
 + 
 +**Source system**: indicates where the message originated. As mentioned ​previously, if an Alias was provided in the endpoint configuration it will be used as the Source system value, otherwiseit will default to the Endpoint URL.
  
 **Source Format**: type of the source message. **Source Format**: type of the source message.
Line 82: Line 95:
  
 **Target System**: indicates the message'​s target destination. If an Alias was specified in the endpoint configuration it will be used as the Target system value, otherwise it will default to the Endpoint URL. **Target System**: indicates the message'​s target destination. If an Alias was specified in the endpoint configuration it will be used as the Target system value, otherwise it will default to the Endpoint URL.
 +
 +====MSP Share Conditions====
 +The conditions specified in this related list define the conditions that must be met for replication to occur and the action suffix produced in the name field of the outbound message. ​  The conditions are executed in sequence from lowest to highest order value.
 +
 +{{:​ShareConditions.png|}}
  
 ==== Creating a New Customer Endpoint (Remedy) ==== ==== Creating a New Customer Endpoint (Remedy) ====
  
 [[http://​wiki.perspectium.com/​doku.php?​id=msp_remedy_endpoint|Remedy Customer Endpoint]] [[http://​wiki.perspectium.com/​doku.php?​id=msp_remedy_endpoint|Remedy Customer Endpoint]]
 +
 +==== Cloning an Existing Endpoint ====
 +
 +{{:​msp_clone_existing.png|}}
 +
 +To clone any existing endpoint, click the blue Clone Existing button located next to the New Button. You will be directed to the following page (below) where you will choose the endpoint to clone, enter the new endpoint instance/​URL,​ endpoint alias (if any), and user and password (if you are cloning a non-ServiceNow endpoint). ​
 +
 +The optional alias field will be pre-populated with the Customer and Endpoint type; you can input a different alias name or choose not to use an alias. This action will create a new shared queue using the new endpoint instance/​URL,​ and will clone the selected Endpoint record and all its associated artifacts (SIAM Mappings, Import Set Table, Dynamic Share, Outbound Table Map, Transform Map, and Inbound Table Map) under the current customer. ​
 +
 +{{:​msp_clone_wizard.png|}}
  
 ==== Viewing an Existing Customer ==== ==== Viewing an Existing Customer ====
Line 103: Line 131:
 ***Note**: If you click the Active checkbox to activate or deactivate an endpoint the Dynamic Share and Transform Map for that specific endpoint will be activated/​deactivated accordingly. ​ ***Note**: If you click the Active checkbox to activate or deactivate an endpoint the Dynamic Share and Transform Map for that specific endpoint will be activated/​deactivated accordingly. ​
 </​WRAP>​ </​WRAP>​
 +
 +==== Export to Update Set ====
 +If you click this button, the current Company, Domain, Customer, Endpoint record, and all associated artifacts (Mappings, Import Set Table, Dynamic Share, Table Map, Transform Map, Inbound Table Map, and Outbound Table Map) will be pushed to the current update set. The Share Conditions will also be pushed to the current update set. You will be directed to the following screen where you must enter the new Gateway ServiceNow instance information,​ and the new target Endpoint instance (or URL if using a non-ServiceNow endpoint). The optional alias field will be pre-populated with the Customer and Endpoint type; you can input a different alias name or choose not to use an alias.
 +
 +{{:​msp_export_wizard.png|}}
 +
 +<WRAP round info>
 +***Note**: After installing this update set, you must create your own Shared and Subscribe queues (and update the Dynamic Share target queue accordingly).
 +</​WRAP>​
 +
 +
 +{{:​msp_update_shared_queue.png|}}
 +
 +
 +To create the shared queue and update the Dynamic Share target queue, you can click on the "Edit Dynamic Share" hyperlink on the MSP Customer Endpoints screen. ​
 +
 +
 +{{:​msp_customer_endpoints.png|}}
 +
 +
 +Once you are directed to the Replicator Configuration - incident [Shared view*] screen, navigate to the Target queue field, click on "​Lookup using list" (Search icon), and then click the New button.
 +
 +
 +{{:​msp_new_queue1.png|}} ​
 +
 +
 +{{:​msp_new_queue2.png|}} ​
 +
 +
 +After the shared queue is created and on the Replicator Configuration - incident [Shared view*] screen, navigate to Related Links and click on "Reset Dynamic Share Rule."
 +
 +
 +{{:​msp_reset_dynamic_share_rule.png|}} ​
 +
 +
 +When installing an update set that contains artifacts associated with a MSP customer endpoint where type = BMC Remedy, you will also be prompted to update the Dynamic Share target queue accordingly. ​
 +
 +On the Replicator Configuration - incident [Shared view*] screen, navigate to Related Links and click on "Reset Dynamic Share Rule."
 +
 +
 +{{:​msp_reset_dynamic_share_remedy.png|}}
 +
 +
 +To complete the process, navigate to the Queues - psp.in.siam.client.remedy [Share view] screen, and update any applicable details accordingly (i.e.Queue user, Queue user password)
 +
 +
 +{{:​msp_remedy_shared_queue.png|}}
 + 
  
 ==== Deleting a Customer Endpoint ====  ==== Deleting a Customer Endpoint ==== 
msp_manage_customers.1536861767.txt.gz · Last modified: 2018/09/13 11:02 by robyn.lin