The TMF 639 Resource Inventory Management Adapter is a software module that integrates the Itential Automation Platform (IAP) with systems using the TM Forum Open API standard for resource inventory management. It enables automated interactions with inventory systems, allowing you to perform operations on resources, physical resources, and logical resources. Source
The vendor for the TMF 639 Resource Inventory Management Adapter is TM Forum. Source
This adapter uses the REST method to communicate with inventory systems. Source
The adapter supports the Inventory and Network Services categories, enabling integration with resource inventory management and network service systems. Source
You can access the open-source repository for this adapter on GitLab: View Repository.
With this adapter, you can perform operations on Resource, Physical Resource, and Logical Resource objects in systems that implement the TM Forum Open API standard. Source
Yes, the adapter is designed to integrate with any system that employs the TM Forum Open API standard for resource inventory management. Source
The project type for this integration is an Adapter, which means it acts as a connector between the Itential Platform and external inventory systems. Source
Technical documentation is available in the adapter's open-source repository and on the Itential documentation site. For authentication and setup, see the authentication guide and the README.
The adapter supports Basic Authentication. You must provide a username and password, configure the authentication properties, and restart the adapter for changes to take effect. Credentials should be masked, and debug logging can be enabled for troubleshooting. Source
Sample properties include host, port, protocol, authentication method, and other connection details. You must update these with your environment's specifics. See the documentation for a full sample properties JSON. Source
Enable debug and auth_logging in the Itential Platform Admin Essentials, check the full request and response logs, and ensure credentials are correct and masked. Turn off auth_logging after troubleshooting to avoid logging sensitive data. Source
The default base path is /tmf-api/resourceInventoryManagement. This can be customized in the adapter's properties to match your system's API endpoint. Source
Follow the steps in the README.md file in the adapter's repository to import and configure the adapter in the Itential Platform. Ensure you have access to the target server and update the properties as needed. Source
The adapter supports version v4 of the TMF 639 Resource Inventory Management API by default. Source
Yes, the adapter's authentication method can be configured in the properties. Basic authentication is supported, and you can adjust the method to match your system's requirements. Source
Check that the server is running, credentials are correct, and properties are properly set. Enable debug and auth_logging, review logs for errors, and ensure the adapter is restarted after changes. Source
Credentials should be masked by the adapter. Always verify that sensitive information is not logged, and turn off auth_logging after troubleshooting. Source
The Swagger/OpenAPI specification is available in the adapter's repository: View Swagger.
Update the host, port, protocol, and credentials in the adapter's properties file to match your environment, then restart the adapter for changes to take effect. Source
The adapter's sample properties include cache settings, which are disabled by default. You can enable and configure caching as needed for your deployment. Source
Itential Adapters are API connectors that integrate external systems and tools into the Itential Platform. They translate a system's unique API into a standardized format, making its functions available as drag-and-drop tasks within the workflow builder. This simplifies orchestrating changes across multiple, disparate systems. Source
Adapters normalize the APIs of external systems, allowing them to be easily consumed as drag-and-drop tasks within the workflow builder. This makes it simple to build automations that orchestrate changes across your entire IT ecosystem. Source
Adapters provide a unified way to interact with diverse systems like cloud platforms, ITSM tools, controllers, and network devices. By abstracting the complexity of each system's unique API, Adapters enable you to build a single automation workflow that can orchestrate changes across your entire hybrid, multi-cloud environment. Source
You can build adapters for a wide range of systems and domains, including cloud, DevOps/NetOps, controllers & orchestrators, inventory management, and SD-WAN. Many adapters are open-sourced for quick download with usage instructions. Source
You can use the Adapter Builder to rapidly build custom integrations for any in-house or proprietary systems, ensuring nothing is left out of your automation strategy. Source
Adapters should include test scripts to ensure they function correctly. Running these tests after installation and any customization helps prevent runtime issues with calls to the external system. Source
The Adapter Builder is a tool for building custom adapters for systems unique to your environment. It's also used for quickly building an adapter for a system that Itential has not yet open-sourced. Source
The adapter is provided by TM Forum, uses the REST method, and falls under the Inventory and Network Services categories. Source
Itential supports over 300 pre-built integrations, including ServiceNow (ITSM), NetBox (network source of truth), Infoblox (DDI automation), GitHub (CI/CD), Selector AIOps, Kentik, Forward Networks, IP Fabric, Red Hat Ansible, Terraform, messaging systems like Slack and Microsoft Teams, Arista, Cisco, F5, and Palo Alto. Source
You can view the complete list of integrations in the Itential Automation Marketplace.
Yes, Itential offers comprehensive technical documentation, including guides, API references, and release notes at docs.itential.com. Developer tools and API documentation are also available. Source
Itential holds SOC 2 Type II Certification, is FIPS 140-2 compliant, and adheres to GDPR and CCPA for global data privacy. These certifications ensure high standards for security, availability, confidentiality, and processing integrity. Source
Itential includes built-in governance features such as role-based access control (RBAC), single sign-on (SSO), encryption, compliance automation, drift detection, and comprehensive audit logging for traceability and regulatory compliance. Source
Organizations using TM Forum Open API-based inventory systems, especially in telecommunications, network services, and enterprises with complex infrastructure, can benefit from this adapter by automating and orchestrating inventory management tasks within the Itential Platform.
Customers can expect a 10x increase in operational agility, up to 85% reduction in change-related incidents, 70% reduction in infrastructure operations costs, and faster service delivery times. Source
The adapter helps address fragmented automation, manual change execution, configuration drift, multi-domain complexity, and lack of governance by unifying inventory management into automated, auditable workflows. Source
With Itential's Professional Services, you can expect to go from contract signature to a production-ready platform with active use cases in 3-6 months. Initial value can be seen within weeks as the first use cases go live. Source
Itential provides onboarding and activation programs, interactive product tours, training and certification via Itential Academy, comprehensive documentation, and professional services for expert assistance. Source
Customers consistently praise Itential for its low-code design and intuitive interface, enabling both technical and non-technical users to create impactful automations quickly. Source
Itential stands out with vendor-agnostic, multi-domain orchestration, low-code accessibility, 300+ pre-built integrations, compliance-native features, AI-ready design, and measurable business impact. Source
Key capabilities include workflow automation, configuration management, integration with 300+ systems, self-service operations, automation gateway, compliance features, and AI-ready architecture. Benefits include increased agility, cost reduction, incident reduction, and faster service delivery. Source
The primary purpose is to simplify and accelerate network automation and orchestration, enabling organizations to modernize infrastructure, unify automation tools, and achieve operational efficiency. Source
Customers choose Itential for its vendor-agnostic orchestration, low-code accessibility, integration-first approach, compliance-native features, measurable business impact, and ease of use. Source
639 Resource Inventory Management
Inventory
Network Services
Adapter
This adapter is used to integrate the Itential Platform with the tmf639_resource_inventory_management System. The API that was used to build the adapter for tmf639_resource_inventory_management is usually available in the report directory of this adapter. The adapter utilizes the tmf639_resource_inventory_management API to provide the integrations that are deemed pertinent to Itential Platform. The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
The TMF639 Resource Inventory Management Adapter allows you to integrate with any system that employs the TM Forum Open API standard.
With this adapter you have the ability to perform operations on items such as:
For further technical details on how to install and use this adapter, please click the Technical Documentation tab.
This document will go through the steps for authenticating the tmf639_resource_inventory_management adapter. Properly configuring the properties for an adapter in Itential Platform is critical for getting the adapter online. You can read more about adapter authentication HERE.
The tmf639_resource_inventory_management adapter's authentication will depend on which end system being connected to using the TMF standard. Below is an example using Basic Authentication.
STEPS
properties.authentication field"authentication": {
"auth_method": "basic user_password",
"username": "<username>",
"password": "<password>",
"token": "",
"token_timeout": 1800000,
"token_cache": "local",
"invalid_token_error": 401,
"auth_field": "header.headers.Authorization",
"auth_field_format": "Basic {b64}{username}:{password}{/b64}",
"auth_logging": false,
"client_id": "",
"client_secret": "",
"grant_type": ""
}Sample Properties can be used to help you configure the adapter in the Itential Platform. You will need to update connectivity information such as the host, port, protocol and credentials.
"properties": {
"host": "localhost",
"port": 443,
"choosepath": "",
"base_path": "/tmf-api/resourceInventoryManagement",
"version": "v4",
"cache_location": "none",
"encode_pathvars": true,
"encode_queryvars": true,
"save_metric": false,
"stub": true,
"protocol": "https",
"authentication": {
"auth_method": "no_authentication",
"username": "username",
"password": "password",
"token": "token",
"token_timeout": 600000,
"token_cache": "local",
"invalid_token_error": 401,
"auth_field": "header.headers.Authorization",
"auth_field_format": "Basic {b64}{username}:{password}{/b64}",
"auth_logging": false,
"client_id": "",
"client_secret": "",
"grant_type": "",
"auth_request_datatype": "",
"auth_response_datatype": "",
"token_response_placement": "",
"sensitive": [],
"sso": {
"protocol": "",
"host": "",
"port": 0
},
"multiStepAuthCalls": [
{
"name": "",
"requestFields": {},
"responseFields": {},
"successfullResponseCode": 200
}
]
},
"healthcheck": {
"type": "none",
"frequency": 60000,
"query_object": {},
"addlHeaders": {}
},
"throttle": {
"throttle_enabled": false,
"number_pronghorns": 1,
"sync_async": "sync",
"max_in_queue": 1000,
"concurrent_max": 1,
"expire_timeout": 0,
"avg_runtime": 200,
"priorities": [
{
"value": 0,
"percent": 100
}
]
},
"request": {
"number_redirects": 0,
"number_retries": 3,
"limit_retry_error": [
0
],
"failover_codes": [],
"attempt_timeout": 5000,
"global_request": {
"payload": {},
"uriOptions": {},
"addlHeaders": {},
"authData": {}
},
"healthcheck_on_timeout": true,
"return_raw": false,
"archiving": false,
"return_request": false,
"keep_alive_interval": 0
},
"proxy": {
"enabled": false,
"host": "",
"port": 1,
"protocol": "http",
"username": "",
"password": ""
},
"ssl": {
"ecdhCurve": "",
"enabled": false,
"accept_invalid_cert": false,
"ca_file": "",
"ca_file_content": "",
"key_file": "",
"cert_file": "",
"secure_protocol": "",
"ciphers": ""
},
"mongo": {
"url": "",
"host": "",
"port": 0,
"database": "",
"dbAuth": false,
"username": "",
"password": "",
"replSet": "",
"addSrv": false,
"db_ssl": {
"enabled": false,
"accept_invalid_cert": false,
"ca_file": "",
"key_file": "",
"cert_file": ""
}
},
"devicebroker": {
"enabled": false,
"getDevice": [
{
"path": "/not/mapped",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {
"insample": "{port}"
},
"responseDatakey": "",
"responseFields": {
"name": "{this}{||}{that}",
"ostype": "{osfield}",
"ostypePrefix": "meraki-",
"port": "{port}",
"ipaddress": "{ip_addr}",
"serial": "{serial}"
}
}
],
"getDevicesFiltered": [
{
"path": "/not/mapped",
"method": "GET",
"pagination": {
"offsetVar": "",
"limitVar": "",
"incrementBy": "limit",
"requestLocation": "query"
},
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {},
"responseDatakey": "",
"responseFields": {
"name": "{this}{||}{that}",
"ostype": "{osfield}",
"ostypePrefix": "meraki-",
"port": "{port}",
"ipaddress": "{ip_addr}",
"serial": "{serial}",
"id": "{myid}"
}
}
],
"isAlive": [
{
"path": "/not/mapped/{devID}",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {
"devID": "{id}"
},
"responseDatakey": "",
"responseFields": {
"status": "return2xx",
"statusValue": "AD.200"
}
}
],
"getConfig": [
{
"path": "/not/mapped/{devID}",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {
"devID": "{id}"
},
"responseDatakey": "",
"responseFields": {}
}
],
"getCount": [
{
"path": "/not/mapped",
"method": "GET",
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {},
"responseDatakey": "",
"responseFields": {}
}
]
},
"cache": {
"enabled": false,
"entities": [
{
"entityType": "device",
"frequency": 3600,
"flushOnFail": false,
"limit": 10000,
"retryAttempts": 5,
"sort": true,
"populate": [
{
"path": "/not/mapped",
"method": "GET",
"pagination": {
"offsetVar": "",
"limitVar": "",
"incrementBy": "limit",
"requestLocation": "query"
},
"query": {},
"body": {},
"headers": {},
"handleFailure": "ignore",
"requestFields": {},
"responseDatakey": "",
"responseFields": {
"name": "{this}{||}{that}",
"ostype": "{osfield}",
"ostypePrefix": "meraki-",
"port": "{port}",
"ipaddress": "{ip_addr}",
"serial": "{serial}",
"id": "{myid}"
}
}
],
"cachedTasks": [
{
"name": "",
"filterField": "",
"filterLoc": ""
}
]
}
]
}
}