Installing GroupWise WebAccess 7 on OES Linux Server
Novell Cool Solutions: AppNote
By Dave Simons
Digg This -
Posted: 12 Dec 2006
In this AppNote I will explain how to install GroupWise WebAccess on a OES Linux Server. Before you can install GroupWise Webaccess, you must have an fully operational GroupWise system. For instructions on installing a GroupWise system on OES Linux, see the AppNote I wrote earlier.
Before you install GroupWise WebAccess, note that the best configuration is to install the WebAccess agent on a server that also holds a GroupWise domain locally. This is because the WebAccess agent must have a connection with the wpdomain.db file. If the connection is lost, users cannot log in to the WebAccess application. When you install the WebAccess Agent on a server that does not hold an Domain, this Agent must connect to a domain over the LAN. When the LAN connection is down, users are not able to log in.
Just like in Netware, in the OES Linux world you also have a GroupWise Agent and a GroupWise Application that together make GroupWise WebAccess possible. The WebAccess Agent is a kind of translator for the WebAccess Application; all the data that goes in or out the Domain is translated by the WebAccess Agent.
Now it's time to install the software ...
1. Insert the GroupWise media CD and browse to the root of the CD.
2. Click Install.
3. Click OK to accept the Default language.
Figure 1 - Setting the default language
4. In the next screen, click Install Products.
Figure 2 - Install Products screen
5. Click Install GroupWise WebAccess.
Figure 3 - GroupWise WebAccess option
6. Click Install WebAccess Agent.
Figure 4 - WebAccess Agent option
7. When the Installation Complete screen appears, click OK.
Figure 5 - Installation Complete
8. Click Configure WebAccess Agent.
Figure 6 - Configure WebAccess Agent option
9. In the WebAccess configuration screen, click Next to start the configuration.
Figure 7 - Introduction to configuration
The license screen then appears.
10. If you agree to the license, mark the the first checkbox and click Next.
Figure 8 - Accepting the license agreement
11. Enter the IP address of the server that runs the WebAccess Agent. In my lab, this is 192.168.1.10. Leave the port as it is.
Figure 9 - IP address for WebAccess Agent
12. Click Next.
13. Enter the path to the GroupWise Domain. This is the path where the WebAccess Agent will save the configuration files. You can change the Default WebAccess directory name if you like; I always leave it as the default.
Figure 10 - Path to GroupWise Domain
14. Click Next.
15. Because GroupWise WebAccess relies on LDAP, you must enter the IP address of your LDAP server (in my case, this is 192.168.1.10).
16. Enter the admin user password. I don't configure SSL connection, because I only use WebAccess from within my LAN.
Figure 11 - IP address for LDAP server
17. Click Next to continue.
18. Enter the path to the GroupWise Domain you created earlier. In my case, this is cn=dom1,ou=groupwise,o=disney. Remember that is should be entered in LDAP format.
Figure 12 - Path to GroupWise domain
19. Click Next.
When the configuration of the Agent is almost ready, you will see this screen:
Figure 13 - Configuration Complete screen
20. To start the agent when the system starts, click Exit to save and enable the configuration.
Now it's time to install and configure the GroupWise WebAccess Application.
Installing and Configuring GroupWise WebAccess
1. In the main menu, select Install WebAccess Application.
Figure 14 - Install WebAccess Application option
2. When the Installation Complete screen appears, click OK.
Figure 15 - Installation Complete screen
3. From the main menu, select Configure WebAccess Application.
Figure 16 - Configure WebAccess Application option
4. In the WebAccess Application configuration screen, click Next to start the configuration.
Figure 17 - Introduction to WebAccess Application configuration
5. Accept the license agreement and click Next.
Figure 18 - Accepting the license agreement
6. Enter the path to the WebAccess Agent directory. This is the directory the agent automatically makes when you install it. In my case it is:
Figure 19 - Path to the WebAccess Agent directory
7. Click Next.
8. Enter the path to the webserver and Tomcat root directory. The directories shown are the defaults - they work for an OES Linux server that's been installed as the default.
9. Click Next to accept the settings if they are OK.
Figure 20 - Web Server information settings
10. Just as with the Agent, enter the IP address of the LDAP server and the admin user password.
Figure 21 - IP address of the LDAP server
11. Click Next to go on.
12. Enter the context of the domain object.
Figure 22 - Domain object context
This is the context where the WebAccess Application objects will be stored. You can use these objects to configure the GroupWise WebAccess Application.
13. Click Next.
14. In the final screen, click Exit to save and apply the configuration.
Figure 23 - Saving the configuration
Now you have installed GroupWise WebAcces and you're ready to start it.
Starting and Testing GroupWise WebAccess
1. Log in to a terminal window, then log in as user root.
2. Change to the /etc/init.d directory and enter "./grpwise status".
Figure 24 - x
The screen indicates that the GroupWise system is down.
3. To start the GroupWise system, enter "./grpwise start".
Figure 25 - Starting GroupWise
You'll see that the Domain, the Postoffice, the WebAccess Agent, and the WebAccess Application are all starting up. Now that everything is running its time to test GroupWise WebAccess.
4. Open a browser and enter this URL:
The login page appears.
Figure 26 - GroupWise login page
I use the IP address in the URL field, but you can also enter the DNS name of the server.
5. Log in with a valid username/password, and you are ready to work with your mailbox.
Figure 27 - x
Just as with Netware, there is also an option here to show the Agent screen. Normally on OES Linux the GroupWise Agent runs in the Background, but sometimes it can be useful to let the Agent show you what is happening with your system.
To see the WebAccess Agent screen, you'll need to shut down the agent and application.
7. Log in again to a terminal window as root.
8. To stop the WebAccess Agent and Application, enter "killall gwinter".
This will stop the WebAccess agent and Application.
9. To start the WebAccess Agent with the agent screen, change to this directory:
Figure 28 - Starting the WebAccess Agent
10. Enter this command: "./gwinter ?show @../share/webac70a.waa &"
Figure 29 - Next command
Now in the terminal window the agent status comes up.
Figure 30 - Terminal window with Agent status
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com