Progress/400
Product Guide
Task List
Follow these steps on the AS/400 to use the Progress/400 AppServer product:
- Install the Progress/400 AppServer product on your machine.
- Optionally, modify the NameServer and Progress/400 AppServer instance configurations in the
ubroker.properties
located in $DLC/properties using EDTF.- Add the Progress library to your library list.
- Start the AdminServer using the Progress/400 command STRADMSVR. Any Auto-start servers (Name or AppServer) will also start at this time.
Use the WRKACTJOB command to make sure the ADMINSERV starts under the user you specified. Look at other jobs in the subsystem and wait for their status to stabilize. New jobs will appear and disappear for a few minutes.
Follow these steps on an NT client machine once you have started the AdminServer on the AS/400:
- Ensure that you have the Progress Explorer installed and running on your NT machine.
- Choose start
Programs
Progress
Progress Explorer from your Windows Taskbar.
The Progress Explorer main window appears. When you expand the tree view under Progress MMC Explorer, you see a list of machines where you can start a Progress server. In this example, only the local host machine is listed:
![]()
To add your remote AS/400 to the list, do the following:
- Select Progress MMC Explorer from the tree view.
- Choose Action
Add Progress Server from the main menu.
- Enter the server name (the name of a remote machine), your user name, and your password in the Server Properties dialog box.
- Select Save username and password if you want to automatically log into this machine every time you connect to it.
- Select the Advanced tab and make sure that the Server Port Number matches the Default AdminServer Port Number specified during the Installation or when using the CHGPRODFT command.
- Select Reconnect at startup only if you want to automatically connect to this machine every time you start Progress Explorer.
- Choose OK.
- Select the name of the machine where your AdminServer is running.
You will see a login dialog box, unless you configured the Progress Explorer tool to automatically log in to a particular machine.
- Choose Action
Connect from the main menu.
- Expand the tree view of the connected server machine. The expanded tree view will look similar to the following:
![]()
You can now manage the Progress/400 AppServer as you would any other AppServer. You can end all AppServers and Name Servers from your client using the Progress Explorer tool or using the respective command-line utilities ASBMAN and NSMAN.
You can shut down an AdminServer process at any time from the AS/400. If you do shut down an AdminServer process, all other jobs managed by this AdminServer end as well. To shut down the AdminServer, use the Progress/400 ENDADMSVR command with the appropriate user profile and password.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |