Setting up TCP/IP for standalone operationsIf your system is not connected to a network, you must set up WebSphere Application Server for standalone operations. To set up your system for standalone operations, you must have TCP/IP networking installed. If you will run WebSphere Application Server as a standalone (not connected to a network), your host name must remain fixed. WebSphere Application Server is a "networked" system that can be clustered into a single domain, with the administration and other aspects rely upon the IP networking. When the product starts for the first time, it records the host name. When it restarts, it needs to be able to contact that IP address again. If you wish to use WebSphere Application Server "disconnected", you must still always be able to "ping" your host name successfully. If you need to set up a fixed IP address, for Windows NT, go to the Network section of the Control Panel, in the Adapters tab, and install the MS Loopback Adapter. Then, go to the Protocols tab, open TCP/IP properties, and specify a fixed TCP/IP address of 10.0.0.1 (which is an address reserved for private use and thus appropriate for standalone operations), and a subnet mask of 255.255.255.0. ![]() No default gateway for this adapter is specified. Go to the Bindings tab, select all protocols, expand TCP/IP Protocol, and then move the MS Loopback Adapter to the top of the TCP/IP Protocol list. ![]() Save the changes and reboot. After rebooting, you should be able to ping your host name whether or not you are connected to a network. To test your new TCP/IP setup, ping your host name while running standalone and, optionally, while connected to a network. |
|