warper2 Outstanding Contributor.
Outstanding Contributor.
436 views

Imanager in a cluster

This not a question how to cluster imanager. I need to know if there is a
way to only have imanager come up on the nodes ip address. I need this since
we are trying to have multiple web servers clustered and we see that all
addresses listen on the server for ports 443 and 80. Is there a way to make
imanager listen only on a certain address. I have googled and searched the
docs with no luck.

Thanks
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Imanager in a cluster

On 3/26/14, 9:37 PM, Rickb wrote:
> This not a question how to cluster imanager. I need to know if there is a
> way to only have imanager come up on the nodes ip address. I need this since
> we are trying to have multiple web servers clustered and we see that all
> addresses listen on the server for ports 443 and 80. Is there a way to make
> imanager listen only on a certain address. I have googled and searched the
> docs with no luck.


Cannot be done, or at least it is not a tested and supported
configuration. The "problem" is that there is no mecanism to handle
updates between different iManager servers - you would have to handle
that manually, and if you use PlugIn Studio then the plugin's will not
get synchronized correctly between the servers.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Imanager in a cluster

On 03/26/2014 02:37 PM, Rickb wrote:
> This not a question how to cluster imanager. I need to know if there is a
> way to only have imanager come up on the nodes ip address. I need this since
> we are trying to have multiple web servers clustered and we see that all
> addresses listen on the server for ports 443 and 80. Is there a way to make
> imanager listen only on a certain address. I have googled and searched the
> docs with no luck.


Works for me the using the typical Apache Tomcat method to restrict the
application server to a single IP address. Just add the following into
the appropriate <Connector/> block within the server.xml file
(./tomcat/conf/server.xml) and restart Tomcat (using your IP of course).

address="192.168.0.1"

For example, my block went from:

Code:
--------------------
<!-- Define a SSL HTTP/1.1 Connector on port -->
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" maxHttpHeaderSize="8192" minSpareThreads="25"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLSv1.2"/>
--------------------

to

Code:
--------------------
<!-- Define a SSL HTTP/1.1 Connector on port -->
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
address="192.168.0.1"
maxThreads="150" maxHttpHeaderSize="8192" minSpareThreads="25"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLSv1.2"/>
--------------------

I did not update the other connector for TCP 8080 so it is still listening
on all addresses, so be sure to get both of yours if desired.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.