--- schema_version: "1" id: a6765c7e2fc0be2e7eb40be4232cf13f4e97454a3b892f88d25e4582ac914161 title: DevOps Process Job collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_discovery_process_devops.md canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_discovery_process_devops.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 98d5aacd04957440863dc1d20be49d9d1fbfb2c13d53e6def84c8669569d8a15 description: Understand dependencies across web, application, database, virtualization, cluster, and load-balancer layers. The DevOps process job creates relationships from configuration data collected during discovery. products: - Service Cloud - Agentforce IT Service release: "264" --- # DevOps Process Job Understand dependencies across web, application, database, virtualization, cluster, and load-balancer layers. The DevOps process job creates relationships from configuration data collected during discovery. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service that have Discovery enabled.
## How DevOps Dependencies Are Mapped The DevOps process job connects middleware, databases, virtualization platforms, clusters, and load balancers. It can also create Oracle Cluster, Windows Cluster, and Windows Cluster Node configuration items (CIs) from cluster information collected during discovery. ## When to Run the Job Run the job after discovery has collected the underlying servers, software, and services. Rerun it regularly to keep middleware and database dependency views current. To start the job, see [Run a Process Job](https://help.salesforce.com/s/articleView?id=service.it_srvcs_discovery_run_prcsjob.htm&release=264.0.0&type=5 "Build dependency-aware views of your discovered infrastructure by running a process job. Select the job that maps the application, cloud, network, software, or virtualization relationships that you want to analyze in Configuration Management Database (CMDB)."). ## IIS Relationships | Source and Target | Relationship | What It Means | How It’s Matched | | --- | --- | --- | --- | | IIS Website to IIS Web Application | Deployed On | An application is deployed under an IIS website. | The host IP addresses match, and the application name starts with the website name. | | IIS Website to Windows Server | Load Balances | A Windows Server load-balancing configuration includes the website. | A load-balancer node IP address in the Windows Server configuration matches the website IP address. | | IIS Host Connection to Destination CI | Configured per Port | A network connection from an IIS host uses the relationship configured for the remote port. | The connection remote port matches a port relationship rule. The listening side determines the relationship direction. | ## Web and Application Server Relationships | Source and Target | Relationship | What It Means | How It’s Matched | | --- | --- | --- | --- | | Website to IPv4 Address | Hosted On | A website resolves to an IP address. | The website address matches the IPv4 Address CI. | | Apache, Tomcat, or JBoss to Application | Hosted On | A web or application server hosts an application. | The server and application share the same IP address and name. | | Tomcat Server to Tomcat Web Application | Hosted On | A Tomcat server hosts a Tomcat web application. | Apache and Tomcat worker configuration identifies the application and the server that hosts it. | | Apache to Tomcat | Load Balancer For | Apache is configured as a load balancer for Tomcat. | The Apache and Tomcat worker configuration identifies a worker as a load balancer. | ## Database Relationships | Source and Target | Relationship | What It Means | How It’s Matched | | --- | --- | --- | --- | | MySQL Instance to Apache or Tomcat | Reads Data From | A web or application server connects to a MySQL instance. | Discovered network connections match the server to the MySQL instance IP address. | | Application to MySQL or Database | Read Data From or Write Data Into | An application reads from or writes to a database. | The application database configuration identifies the database host and access type. | | Microsoft SQL Instance to Windows Server | Runs | A SQL instance runs on a Windows server. | The SQL instance IP address matches the Windows server. | | Microsoft SQL Instance to Microsoft SQL Server Software | Instantiates | A running SQL instance uses Microsoft SQL Server software. | The instance ports match the software listening ports. | | Oracle Database to Oracle Cluster | Cluster Of | An Oracle database is a node in an Oracle Real Application Clusters environment. | Discovered cluster information identifies each node host name and its Oracle database. | | Oracle Cluster to Master Node | Hosts | An Oracle cluster hosts its master node. | Discovered cluster information identifies the master node and virtual IP address. | ## Virtualization, Cluster, and Load-Balancer Relationships | Source and Target | Relationship | What It Means | How It’s Matched | | --- | --- | --- | --- | | Windows Cluster Node to Windows Cluster | Cluster Of | A node belongs to a Windows cluster. | Discovered cluster information identifies the cluster by IP address and its nodes by name. | | Windows Server to Windows Cluster Node | Hosted On | A Windows server hosts a cluster node. | The node IP address matches the Windows server. | | Windows Host or Server to Hyper-V | Virtualizes | A Windows host or server provides Hyper-V virtualization. | The host IP address matches the Hyper-V record. | | Cisco UCS to Cisco UCS Chassis | Contains | A Cisco Unified Computing System contains a chassis. | The discovered Cisco UCS components identify their parent-child structure. | | Cisco UCS Chassis to Cisco Blade Server | Contains | A Cisco UCS chassis contains a blade server. | The discovered Cisco UCS components identify their parent-child structure. | The job also matches NetScaler and F5 nodes to discovered hosts by IP address and records the host asset ID on each matching node.