Assets - Jamf Integration
統合によるインポート
このページの内容
関連コンテンツ
- Secure Bitbucket with Apache using SSL
- Integrate Bitbucket with Apache HTTP Server
- Secure Bitbucket behind nginx using SSL
- Secure Bitbucket behind HAProxy using SSL
- Secure Bitbucket with Tomcat using SSL
- Setting up SSH port forwarding
- Moving Bitbucket Server to a different context path
- Change Bitbucket's context path
- You are accessing Bitbucket from a URL that does not match the configured base URL
- Install Bitbucket Server on Linux from an archive file
Assets - Jamf Integration allows you to assemble detailed data from the Jamf Platform. Import the data automatically into Assets and use Jira to relate Incidents, Problems and Change Requests to all your CIs.
概要
Being able to detect and collect data from your Jamf assets is a very common request, in fact all enterprises need to be in IT-Ops Control.
Assets - Jamf Integration is unique in the following aspects:
- It's the only Jamf discovery solution that is integrated tightly with the Jira platform
- Jira で実際の CMDB を提供する唯一のソリューションである。
- Jira で依存関係マッピングと影響分析を提供する唯一のソリューションである。
- Jira のアセットに焦点を当てた豊富な自動化フレームワークを提供する唯一のソリューションである。
Assets - Jamf Integration fetches assets using the Jamf API that is used by your enterprise's network.
A discovered object is explored to capture the configuration, provisioning and current status. All the collected data is sent to the CMDB in Assets and Jira.
はじめる前に
- Assets - Jamf Integration requires both Jira (Core, Software, or Service Management) and Assets to function.
You can download the latest version of Assets - Jamf Integration from Atlassian Marketplace.
You need to setup Assets in order to import data from Jamf. Set up Assets
Get started with Assets - Jamf Integration
次は、開始に役立つページのリストです。
関連コンテンツ
- Secure Bitbucket with Apache using SSL
- Integrate Bitbucket with Apache HTTP Server
- Secure Bitbucket behind nginx using SSL
- Secure Bitbucket behind HAProxy using SSL
- Secure Bitbucket with Tomcat using SSL
- Setting up SSH port forwarding
- Moving Bitbucket Server to a different context path
- Change Bitbucket's context path
- You are accessing Bitbucket from a URL that does not match the configured base URL
- Install Bitbucket Server on Linux from an archive file