Administration guide > Tune and performance

Operational checklist

AIX operating system settings

1. TCP_KEEPINTVL

   The TCP_KEEPINTVL setting is part of a socket keep-alive protocol that enables detection of network outage. The property specifies the interval between packets that are sent to validate the connection. When you are using WebSphere eXtreme Scale, set the value to 10.

   To check the current setting...

   # no -o tcp_keepintvl

   To change the current setting...

   # no -o tcp_keepintvl=10

   The TCP_KEEPINTVL setting is in half seconds.

2. TCP_KEEPINIT

   The TCP_KEEPINIT setting is part of a socket keep-alive protocol that enables detection of network outage. The property specifies the initial timeout value for TCP connection. When you are using WebSphere eXtreme Scale, set the value to 40.

   To check the current setting...

   # no -o tcp_keepinit

   To change the current setting...

   # no -o tcp_keepinit=40

   The TCP_KEEPINIT setting is in half seconds.

Transport behavior

To modify the transport behavior of the grid, edit...

java/jre/lib/orb.properties

startOgServer

Use parameters in the startOgServer script. In particular, use the following parameters:

• Set heap settings with the -jvmArgs parameter.
• Set application class path and properties with the -jvmArgs parameter.
• Set -jvmArgs parameters for configuring agent monitoring.

Port settings

WebSphere eXtreme Scale has to open ports for communications for some transports. These ports are all dynamically defined. However, if a firewall is in use between containers then specify the ports. Use the following information about the ports:

• Listener port

  Use the -listenerPort argument to specify the port that is used for communication between processes.

• Core group port

  Use the -haManagerPort argument to specify the port that is used for failure detection. This argument is the same as peerPort. Note that core groups do not need to communicate across zones, so you might not need to set this port if the firewall is open to all the members of a single zone.

• JMX service port

  Use the -JMXServicePort argument to specify the port that the JMX service should use.

• SSL port

  To set the SSL port to 1234 pass...'

  -Dcom.ibm.CSI.SSLPort=1234

  ...as a -jvmArgs argument. The SSL port is the secure port peer to the listener port.

• Client port

  Used in the catalog service only. You can specify this value with the -catalogServiceEndPoints argument. The format of the value of this parameter is in the format:

  serverName:hostName:clientPort:peerPort

Security settings

Verify that security settings are configured correctly:

• Transport (SSL)
• Application (Authentication and Authorization)

To verify the security settings, you can try to use a malicious client to connect to the configuration. For example, when the SSL-Required setting is configured, a client that has a TCP_IP setting with or a client with the wrong trust store should not be able to connect to the server. When authentication is required, a client with no credential, such as a user ID and password, should not be able to connect to the sever. When authorization is enforced, a client with no access authorization should not be granted the access to the server resources.

Monitor the environment

Options

• xsAdmin tool:

  • The JMX ports of the catalog servers need to be visible to the xsAdmin tool. The container server ports also need to be accessible for some commands that gather information from the containers.

• Monitoring console:

  With the monitoring console, you can chart current and historical statistics.

• Vendor monitoring tools:
  • Tivoli Enterprise Monitoring Agent
  • CA Wily Introscope
  • Hyperic HQ

See...

• Monitor with the xsAdmin sample utility
• Java Management Extensions (JMX) security
• Monitor with the web console
• Monitor with the IBM Tivoli Enterprise Monitoring Agent for WebSphere eXtreme Scale
• Monitor eXtreme Scale with Hyperic HQ
• Monitor eXtreme Scale applications with CA Wily Introscope

Parent topic:

Plan the WebSphere eXtreme Scale environment

Parent topic:

Tune and performance

Related concepts

Plan overview
Hardware and software requirements
JEE considerations
Cache topology: In-memory and distributed caching
Catalog service
Container servers, partitions, and shards
Capacity planning
Operating systems and network tuning
Plan for network ports
ORB properties and file descriptor settings
JVM tuning for WebSphere eXtreme Scale
Use WebSphere Real Time

Related tasks

Configure failover detection
Tune the dynamic cache provider
Tune the cache sizing agent for accurate memory consumption estimates

Related reference

Directory conventions

+

Search Tips   |   Advanced Search