Configure multiple network interface card support

Use this task to first prepare your server for multiple network interface card support and enable multiple network interface card logic, including configuring multiple network interface cards to coexist on the same machine.

 

Procedure

1. Configure object request broker (ORB) properties to support multiple network interface cards.

   • Set the com.ibm.CORBA.LocalHost property to resolve to a valid host name or IP address. The value should not resolve to a local host or loop back address (for example, 127.0.0.1).

   1. In the administrative console, click Servers > Application servers > servername > Java and process management > Process Definition > Java Virtual Machine.

   2. Add the following generic JVM argument:

      -Dcom.ibm.CORBA.LocalHost=xxxx.xx.xx.xx -Dcom.ibm.websphere.network.useMultiHome=false -Dcom.ibm.CORBA.ServerSocketQueueDepth=50 -Dcom.ibm.ws.orb.transport.useMultiHome=false
      

2. Update the host name for all HTTP transport chains. In the administrative console, click Servers > Application servers > servername > Web container settings > Web container transport chains. Update the host name for all of the transport chains listed on this page. The value should not resolve to a local host or loop back address (for example, 127.0.0.1).

3. Change the initial state to stopped for each of the listener ports. In the administrative console, click:

   • Servers > Application servers > servername > Messaging > Message listener service > Listener ports > SamplePtoPListenerPort

   • Servers > Application servers > servername > Messaging > Message Listener Service > Listener Ports > SamplePubSubListenerPort

   Update the state to stopped for each port.

4. In a Network Deployment environment, also add the following generic Java virtual machine (JVM) arguments and make sure all nodes are in sync.

   1. In the administrative console, click System administration > Deployment manager > Java and process management > Process definition > Java virtual machine. Add the following generic JVM argument

      -Dcom.ibm.CORBA.LocalHost=xxxx.xx.xx.xx -Dcom.ibm.websphere.network.useMultiHome=false -Dcom.ibm.CORBA.ServerSocketQueueDepth=50 -Dcom.ibm.ws.orb.transport.useMultiHome=false
      

   2. In the administrative console, click System administration > Node agents > node_agent_server > Java and process management > Process definition > Java virtual machine. Add the following generic JVM argument

      -Dcom.ibm.CORBA.LocalHost=xxxx.xx.xx.xx -Dcom.ibm.websphere.network.useMultiHome=false -Dcom.ibm.CORBA.ServerSocketQueueDepth=50 -Dcom.ibm.ws.orb.transport.useMultiHome=false
      

5. Change the initial state of the JMS server to stopped. In the administrative console, click Servers > JMS Servers > JMS_server > Initial state > stopped.

6. Apply these changes to all application servers and the deployment manager.

 

Result

By completing these steps, you enabled multiple network interface card support.

 

Example

1. Install the WAS base product for each network interface card. To install on distributed platforms, see Installing the product and additional software for more information.

2. Start the server that is on the first network interface card. Follow the preceding steps in this task to prepare this server for multiple network interface card support and enable multiple network interface card logic. After you complete this step, stop the server.

3. Start the server that is on the other network interface card. Follow the preceding steps in this task to prepare this server for multiple network interface card support and enable multiple network interface card logic. After you complete this step, stop the server.

4. Start the servers on both network interface cards.

By completing these steps, you enabled multiple application servers to coexist on a single machine that has two network interface cards.

 

---