The GroupWise client can be distributed through a system called SETUPIP. SETUPIP requires a client and a server/host. The SETUPIP Client is called SETUPIP.EXE. The SETUPIP Host is a web server that serves up a compressed GroupWise install set called a SETUPIP Client Distribution Set. The advantage to distributing the GroupWise client via the SETUPIP method is that users do not need to have file-system rights to a server to install the GroupWise client. This section explains all the aspects of creating a SETUPIP GroupWise Client Distribution System. SETUPIP Host configuration instructions given in this chapter are specific to Apache on NetWare 6.5 and Apache on SUSE Linux Enterprise Server 9. However, you can model the instructions given in this chapter to try to implement a SETUPIP Host on other flavors of web servers. Note You must have a web server of some sort. The web server must allow connections on port 80, the standard HTTP port. Creating the SETUPIP.EXE Client UtilityThe SETUPIP.EXE Client utility is a file that you actually generate. Here are the steps you must complete to create the SETUPIP.EXE Client utility:
Although the SETUPIP utility is created, and can be executed, it will error out if you run it, because you must implement the rest of the SETUPIP GroupWise Client Distribution System. Configuring the SETUPIP Host Web ServerThe SETUPIP Client expects a SETUPIP Client Distribution Set, which is a handful of files and a directory path that should be present and served up at the HTTP location you specified in the WRITEIP utility. The directory path should be under the web server's "document root" folder. The name of the directory path you create should correlate to the name of the directory path you indicated earlier in the WRITEIP utility. So in our example, the directory path should be a directory called gw7cl, under the web server's document root directory. So, for example, on a typical NetWare 6.5 server, you would create the gw7cl directory off of SYS:APACHE2\HTDOCS. After the directory path is created, there are specific files you will want to put in place. Right now, though, is a good time to make this discussion more specific to the version of web server you are using. We'll first review the steps to creating the SETUPIP Host on the NetWare 6.5 platform. And then we'll explain the exact same steps relative to Apache on a SUSE Linux Enterprise Server 9 server. The methods we employ for these web servers should be sufficient for you to implement a SETUPIP Host on whatever web server platform you happen to have. Configuring the SETUPIP Host Web Server on NetWare 6.5The SETUPIP Host web server generally does not need any specific "configuration"; it's all about creating the directories and placing the files that will make a correctly configured SETUPIP Client Distribution Set. Your Apache web server, though, should allow for connections on the standard HTTP port, which is port 80. In our sample scenario, we will use each of the steps indicated on the servers that host the DNS names: wwwfs1.wwwidgets.com and wwwfs2.wwwidgets.com. The reason for this is that when we ran the WRITEIP utility earlier, we indicated that both of these servers were going to be available to serve SETUPIP Client requests:
Now that you have both the SETUPIP Client and the SETUPIP Host configured, you have a complete SETUPIP GroupWise Client Distribution System. The ..\GW7CL directory should look similar to what's shown in Figure 12.6. Figure 12.6. The contents of the GW7CL directoryThe ..\GW7CL\WIN32 directory should look similar to what's shown in Figure 12.7. Figure 12.7. The contents of the GW7CL\WIN32 directoryNow you need to test your SETUPIP System, and perfect it if needed. To test it, simply run the SETUPIP Client utility you created earlier. It's called SETUPIP.EXE, and by default it's located in the GroupWise 7 SDD\ADMIN\UTILITY\SETUPIP directory. When you run SETUPIP.EXE, you should see a dialog similar to the one shown in Figure 12.8. After SETUPIP.EXE downloads and extracts the GroupWise Client, the regular GroupWise Client SETUP.EXE runs. Figure 12.8. The SETUPIP Client utility SETUPIP.EXE downloading the GroupWise client
If you run into problems getting SETUPIP to work, make sure that the Apache web server is running. You may also want to confirm that the Apache web server is listening on port 80. The command to load Apache on a NetWare 6.5 server is as follows: apache2 To further troubleshoot and configure your Apache web server on NetWare 6.5, you may need to stray into the configuration file for Apache. Typically the configuration file is SYS:APACHE2\CONF\HTTPD.CONF. Also, note that case sensitivity is important to Apache, so be sure to keep the filename lowercasefor example, httpd.conf. The common writing convention in this book shows filenames in uppercase, so we refer to files in uppercase format. Generally on NetWare the case of a file does not matter, but to Apache it does. Configuring the SETUPIP Host Web Server on SLES9 ServerThe SETUPIP Host web server generally does not need any specific "configuration"; it's all about creating the directories and placing the files that will make a correctly configured SETUPIP Client Distribution Set. Your Apache web server, though, should allow for connections on the standard HTTP port, which is port 80. In our sample scenario, we will use each of the steps indicated on the servers that host the DNS names: wwwfs1.wwwidgets.com and wwwfs2.wwwidgets.com. The reason for this is that when we ran the WRITEIP utility earlier, we indicated that both of these servers were going to be available to serve SETUPIP Client requests:
Now that you have both the SETUPIP Client and the SETUPIP Host configured, you have a complete SETUPIP GroupWise Client Distribution System. The ../gw7cl directory and contents under the directory should look similar to what's shown in Figure 12.9. Figure 12.9. The contents of the gw7cl directory and subdirectories on a SLES9 Server
Now you need to test your SETUPIP System, and perfect it if needed. To test it, simply run the SETUPIP Client utility you created earlier. It's called SETUPIP.EXE, and by default it's located in the GroupWise 7 SDD\ADMIN\UTILITY\SETUPIP directory. When you run the SETUPIP.EXE, you should see a dialog similar to the one shown in Figure 12.10. After SETUPIP.EXE downloads and extracts the GroupWise Client, the regular GroupWise Client SETUP.EXE runs. Figure 12.10. The SETUPIP Client utility SETUPIP.EXE downloading the GroupWise client
If you run into problems getting SETUPIP to work, make sure that the Apache web server is running. You may also want to confirm that the Apache web server is listening on port 80. The command to load Apache on our SLES9 server is as follows: /etc/opt/novell/httpd/init.d/httpd start The command to start Apache on your Linux server could very well be different. To further troubleshoot and configure your Apache web server on Linux, you may need to stray into the configuration file for Apache. The *.conf file on our SLES9 server is /etc/opt/novell/httpd/conf.d. Also, note that case sensitivity is important to Apache, so be sure to keep the filename lowercase. The Apache error log file is also a good place to go for troubleshooting purposes. On our SLES9 server the error log was located at /var/opt/novell/httpd/logs/error_log. When writing this chapter, we used the Apache error_log to determine that the SETUPIP Client was trying to find the SETUPIP.* files with a particular case. So using the error_log file for troubleshooting is really handy. Troubleshooting SETUPIPThe SETUIP Client utility creates an error log called SETUPIP.ERR if SETUPIP.EXE encounters an error condition. This file is created in the Windows root program folder, such as C:\WINNT. Here is an example of the contents of our SETUPIP.ERR file in our test system: 137.65.55.215 - The file SetupIP.US was not found. (200) Another good place to go for troubleshooting purposes is the error log of the web server. For example, the Apache error log file is also a good place to go for troubleshooting purposes for the Apache web server. |