Remote clients can identify the server they are talking to if the server can be distinguished using a unique ID. TDI allows you to specify unique server IDs that allow remote clients, such as the Administration and Monitoring Console (AMC), to connect to different TDI servers at different times using the same IP and port. In order to connect using the same ID and port but at different times, TDI client applications must be able to register these client applications as different TDI servers that we can associate with different data and databases.
Users are to assign the unique IDs manually, ensuring that any remote client (such as AMC) can connect to a TDI server based on the IP address, the port, and the unique ID of the TDI server. AMC registers every server with a unique ID, so that a TDI server cannot be registered more than once by mistake or intentionally. When assigning IDs manually, users must ensure that different TDI servers have distinguishable IDs.
We can configure the unique server ID property using com.ibm.di.server.id. To give a server a unique server id for a given server, provide a unique ID string for this property in the global.properties or solution.properties file on the server you are identifying. The default value for com.ibm.di.server.id is blank.