Domain Separation Question and Mid server

[CV1]

Hi All,

Please guide me on 

• What all are not domain separated for eg: SQL Data Source and Transform Map . They are not domain separated. what are others like this.
• We have a duplicate mid server that we do not need. How to delete a Mid server.

TIA

[Astik Thombare]

Hi @CV1 ,

Domain Separation in ServiceNow

Domain separation in ServiceNow refers to the practice of isolating different areas of functionality to improve security, performance, and manageability. This means keeping data, workflows, and configurations specific to each domain separate from others.

Examples of domain separation in ServiceNow:

• Data sources: Keeping data sources like SQL servers and Transform Maps separate from the main ServiceNow instance helps protect sensitive information and improve performance.
• Applications: Isolating applications by using plugins or dedicated instances prevents conflicts and improves stability.
• Workflows: Separating workflows for different departments or processes minimizes complexity and reduces the risk of unintended interactions.
• Roles and permissions: Assigning different roles and permissions to different user groups ensures access control and data security.

In your example, SQL Data Source and Transform Maps are not domain-separated because they directly interact with data within the ServiceNow instance. Transform Maps are used to manipulate data retrieved from data sources, potentially exposing sensitive information. Ideally, data sources should be accessed only through specific workflows or integrations, further restricting direct access.

Other examples of areas not domain-separated in ServiceNow (without proper configuration):

• User tables: Sharing user tables between different instances can lead to data inconsistencies and security vulnerabilities.
• Global variables: Exposing global variables across domains can create dependencies and increase complexity.
• Scripts: Uncontrolled scripts can access data and functionality across domains, bypassing security measures.

Deleting a Duplicate Mid Server

To delete a duplicate Mid server in ServiceNow, follow these steps:

1. Stop the Mid Server service:

• Log in to the machine where the Mid Server is installed.
• Open the Services console (e.g., services.msc).
• Locate the MidServer Service.
• Right-click and select Stop.

2. Delete the Mid Server record from ServiceNow:

• Log in to the ServiceNow instance with administrator privileges.
• Navigate to System Administration > MID Servers.
• Select the duplicate Mid Server record.
• Click the Uninstall button.

3. Uninstall the Mid Server software:

• Once the Mid Server record is deleted, you can safely uninstall the software from the machine.
• Follow the instructions provided in the ServiceNow documentation for your specific Mid Server version.

Important notes:

• Before deleting any Mid Server, ensure it is not actively used by any workflows or integrations. Disabling or replacing it with another Mid Server might be necessary.
• Always back up your data before performing any deletion operations.
• Consult the ServiceNow documentation or community resources for specific instructions and troubleshooting tips.

Please mark ✅ Correct if this resolves your issue, and also mark 👍 Helpful if you find my response valuable based on its impact.

Regards,

Astik Thombare

[Astik Thombare]

Hi @CV1 ,

Please mark ✅ Correct if this resolves your issue, and also mark 👍 Helpful if you find my response valuable based on its impact.

Regards,

Astik Thombare