Try OpenEdge Now
skip to main content
Administration
WebSpeed Administration : Configuring WebSpeed on UNIX : WebSpeed configuration overview : Configuring the WebSpeed components on UNIX
 
Configuring the WebSpeed components on UNIX
To configure the WebSpeed components:
1. Start the AdminServer process on each machine by using the PROADSV utility. (See Starting the AdminServer.)
2. Once the AdminServer is running, you can then use OpenEdge Management/OpenEdge Explorer or a text editor to create and modify NameServer and WebSpeed Transaction Server configurations. These configurations are in the properties file (ubroker.properties) on the machine where you installed the WebSpeed Transaction Server. You can also use OpenEdge Management/OpenEdge Explorer, which runs in a Web browser, to access configurations installed on UNIX.
You can also edit the ubroker.properties file manually using a text editor. If you choose to use a text editor, you must have file system access to the file (see Overview of the ubroker.properties file).
Note: You can use the mergeprop utility installed with OpenEdge to manually edit the ubroker.properties file. For information on using mergeprop, see OpenEdge Getting Started: Installation and Configuration.
You can validate NameServer and WebSpeed configurations using the validation utilities, NSCONFIG and WSCONFIG. These utilities must have access to the properties file (see NSCONFIG and WSCONFIG).
3. Determine if you need to set (or change any preset) WebSpeed environment variables (see Setting up the WebSpeed environment).
4. Use the NSMAN utility (or OpenEdge Management/OpenEdge Explorer remotely) to start up a NameServer instance that you configured to coordinate client access to one or more WebSpeed Transaction Server instances on your network. After the NameServer has started, use the WTBMAN utility (or OpenEdge Management/OpenEdge Explorer remotely) to start up each WebSpeed Transaction Server instance controlled by that NameServer (see Starting the WebSpeed Transaction Server and NameServer ).
After a WebSpeed Transaction Server starts up, it registers its location and the Application Services it supports with its controlling NameServer.
5. Set up the WebSpeed Messenger on your Web server (see Setting up WebSpeed on the Web server machine ).
6. At any time after Step 5, you can validate that the AdminServer, the NameServer, and the WebSpeed Transaction Server are running and test the configuration to confirm that you have set up WebSpeed correctly. You perform this validation by using the WebSpeed command-line utilities, OpenEdge Management/OpenEdge Explorer, or the WebSpeed Messenger Administration (WSMAdmin) page in a browser (see Testing your configuration for more information).
7. You can shut down the AdminServer process at any time on the WebSpeed machine. If you shut down the AdminServer while there are NameServer and WebSpeed Transaction Server instances still running, those instances are shut down as well.