Previous Topic: ReportCenter Communication and Connections

Next Topic: Customize the ReportCenter Control Region


ReportCenter and the Sockets Interface

Report Center requires that the region's TCP/IP sockets interface is active. This is set in the $NM SOCKETS Customizer parameter group (/PARMS). This parameter group should have been completed and actioned as part of the region implementation.

ReportCenter uses TCP/IP socket connections between the NM RC Control Region and the Java Task to establish connections for transferring information. If there is no connection through TCP/IP, error messages appear in the NetMaster Activity Log, and the Java Task may appear not to be working, or may actually stop.

Use the OCS SELFTEST command to check the sockets interface.

Coexistence with TCP/IP Version 6

CA NetMaster NM for TCP/IP monitors IPv6 network activity, sends IPv6 performance data to ReportCenter, and uses an IPv6 network to perform management functions when necessary. Some internal functions in CA NetMaster NM for TCP/IP, such as the socket connection between the ReportCenter Java Task and ReportCenter regions, continue to use IPv4.