I've installed 32 bit and 64 bit Progress on the same machine (64bit Win7) and was wondering if someone could walk me through what additional steps I need in order to be able to connect to OE Management for both deployments please?
What kind of errors are you getting (if any)? In theory it should be connecting to the different ports specified during the install but it seems that not all of the issues with 32 bit and 64 bit installed on the same PC are resolved....
knowledgebase.progress.com/.../OpenEdge-11-5-SP1-64-Bit-overwrites-32-Bit-registry
Hi,
With coexistence, the first installed product always uses the default ports. In order to work with both products , you need to configure the ports explicitly.
If you have installed 32bit product first, please start the 64bit admin service on a different port from proenv using the following command. Other way is you can also set the ports in registry entries.
From proenv use this command: proadsv -start -adminport 20934 -port 2544
Once the admin server is started, fathom.properties file will get created under 64bit $DLC\properties.
Append, httpport=9094 (some custom port other than 9090 as it is used by 32 bit OpenEdge Explorer) at the end of the fathom.properties file to make 64-bit OpenEdge Explorer run on a different port. Restart the admin service.
Now the 64-bit OpenEdge Explorer can be used with the url: http://localhost:9094
Now the 32-bit OpenEdge Explorer can be used with the url: http://localhost:9090
Thanks,
Rama
[collapse]I've installed 32 bit and 64 bit Progress on the same machine (64bit Win7) and was wondering if someone could walk me through what additional steps I need in order to be able to connect to OE Management for both deployments please?
Flag this post as spam/abuse.
Hi,
With coexistence, the first installed product always uses the default ports. In order to work with both products , you need to configure the ports explicitly.
If you have installed 32bit product first, please start the 64bit admin service on a different port from proenv using the following command. Other way is you can also set the ports in registry entries.
From proenv use this command: proadsv -start -adminport 20934 -port 2544
Once the admin server is started, fathom.properties file will get created under 64bit $DLC\properties.
Append, httpport=9094 (some custom port other than 9090 as it is used by 32 bit OpenEdge Explorer) at the end of the fathom.properties file to make 64-bit OpenEdge Explorer run on a different port. Restart the admin service.
Now the 64-bit OpenEdge Explorer can be used with the url: http://localhost:9094
Now the 32-bit OpenEdge Explorer can be used with the url: http://localhost:9090
Thanks,
Rama
I've installed 32 bit and 64 bit Progress on the same machine (64bit Win7) and was wondering if someone could walk me through what additional steps I need in order to be able to connect to OE Management for both deployments please?
Flag this post as spam/abuse.
Flag this post as spam/abuse.
apart from the question why would you want to have 2 OEM of same version on the same machine, you also need to change the 4444 polling port - that can only be changed in OEM - options while the OEM is running, so make sure you do it in one version before you go and start both of them
Interesting, is it (now) fully supported to have 32bit and 64 bit on the same windows server?
I think a connect between 32bit client to 64bit server isn't possible (shared memory), only through ports (-S)
Interesting, is it (now) fully supported to have 32bit and 64 bit on the same windows server?
I think a connect between 32bit client to 64bit server isn't possible (shared memory), only through ports (-S)
Flag this post as spam/abuse.
Correct - 32bit client can only connect client/server to a 64bit served DB and vice versa.
In terms of OEM I only really need the 64bit version running so I've uninstalled and reinstalling, 64bit first, rather than faffing about.
Is there any existing, if not, suggest that to have a -port-offset n configuration (similar to JBoss - https://docs.jboss.org/author/display/WFLY9/Domain+Setup) which will automates the increasing/decreasing of the binding port(s) based on the n value?
Example:
-port-offset=100
As such, all the default ports (-adminport, -port, -httpport, etc) will be increased by 100. This way will be much easier to setup for different OE environments.
Is there any existing, if not, suggest that to have a -port-offset n configuration (similar to JBoss - https://docs.jboss.org/author/display/WFLY9/Domain+Setup) which will automates the increasing/decreasing of the binding port(s) based on the n value?
Example:
-port-offset=100
As such, all the default ports (-adminport, -port, -httpport, etc) will be increased by 100. This way will be much easier to setup for different OE environments.
Flag this post as spam/abuse.
[quote user="Peter Judge"]
[/quote]