2.1 ConsoleOne on Linux

2.1.1 Installing Linux ConsoleOne

You can install Linux ConsoleOne on any server that meets the system requirements listed in GroupWise Administration Requirements in GroupWise Product Overview in the GroupWise 2012 Installation Guide.

You must install the version of Linux ConsoleOne that is included in the downloaded GroupWise 2012 software image in the consoleone/Linux subdirectory. Under some circumstances, an older version of ConsoleOne might already be installed.

  1. In a terminal window, become root by entering su - and the root password.

  2. Make the downloaded GroupWise 2012 software image available on the Linux server where you want to install ConsoleOne.

  3. Install the IBM JRE that is required for use with ConsoleOne:

    1. Change to the admin subdirectory of the software image.

    2. Install IBM JRE 1.5:

      rpm -i NOVLc1Linuxjre-1.5.0-11.i586.rpm

  4. Change to the consoleone/Linux subdirectory of the software image.

  5. Check to see if an older version of ConsoleOne is already installed on the Linux server:

    ls /usr/ConsoleOne

  6. (Conditional) If the ConsoleOne directory exists, uninstall ConsoleOne:

    ./c1-uninstall

  7. Install the GroupWise 2012 version of ConsoleOne:

    ./c1-install

  8. Enter the numbers for the languages that you want to install.

  9. Enter 3 to install the LDAP snap-in.

  10. Decline the installation of the bundled JRE 1.4.2, which is incompatible with the JRE installed in Step 3 above.

    ConsoleOne, along with other supporting packages, is then installed to /usr/ConsoleOne.

  11. Continue with Installing the GroupWise Administrator Snap-Ins to Linux ConsoleOne.

2.1.2 Installing the GroupWise Administrator Snap-Ins to Linux ConsoleOne

After Linux ConsoleOne is installed, use the GroupWise Installation program to install the GroupWise Administrator snap-ins to ConsoleOne to the ConsoleOne installation on that server.

  1. Mount the primary domain directory of your GroupWise system to the server where you are installing the GroupWise Administrator snap-ins to ConsoleOne.

    If you need assistance with this task, see Section 2.1.5, Mounting a Linux File System for a Domain or a Post Office

  2. Change to the root of the GroupWise 2012 software image.

  3. Start the GroupWise Installation program:

    ./install

  4. Select the language in which you want to run the GroupWise Installation program, then click OK.

  5. Click Install Products > GroupWise Administration.

  6. Click Install Administration, then click OK when installation is complete.

  7. Click Configure Administration.

  8. Review the introduction, then click Next.

  9. Accept the License Agreement, then click Next.

  10. Click Next to accept the default software distribution directory:

    /opt/novell/groupwise/software

  11. Select GroupWise Administration, then click Next.

  12. When the software has been copied to the software distribution directory, click Next.

  13. Click Next to accept the default of Updating an existing GroupWise system.

  14. Browse to and select the primary domain directory for your GroupWise system, then click Update.

  15. Exit the GroupWise Administration program.

    For convenience, ConsoleOne and the GroupWise Administrator snap-ins should be installed on each Linux server where a domain is located. For some administration tasks, ConsoleOne on the local server needs to have remote servers mounted. For more information, see Section 2.1.5, Mounting a Linux File System for a Domain or a Post Office.

  16. (Conditional) If you installed ConsoleOne on Open Enterprise Server (OES) Linux, continue with Enabling File Locking on OES Linux

    or

    (Conditional) If you installed ConsoleOne on SUSE Linux Enterprise Server (SLES), skip to Section 2.1.4, Starting Linux ConsoleOne

2.1.3 Enabling File Locking on OES Linux

(Conditional) If you have installed ConsoleOne on OES Linux:

  1. As root, edit the following file:

    /etc/opt/novell/ncpserv.conf

  2. Add the following line at the bottom of the file:

    CROSS_PROTOCOL_LOCKS 1

  3. Restart the Novell eDirectory daemon:

    rcndsd restart

  4. Continue with Starting Linux ConsoleOne.

2.1.4 Starting Linux ConsoleOne

  1. Make sure that any domain directories and post office directories that you want to access from ConsoleOne are mounted to your local Linux server.

    If you need assistance with this task, see Section 2.1.5, Mounting a Linux File System for a Domain or a Post Office

  2. As root, enter the following command:

    /usr/ConsoleOne/bin/ConsoleOne

IMPORTANT:Do not start ConsoleOne using the desktop icon. You cannot access the properties of GroupWise objects in eDirectory if you start ConsoleOne from the Linux desktop.

2.1.5 Mounting a Linux File System for a Domain or a Post Office

To administer a domain that is located on a remote Linux server, you must mount the domain directory to the local Linux server. To administer a post office that is located on a remote Linux server, the domain directory for the owning domain and the post office directory must both be mounted to the local Linux server. In addition, you might also want to mount the primary domain server to each secondary domain server, so that administrative messages can flow from one secondary domain to another through the primary domain.

Working with the Linux Mount Directory

The first time you run Linux ConsoleOne on a server, you are prompted to provide a Linux mount directory on that server. The default location is /mnt. For more information, see Linux Mount Directory in Planning a Basic GroupWise System in the GroupWise 2012 Installation Guide. For convenience, you can later change the Linux mount directory, as described in Section 2.1.6, Changing the Linux Mount Directory.

Underneath the Linux mount directory, you must create a subdirectory for each file system where a domain or post office resides on a remote Linux server, that you want to be able to access from Linux ConsoleOne on the local Linux server. For example, if you have a domain directory named provo1 on a remote Linux server, you would create a provo1 subdirectory under /mnt on the local Linux server where you want to run ConsoleOne.

Mounting an OES Linux File System Using NetWare Core Protocol (NCP)

Configuring NCP

  1. In a terminal window on the OES Linux server, become root by entering su - and the root password.

  2. If you are creating a new domain or post office, create the directory where you want to create the GroupWise domain and/or post office.

    or

    If you are not creating a new domain or post office, make sure you know where the existing directory is located.

  3. Enter the following command to create the NCP volume:

    ncpcon create volume volume_name /directory

    1. Replace volume_name with a unique name for the location where you want to create the GroupWise domain and/or post office.

    2. Replace directory with the directory referenced in Step 2.

  4. Verify that the volume has been created:

    more /etc/opt/novell/ncpserv.conf

    The new volume should be listed at the end of the NCP server configuration file.

  5. Restart the Novell eDirectory daemon:

    rcndsd restart

  6. Continue with Mounting an NCP Volume.

Mounting an NCP Volume

  1. Use the following command to mount the NCP volume to the OES Linux server:

    ncpmount -S fully_qualified_hostname -V volume_name -A ip_address 
             -U fully_qualified_administrator_user /linux_mount_directory

    1. Replace fully_qualified_hostname with the name of the remote Linux server that you are mounting to the local Linux server, such as provo1.novell.com.

    2. Replace volume_name with the name of the NCP volume that you created in Step 3 in Configuring NCP.

    3. Replace ip_address with the IP address of the remote server specified in Step 1.a above.

    4. Replace linux_mount_directory with the full path for the directory that you created in Working with the Linux Mount Directory.

  2. Create a script in the /mnt directory containing the resulting mount command, then run the script.

  3. Change to the domain or post office directory that you have mounted, then enter the following command:

    touch test

    This creates a file named test across the mount and shows that ConsoleOne can also write across the mount.

  4. To make the mount persistent, so that it is automatically available whenever you reboot the Linux server, edit the /etc/fstab file with the same information that you used in the mount command.

Mounting a SLES File System Using Samba

Identifying the Directory Structure for the Samba Share

  1. In a terminal window on the SLES server, become root by entering su - and the root password.

  2. If you are creating a new domain or post office, create the directory structure new domain and/or post office.

    or

    If you are not creating a new domain or post office, make sure you know where the existing directory is located.

  3. Continue with Preparing Your Firewall to Allow Samba Connections.

Preparing Your Firewall to Allow Samba Connections

  1. In YaST, click Security and Users > Firewall, then click Interfaces.

  2. Click Change, select Internal Zone, then click OK.

  3. Click Next to view the summary, then click Finish.

  4. Continue with Configuring the Samba Server.

Configuring the Samba Server

  1. In YaST, click Network Services > Samba Server.

  2. Specify a workgroup or domain name, then click Next.

    For use in your GroupWise system, the Samba server does not need to be part of a workgroup or domain, so it does not matter what you put in this field. For example, you could use GWSYSTEM.

  3. Select Not a Domain Controller, then click Next.

    For use in your GroupWise system, the Samba server does not need to be a domain controller.

  4. Under Service Start, select During Boot.

    Because you prepared the firewall in Preparing Your Firewall to Allow Samba Connections, the Firewall Settings section shows that the firewall port for Samba is already open.

  5. Click OK to finish the basic configuration of the Samba server.

  6. Continue with Configuring the Samba Web Administration Tool (SWAT).

Configuring the Samba Web Administration Tool (SWAT)

  1. In YaST, click Network Services > Network Services (xinetd).

  2. Select Enable.

  3. In the Currently Available Services list, select swat, then click Toggle Status (On or Off).

    SWAT is off by default; this turns it on.

  4. Click Finish.

  5. Continue with Accessing SWAT.

Accessing SWAT

  1. Display SWAT in your Web browser with the following URL:

    http://localhost:901

  2. Specify the root user name and password, then click OK.

  3. On the SWAT toolbar, click Status to verify that smbd and nmbd are running.

    It is not necessary for winbindd to be running.

  4. Continue with Setting the Samba Password.

Setting the Samba Password

  1. On the SWAT toolbar, click Password.

    The User Name field defaults to root.

  2. Type, then retype, the root password, then click Add New User.

    This sets up root as a Samba user, so that Samba mounts have the read/write access required by ConsoleOne.

  3. Continue with Creating a Samba Share.

Creating a Samba Share

  1. On the SWAT toolbar, click Shares.

  2. In the Create Share field, type a unique name for the share, such as gwsystem, then click Create Share.

  3. In the Path field, specify the directory referenced in Identifying the Directory Structure for the Samba Share.

  4. In the Read Only field, select No.

  5. In the Available field, select Yes.

  6. Click Commit Changes.

  7. Continue with Mounting a Samba Share.

Mounting a Samba Share

  1. Use the appropriate command to mount the Samba share to the SLES server where you want to run ConsoleOne:

    SLES 11:

    		 
    mount -t cifs //fully_qualified_hostname/windows_share_name 
               /linux_mount_directory -o username=root,noserverino

    The noserverino option uses client-generated inode numbers instead of server-generated inode numbers, which produces a more reliable CIFS mount.

    SLES 10:

    		 
    mount -t smbfs //fully_qualified_hostname/windows_share_name 
                         /linux_mount_directory -o username=root

    NOTE:The SLES 11 mount command does not accept smbfs as a valid mount type. CIFS (Common Internet File System) is an update to the SMB (Samba) protocol.

    1. Replace fully_qualified_hostname with the name of the server that you are mounting the local server, such as provo1.novell.com.

    2. Replace share_name with the name of the Samba share that you created in Creating a Samba Share.

    3. Replace linux_mount_directory with the full path for the directory that you created in Identifying the Directory Structure for the Samba Share.

  2. Create a script in the /mnt directory with the resulting mount command, then run the script.

  3. Change to the domain or post office directory that you have mounted, then enter the following command:

    touch test

    This creates a file named test across the mount and shows that ConsoleOne will also be able to write across the mount.

  4. To make the mount persistent, so that it is automatically available whenever you reboot the Linux server, edit the /etc/fstab file with the same information that you used in the mount command.

2.1.6 Changing the Linux Mount Directory

During creation of your basic GroupWise system, you established a Linux mount directory on the server where you created your basic GroupWise system, as described in Selecting a Linux Mount Directory in Installing a Basic GroupWise System in the GroupWise 2012 Installation Guide. The mount directory information is stored in the .consoleone/SnapinPrefs.ser file in the /root directory, which is the home directory for the root user.

To change the mount directory later in ConsoleOne:

  1. Click Tools > GroupWise System Operations.

  2. Click System Preferences > Linux Settings.

  3. In the Linux Mount Directory field, browse to and select the desired mount directory, then click OK.