I'm not 100% sure what your goal is but I'll offer this.
We have 2 different Windows machines with EM running. On the development machine I found C:\SAS\Config\Lev1\Web\WebServer\htdocs\sas\sas-environment.xml.
I made a backup copy of the file before modified it.
I copied the default <environment> section and pasted it below the original.
I changed the first <environment> to name="Dev" and <desc> to Development SAS Environment.
In the new/copied <environment> I changed name="Prod", <desc> to Production SAS Environment and pointed the <service-registry> to our production machine.
When I logged in to EM on my development machine it gave me a choice of environments.
In the following environments.xml I redacted MACHINENAME1 and MACHINENAME2:
<?xml version="1.0" encoding="UTF-8"?>
<environments xmlns="http://www.sas.com/xml/schema/sas-environments-9.4"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://www.sas.com/xml/schema/sas-environments-9.4
http://www.sas.com/xml/schema/sas-environments-9.4/sas-environments-9.4.xsd"
version="2.0">
<environment name="DEV" default="true" platform-version="9.4">
<desc>Development SAS Environment</desc>
<service-registry>
http://MACHINENAME1:80/SASWIPClientAccess/remote/ServiceRegistry
</service-registry>
<service-registry interface-type="soap">
http://MACHINENAME1:80/SASWIPSoapServices/services/ServiceRegistry
</service-registry>
<service-registry interface-type="rest">http://MACHINENAME1:80/SASWIPClientAccess/rest/</service-registry>
</environment>
<environment name="PROD" default="false" platform-version="9.4">
<desc>Production SAS Environment</desc>
<service-registry>
http://MACHINENAME2:80/SASWIPClientAccess/remote/ServiceRegistry
</service-registry>
<service-registry interface-type="soap">
http://MACHINENAME2:80/SASWIPSoapServices/services/ServiceRegistry
</service-registry>
<service-registry interface-type="rest">http:MACHINENAME2:80/SASWIPClientAccess/rest/</service-registry>
</environment>
</environments>
I hope this helps.
