Netcool Impact Notes

Subject Description
How To Disable the password authentication to the impact operator view Click Here

This document applies only to the following language version(s):

English
Question

How can disable the password authentication to the operator view?
Answer

To disable the password you need to do the following:

1. From $NCHOME/guiserver/install/stage/opview/WEB-INF/vi web.xml comment out following tags and inner content:

FROM:

</security-constraint>
<web-resource-collection>
<web-resource-name>NCI Client Protected Area</web-resource-name>
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>

<auth-constraint>
<role-name>NETCOOL_ADMIN</role-name>
<role-name>OPVIEW_USER</role-name>
<role-name>IMPACT_USER</role-name>
</auth-constraint>
</security-constraint>

TO:

<!--
</security-constraint>
<web-resource-collection>
<web-resource-name>NCI Client Protected Area</web-resource-name>
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>

<auth-constraint>
<role-name>NETCOOL_ADMIN</role-name>
<role-name>OPVIEW_USER</role-name>
<role-name>IMPACT_USER</role-name>
</auth-constraint>
</security-constraint>
-->

2. While the server is running regenerate and redeploy the guiserver ear by running the following command:
$NCHOME/guiserver/install/ncgui_createear
How To Recover Lost Impact Policies replace policy.lst file in $IMPACT_HOME/policy. Stop all impact servers in the cluster. start primary impact server then the others.
Clustering How To  

Steps to Do the Impact Clustering:

Step1:  Install Netcool Impact, guiserver, nameserver on both Primary and Secondary server with default Port configuration.

Step2:  Configure the primary GUI Server.

Add or update the following lines in the $NCHOME/guiserver/etc/

nameserver.props file:

nameserver.1.host=secondary.com

nameserver.1.port=9080

nameserver.1.location=/nameserver/services

nameserver.count=2

The nameserver.count property sets the number of Name Servers in the cluster

to 2.

Now the file should look like this:

nameserver.count=2

nameserver.0.host=primary.com

nameserver.0.port=9080

nameserver.0.location=/nameserver/services

nameserver.1.host=secondary.com

nameserver.1.port=9080

nameserver.1.location=/nameserver/services

Step3:  Add or update the following lines in the $NCHOME/impact/etc/nameserver.props

file:

impact.nameserver.1.host=secondary.com

impact.nameserver.1.port=9080

impact.nameserver.1.location=/nameserver/services

impact.nameserver.count=2

The nameserver.count property sets the number of Impact Servers in the cluster

to 2.

For more information on these properties see “Connection properties between

the Name Server and the Impact Server” on page 49. So the file should look

like this:

impact.nameserver.count=2

impact.nameserver.0.host=primary.com

impact.nameserver.0.port=9080

impact.nameserver.0.location=/nameserver/services

impact.nameserver.1.host=secondary.com

impact.nameserver.1.port=9080

impact.nameserver.1.location=/nameserver/services

Step4:  Configure the primary Name Server.

Edit the $NCHOME/guiserver/install/stage/nameserver/WEB-INF/web.xml file.

After the changes, the file should look like this:

<context-param>

<param-name>REPLICANT.COUNT</param-name>

<param-value>2</param-value>

</context-param>

<context-param>

<param-name>REPLICANT.0.HOST</param-name>

<param-value>primary.com</param-value>

</context-param>

<context-param>

<param-name>REPLICANT.0.PORT</param-name>

<param-value>9080</param-value>

</context-param>

<context-param>

<param-name>REPLICANT.0.LOCATION</param-name>

<param-value>/nameserver/services</param-value>

</context-param>

<context-param>

<param-name>REPLICANT.1.HOST</param-name>

<param-value>secondary.com</param-value>

</context-param>

<context-param>

<param-name>REPLICANT.1.PORT</param-name>

<param-value>9080</param-value>

</context-param>

<context-param>

<param-name>REPLICANT.1.LOCATION</param-name>

<param-value>/nameserver/services</param-value>

</context-param>

<context-param>

<param-name>SELFINDEX</param-name>

<param-value>0</param-value>

</context-param>

Note: The value of the SELFINDEX property is 0 because this property file is

associated with the first Name Server instance in the cluster. For the second

Name Server, you must set this property to 1. For a third Name Server, you

would set this property to 2.

Step5:  Configure the secondary GUI Server.

Add or update the following lines in the $NCHOME/guiserver/etc/

nameserver.props file:

nameserver.1.host=secondary.com

nameserver.1.port=9080

nameserver.1.location=/nameserver/services

nameserver.count=2

The nameserver.count property sets the number of Name Servers in the cluster

to 2.

Now the file should look like this:

nameserver.count=2

nameserver.0.host=primary.com

nameserver.0.port=9080

nameserver.0.location=/nameserver/services

nameserver.1.host=secondary.com

nameserver.1.port=9080

nameserver.1.location=/nameserver/services

Step6:  Configure the secondary Impact Server.

Add or update the following lines in the $NCHOME/impact/etc/nameserver.props

file:

impact.nameserver.1.host=secondary.com

impact.nameserver.1.port=9080

impact.nameserver.1.location=/nameserver/services

impact.nameserver.count=2

The nameserver.count property sets the number of Impact Servers in the cluster

to 2.

Note: The file should be the same as the nameserver.props file of the primary.

Step7: Configure the secondary Name Server.

Edit the $NCHOME/guiserver/install/stage/nameserver/WEB-INF/web.xml file.

The file should be the same as in the primary Name Server except for the

SELFINDEX part which for the secondary will have the value of 1, like in the

following example:

<context-param>

<param-name>SELFINDEX</param-name>

<param-value>1</param-value>

</context-param>

 

Step8: Edit $NCHOME/impact/etc/<servername>_server.props

- Add the property:
impact.server.ipadress=<ipaddress>
where <ipaddress> is the IP address that Impact should be using locally to connect to the nameserver
please make sure there are no trailing or leading spaces

Note: Ipadress should be the “Management Ip Adress Value”.

Step9: Redeploy the “GuiServer” instance using the below command on both the server(Primary as well as Secondary)

/opt/ibm/tivoli/netcool/guiserver/install/ncgui_createear

Step10: Restart the Impact server running the below command on both the server(Primary as well as Secondary)

/etc/init.d/nci restart

 

Note: Please make sure 9080 port needs to be open between two servers.


Email me here simon@simonsaysbiz.com

Note: Please fill out the fields marked with an asterisk.