Configuring ServiceNow for Export

FlexNet Manager Suite 2021 R1 (On-Premises)

Now that you have a MID server installed, two further configuration points for ServiceNow remain:

• Identifying the MID server as the one to use for the exports to FlexNet Manager Suite
• Scheduling the exports from ServiceNow.

Continue the following while still logged into ServiceNow with administrator privileges.

To configure ServiceNow for export:

1. In ServiceNow, go to Flexera Integration > Integration Properties.
2. In ServiceNow, in integration application 5.x, go to Flexera Integration > Integration Properties, or in integration app 4.x, see FlexNet Manager Suite > Integration Properties.
3. In the list of Integration Properties, scroll down to the MID server name field (in the ServiceNow → FNMS section), and enter the full name of the MID server.
4. Optionally, in the Export file path field, enter an alternative file path location to store the XML file (instead of the default MID server location). Because the FlexNet Beacon reads this file using the business adapter, FlexNet Beacon needs access to this file location.
5. Scroll down (if necessary), and click Save.
6. In ServiceNow, in integration application 5.x, go to Flexera Integration > Export Configuration > Scheduled Jobs, or in integration app 4.x, go to FlexNet Manager Suite > Scheduled Jobs.
   The list of standard jobs to export data from ServiceNow is displayed, including:

   • Export Assets from ServiceNow
   • Export Contracts from ServiceNow.

   Each of these jobs needs to be configured for your environment.

7. Add a Run as column to this page and enter the integration user ID in the column for both jobs. To do so:
   1. Click the Personalized List (gear) icon in the upper left corner at the top of list of scheduled jobs.
   2. On the Personalize List Columns dialog, select Run as from the Available columns and move it to the Selected columns.
   3. On the Scheduled Script Executions page, change the Run as user (that is blank by default) to the integration user ID (see Creating a ServiceNow Integration User).
8. Click the first export task to schedule (such as Export Assets from ServiceNow).
   The Scheduled Script Execution properties are displayed.

   Note: The MID server collects the exported XML data in chunks, such that the XML file is not well formed until the last chunk has been received. Be sure to schedule sufficient time for the exports to complete before the scheduled import from the MID server into FlexNet Manager Suite.
9. Change the value in the Run field to your desired schedule.
   These data exports may be large, based on the size of your ServiceNow repository. A common practice would be to choose Weekly exports.

   Tip: ServiceNow by default limits its exports from the database to 10,000 records (for a general discussion, see https://community.servicenow.com/community/blogs/blog/2014/08/01/increasing-the-export-limit, but note that this page discusses limits for exports from the ServiceNow user interface grids, which are not relevant to the database exports to FlexNet Manager Suite). You can modify the maximum number of records exported from ServiceNow by having your ServiceNow administrator add the property glide.db.max_view_records and setting a new limit. For instructions on adding the property, see http://wiki.servicenow.com/index.php?title=Adding_a_Property#gsc.tab=0.
10. Use the additional fields that appear to complete configuring your scheduled job.
    For example, for Weekly exports, set the Day, and Time of day, when the export should occur. An off-peak time is preferable.
11. Click Update to save your changes.
    Repeat the scheduling for the Export Contracts from ServiceNow task.
12. With both exports now scheduled, run a test of each by clicking Execute Now on the associated Scheduled Script Execution properties page.
    (This same button can be used to run the export if you chose the Run On Demand setting for the schedule.) Use the test to assess the time taken to complete the export and finish a well-formed XML file on the MID server, as a check on your scheduling plans. The test also allows you to troubleshoot any problems.
13. Monitor overall progress in ServiceNow by going to Flexera Integration > Export History > Export Runs in integration application 5.x, and in integration app 4.x, go to FlexNet Manager Suite > Integration History > Export Runs.
    The State column on this view shows the progress of export, and the Stage column displays File Completion when the XML file is done.
14. On the MID server, check for well-formed (complete) XML files.
    The file names are of the form x_fls_flexera_fnms_ExportType.xml, where the placeholder ExportType is either Asset or Contract.

This completes the configuration of ServiceNow for data flows from ServiceNow to FlexNet Manager Suite. These same data flows also require some configuration of FlexNet Manager Suite to receive the data. This side of the configuration is covered next.