データ マネージャーを使用する準備はどのようにすればよいですか?

• ユーザー側で必要な操作について

  • ステップ 1 - ツールを決定する

    • CSV ファイル収集に関するその他の注意事項

    • ファイル形式の詳細

  • ステップ 2 - スコープとフィルタリング要件を決定する

  • ステップ 3 - "アダプタ クライアント" と "クレンジングおよびインポート クライアント" のインストール先を決定する

    • データのアップデート

  • ステップ 4 - データや認証情報を取得する

    • CSV ファイルのさまざまなデータ ソース タイプ用に提案されたフィールド

 To get your Data Manager up and running smoothly, you'll need to follow these key steps to prepare your system and data for integration.

Steps to Follow:

1. Choose the Tools to Connect

2. Define Your Scope and Filtering Requirements

3. Install the Necessary Clients

4. Gather Data and Credentials

Step One - Choose the Tools to Connect

Start by selecting the tools you want to integrate with Data Manager. Limit your initial selection to five tools; you can add more later.

Check if any tools have pre-existing connections. Review this list for details on available connections and what information you’ll need from each tool’s Subject Matter Expert (SME).

Coordinate with each SME to obtain either a comma-separated file (CSV) or specific connection details (like API or database information).

CSV ファイル収集に関するその他の注意事項

Step Two - Define Your Scope and Filtering Requirements

Understand the data coverage of the tools you plan to integrate into Data Manager.

For example, if you're using Active Directory (AD), you need to know how many AD domains your organization has and ensure they align with your ITSM tool, which might cover all domains.

For IT Asset Management (ITAM) solutions, determine what types of endpoints are relevant (for example, laptops, servers) and ensure they match across systems. If your ITAM solution tracks non-computer assets like chairs or desks, you'll need to set up filters in Data Manager to exclude these items, keeping the scope consistent with other systems.

Understand the criteria each system uses to classify data as active or stale. For example, Active Directory might consider data stale if it's over 90 days old, while another tool might have different criteria. Know these rules for each system to ensure accurate data integration. You may need to engage with the tool SME to understand the details.

Step Three - Install the Necessary Clients

You need two apps: the Adapters client and the Cleanse and Import client. Here's how to set them up:

• Adapters Client: Install this locally on a machine or server within your environment. You can download it via the Atlassian Marketplace. Having the machine in your local environment limits the security exposure between data sources and the internet. The local server will need to be able to see each of your data sources and your Jira Service Management Assets instance. Without the local server, all data sources would be exposed directly to the internet.

• Cleanse and Import Client: This client should be installed on your local machine or server. It cleanses and imports data before sending it to the Assets Data Manager. This can also be found in the Atlassian Marketplace - . If you're using API or database connections, this client ensures data can be refreshed automatically according to your schedule.

The Adapters Client and Cleanse and Import Client are bundled together on the Atlassian Marketplace download.

When running jobs from the Adapters client and the Cleanse and Import client, you'll need your Token and workspace-ID. You can generate these tokens by:

• Navigate to your service project and go to Assets > Global Configuration.

• Select the Data Manager tab.

• Select the token you want to generate.

Note - the Adapters & Cleanse and Import client tokens are different but created from the same location. The workspace-ID is the same for both clients.

Step Four - Gather Data and Credentials

Connect with your SMEs to obtain database access, API details, or prepare your flat files.

Some out-of-the-box Adapters are ready for Data Manager. The Adapters page provides detailed information on each Adapter, including connection requirements and the data attributes returned to Data Manager.

Suggested Fields for Flat Files

Here are some suggested fields for Flat files, which you can share with your SME as examples of what columns might be needed. The field names and availability may vary based on the tools in your organization. If Data Manager is used for asset or configuration item comparison, aim to include columns marked as "Required = Mandatory."

資産管理

CMDB (Jira Service Management Assets, ServiceNow etc)

System Management or Patching tool (eg SCCM, BigFix etc)

Cyber / Security (eg Qualys, Crowdstrike, Rapid-7, MS Defender)

Active Directory > Computer

Active Directory > Subnets

SolarWinds (Network object class)

Note: If SolarWinds is also discovering Servers, then that information could also be put into the Compute Object.

ユーザー