With the release of Assets Data Manager coming up, now is a great time to prepare for when the feature will be available within Assets in Jira Service Management.
This page will help you understand the Architecture, infrastructure requirements, and some of the planning you need to do to be ready to roll.
The important thing to note in the above diagram is that the first two boxes are in your environment.
Source Data
Local Server
The local server is required to use the Adapters Client (which consumes data from your data sources) and the Cleanse and Import Client (which leverages your local system to clean and reconcile your data). This server is in your environment and can be either OnPrem or in the Cloud. The important piece is that it has the ability to connect to any location where data is sourced from and be able to pass data up to JSM Assets, including Data Manager.
Note: For quick testing, this can also be a workstation.
As an example, you’ve decided to start with the Compute Object Type, your organisation has about 20,000 compute devices, including physical and virtual end points in both the infrastructure server and end user computing space; and you are going to connect five (5) data sources using the Flat File method as a quick test. That is; you can get Data Manager set-up quickly loading CSV files and will work to automate the process in the future.
To be really ready, prior to starting your set-up of Data Manager - work with your tool SME’s to ensure that they are able to provide an unfiltered* CSV extract of their tool, including the columns (or attributes) you want Data Manager to utilise. If you’re looking at the Compute object type, include all the types of things you’d look at when buying a new computer (eg manufacturer, model, processor, CPU count, operating system, serial number, RAM, disk space, etc and of course an asset name).
* An unfiltered extract is requested, as this allows full cross comparative data analysis to occur within Data Manager. As an example; if may show where one data source has identified an end point are retired but another tool may still have it as active.
The above example, fits in the blue box below; so above our Operating System and standard organisation requirements (i.e. for monitoring tools etc), our RAM requirements are 8gb and an additional 50gb storage to store the CSV files you collect.
The Data Manager Cleanse & Import client for JSM Assets can run on many operating systems including Windows, Linux, or MAC.
Once you have your local server set-up and you’ve worked out the tools to connect, plus obtained extracts** for those tools, you will be ready to roll when Assets Data Manager is released.
** Several out of the box adapters exist; however, obtaining appropriate credentials can often slow down the set-up process. Therefore, CSVs are a great way to see the tool up and running quickly. You can always switch to those adapters at a later stage.
Karyn Findlay
Product Manager | Jira Service Manager
Atlassian
Australia
3 accepted answers
6 comments