Upgrading Policy and Distribution Services

To upgrade from ZfS 2 to ZfS 3.0.2, review the following sections:


Understanding Upgrading from ZfS 2 to ZfS 3.0.2

The Upgrade Wizard upgrades ZfS 2 Tiered Electronic Distribution (TED) objects and servers to ZfS 3.0.2. This wizard does not upgrade other ZfS components.

We recommend that you upgrade Policy and Distribution Services from the ZENworks for Servers Program CD or the ZENworks 6 Server Management Program CD. However, if you need to copy the CD structure to a hard drive, the path between the root of the hard drive and the first CD directory can contain only directory names that conform to the 8.3-character DOS file naming convention. If any long directory names exist in the path, the upgrade program will not work.

Review the following to understand what the Upgrade Wizard does, and to understand the issues involved in upgrading Policy and Distribution Services from ZfS 2 to ZfS 3.0.2:


What the Upgrade Wizard Does

In summary, the Upgrade Wizard upgrades the ZfS 2 objects to ZfS 3.0.2 objects for the associated servers. It also installs ZfS 3.0.2 software on ZfS 2 servers, and disables the servers from using the ZfS 2 software.


What the Upgrade Wizard Does Not Do

In summary, the Upgrade Wizard does not install ZfS 3.0.2 where ZfS 2 was not installed. ZfS objects are necessary for identifying target servers.


Issues Concerning Upgrading Incrementally

You use the Upgrade Wizard to upgrade Distributor and Subscriber objects in a given tree, and the ZfS software on the corresponding servers.

If you have multiple trees with ZfS objects, you will need to run the Upgrade Wizard once per tree, because the wizard discovers your target servers by their corresponding Distributor or Subscriber objects contained in the tree.

For a variety of reasons, you might need to upgrade your ZfS 2 Subscriber objects incrementally per tree. For example, because the upgrade process is done for one object and its server at a time, your network could have so many Subscriber servers that you might not want to perform the upgrade in one long session.

An incremental upgrade of your Distributors might not be necessary. Maintaining both ZfS 2 and ZfS 3.0.2 Distributors would only be warranted if you are using the NAL/TED Distribution type in ZfS 2. In this case, you would want to have one ZfS 2 Distributor manage all NAL/TED Distributions and your ZfS 3.0.2 Distributors manage the ZfS 3.0.2 Desktop Application Distributions. For more information, see Re-creating Desktop Application Distributions.

Review the following sections to determine whether to upgrade incrementally:


Incremental Upgrade Issues


Determining Whether to Upgrade Incrementally

We recommend (per tree) that you upgrade all of your Distributors first, then upgrade your Subscribers. Consider the following in determining whether to upgrade your Subscribers incrementally:


Installing ZfS Software to New Servers When You Are Also Upgrading Incrementally

If you have ZfS 2 in your network, and also have servers where ZfS has not been installed and you want to install ZfS to those servers, then to prevent incompatibility problems you must do the following in order:

  1. Upgrade your ZfS 2 servers.
  2. Install to your non-ZfS servers.

This will ensure that all Distributors and Subscribers work together correctly.

However, if your upgrade plan includes incrementally upgrading your servers and you also want to install the ZfS 3.0.2 Distributor on a non-ZfS server before completing the incremental upgrade cycles, then you will need to manually add a command line switch to the new Distributor's configuration file for compatibility between the ZfS 3.0.2 Distributor and the remaining ZfS 2 Subscribers.

The following procedure is only necessary if you plan to use ZfS 3.0.2 Distributors to send Distributions to the ZfS 2 Subscribers.

  1. Run the Upgrade Wizard to perform the necessary upgrades.

  2. Run the installation program to install the Distributor software to a server where ZfS has never been installed.

  3. To set up compatibility between a ZfS 3.0.2 Distributor and existing ZfS 2 Subscribers, perform the instructions in the following sections as necessary to edit a Distributor's configuration file:

  4. Repeat Step 2 and Step 3 for each ZfS 3.0.2 Distributor that you will use for sending Distributions to ZfS 2 Subscribers.

After editing the configuration files and restarting the ZfS 3.0.2 Distributors, ZfS 2 Subscriber servers will be able to receive Distributions from these Distributors.


Editing the Distributor's Configuration File on NetWare Servers

  1. Open SYS:\ZENWORKS\PDS\TED\TED.NCF in a text editor.

    The path to your ZENWORKS directory might be different if you used a different volume or inserted other path information between the volume and the ZENWORKS directory.

  2. Locate the line similar to the following (usually at the end of the file):

    java -mx128M -envDISPLAY=127.0.0.1:0 -noclassgc -ns -jstedexit -snTed -classpath $tedpath com.novell.application.zenworks.ted.TED CORPTREE "Distributor_Server001.TED.ZENworks.Novell" distributor_password

  3. Between the ...ted.TED phrase and your server's tree name, insert the -v2 switch.

    The line should now appear as:

    java -mx128M -envDISPLAY=127.0.0.1:0 -noclassgc -ns -jstedexit -snTed -classpath $tedpath com.novell.application.zenworks.ted.TED -v2 CORPTREE "Distributor_Server001.TED.ZENworks.Novell" distributor_password

  4. Save the configuration file > exit the text editor.

  5. In order for this configuration file change to be recognized, restart the Distributor.


Editing the Distributor's Configuration File on Windows Servers

  1. Open C:\ZENWORKS\PDS\TED\TEDSERV.CFG in a text editor.

    The path to your ZENWORKS folder might be different if you used a different drive or inserted other path information between the drive and the ZENWORKS folder.

  2. Add the following line in the file:

    flags="-v2"

  3. Save the configuration file > exit the text editor.

  4. In order for this configuration file change to be recognized, restart the Distributor.


Editing the Distributor's Configuration File on Linux and Solaris Servers

  1. Open usr/ZENworks/PDS/ted/TEDSERV.sh in a text editor.

  2. Locate the line similar to the following (usually at the end of the file):

    $ZFS_JAVA_HOME/bin/java -Xmx128M -classpath "$BOOTCLASSPATH:$tedpaths" com.novell.application.zenworks.ted.TED "$DNS_NAME" "$OBJECT_NAME" "$PWD" >/dev/null 2>&1 & echo $! > $TED_LIB/ted.pid

  3. Between com.novell.application.zenworks.ted.TED and "$DNS_NAME", insert the -v2 switch.

    The line should now appear as:

    $ZFS_JAVA_HOME/bin/java -Xmx128M -classpath "$BOOTCLASSPATH:$tedpaths" com.novell.application.zenworks.ted.TED -v2 "$DNS_NAME" "$OBJECT_NAME" "$PWD" >/dev/null 2>&1 & echo $! > $TED_LIB/ted.pid

  4. Save the configuration file > exit the text editor.

  5. In order for this configuration file change to be recognized, restart the Distributor.


Meeting Policy and Distribution Services Requirements for NetWare and Windows Servers

You can upgrade Policy and Distribution Services on the following NetWare and Windows* server platforms:

   NetWare 5.1
   NetWare 6
   Windows NT* 4
   Windows 2000

WARNING:  If you intend to upgrade incrementally, be aware that some system requirements for ZfS 3.0.2 should not be applied to servers where you will continue to use ZfS 2. Meet the server requirements only for the servers you will be upgrading to ZfS 3.0.2.

The NetWare servers where you upgrade Policy and Distribution Services must meet the following minimum system requirements:

Requirement NetWare 5.1 NetWare 6

Support Pack Version

5

For instructions, see Installing NetWare 5.1 Support Pack 3 or 4.

2 (or 3 if using JVM 1.4.1)

Novell eDirectory

8.x 1

8.x 1

Cache for ZENworks Database

32 MB

32 MB

Server RAM

384 MB; 512 MB is recommended for larger deployments of Policy and Distribution Services.

512 MB

Server CPU Type

Pentium* II or faster

To enhance ZfS efficiency, it is more important to increase the amount of RAM than to increase the processor speed.

Pentium III or faster

To enhance ZfS efficiency, it is more important to increase the amount of RAM than to increase the processor speed.

Disk Space for Policy and Distribution Services Files

35 MB

35 MB

Disk Space for ConsoleOne Files

70 MB

70 MB

Database File Location

Any volume other than SYS:

Any volume other than SYS:

1  ZfS 3.0.2 can be installed in a mixed eDirectory environment, such as servers in the directory tree containing an earlier version of eDirectory (NDS® 6.x or 7.x). However, ZfS 3.0.2 requires eDirectory 8.x to be installed, but not necessarily on the server where you are installing the ZfS software. eDirectory 8.x must simply be installed somewhere in the network so that ZfS objects can be placed in the tree during installation of the product. The only requirement for any server where you install ZfS is that it can communicate with the server where eDirectory is installed.

The Windows servers where you upgrade Policy and Distribution Services must meet the following minimum system requirements:

Requirement Windows NT Server Windows 2000 Server

Service Pack Version

6a

For instructions, see Installing Windows NT 4 Service Pack 6a.

2

For instructions, see Installing Windows 2000 Service Pack 3.

Novell eDirectory

8.x 1

8.x 1

Server RAM

384 MB

512 MB

Server CPU Type

Pentium II or faster

Pentium III or faster

Disk Space for Policy and Distribution Services Files

35 MB

35 MB

Disk Space for ConsoleOne Files

50 MB

50 MB

1 ZfS 3.0.2 can be installed in a mixed eDirectory environment, such as servers in the directory tree containing an earlier version of eDirectory (NDS® 6.x or 7.x). However, ZfS 3.0.2 requires eDirectory 8.x to be installed, but not necessarily on the server where you are installing the ZfS software. eDirectory 8.x must simply be installed somewhere in the network so that ZfS objects can be placed in the tree during installation of the product. The only requirement for any server where you install ZfS is that it can communicate with the server where eDirectory is installed.

IMPORTANT:  All target servers should have fully qualified DNS names. For more information, see Ensuring Successful DNS Name Resolution.


Before Upgrading

You need to know the following information to upgrade ZfS 2 objects and servers to ZfS 3.0.2:


Trees to Upgrade

Determine the trees where ZfS 2 objects have been installed. You need to extend the schema on these trees before upgrading. Extending the ZfS 3.0.2 schema does not remove the ZfS 2 schema extensions.

If you have ZfS 2 installed across multiple trees, you should first upgrade the Distributors per tree, then incrementally upgrade the Subscribers in those trees.


Upgrading Incrementally

ZfS 2 and ZfS 3.0.2 can coexist in your network. You can upgrade ZfS 2 objects incrementally, or all at once (per tree). Determine per tree whether you want to upgrade the ZfS 2 objects incrementally. For more information, see Issues Concerning Upgrading Incrementally.


Distributor Servers to Upgrade

The upgrade wizard displays all ZfS 2 Distributor objects in the tree.

If you are upgrading incrementally in a given tree, make lists of the installed ZfS 2 Distributor objects that you want to upgrade together. If you need to temporarily keep a ZfS 2 Distributor for distributing NAL/TED Distributions, note this Distributor separately for upgrading later.

If you will be upgrading all Distributor objects in one pass for a given tree, you do not need to make a list.


Subscriber Servers to Upgrade

The upgrade wizard displays all ZfS 2 Subscriber objects in the tree.

If you are upgrading incrementally in a given tree, make lists of the ZfS 2 Subscriber objects that you want to upgrade together, so you can use that list to select which Subscribers to upgrade.

If you will be upgrading all Subscriber objects in one pass for a given tree, you do not need to make a list.

For servers that were both a ZfS 2 Distributor and Subscriber, the Subscriber software is also upgraded when you upgrade the Distributor software (which is usually done first). Therefore, you do not need to list these Subscriber servers for upgrading again if you have already upgraded them as Distributors.

IMPORTANT:  Make sure that you do not upgrade a server to be a ZfS 3.0.2 Subscriber when it is still a ZfS 2 Distributor. If you select to upgrade a ZfS 2 Distributor to be only a ZfS 3.0.2 Subscriber, all Distributor functionality will be lost. Keep this in mind for any NAL/TED Distributors you can upgrade later.


Upgrading on NetWare and Windows Servers

If you have ZfS objects installed to multiple trees, repeat the following upgrade instructions for each tree. Also, if you are upgrading incrementally, repeat the following upgrade instructions for each incremental group.

To upgrade ZfS 2 to ZfS 3.0.2, perform the following tasks in order:

  1. Preparing to Upgrade ZfS 2
  2. Using the Upgrade Wizard
  3. Completing the Upgrade

Preparing to Upgrade ZfS 2

To prepare for upgrading ZfS 2 to 3.0.2:

  1. Review the Readme for any last-minute information concerning upgrading.

    README.TXT is located at the root of the ZENworks for Servers Program CD or in the ZENWORKSFORSERVERS directory on the ZENworks 6 Server Management Program CD. READMEZFS302.HTML is located in the DOCUMENT directory on the Program CD, and the most up-to-date HTML version is located on the Novell Documentation Web site.

  2. Make sure you have met the workstation requirements listed in Getting Started.

    IMPORTANT:  Make sure you have updated each of your ConsoleOne installations, because you will be updating the ZfS 3.0.2 snap-ins before completing the upgrade process (see Installing the New Snap-Ins to ConsoleOne).

  3. Select the workstation you will use to upgrade from.

  4. Make sure you have met all of the server requirements listed in Meeting Policy and Distribution Services Requirements for NetWare and Windows Servers.

    IMPORTANT:  Do not assume that your existing hardware and software on Distributor and Subscriber servers will meet ZfS 3.0.2 requirements. Some basic server requirements, such as minimum RAM, have changed between ZfS 2 and ZfS 3.0.2.

  5. If Java has not been unloaded on the target NetWare servers, unload JAVA.NLM.

    For example, at each NetWare server's console prompt, type:

    java -exit

    This will also cause all ZfS software to stop running on the server.

  6. If you have not already done so, log in to the eDirectory tree where you will be updating the ZfS objects.

    If you are not logged into this tree, you will not be able to select it during the upgrade process.

    You can upgrade Distributors and Subscribers one tree at a time. You can run the Upgrade Wizard as many times as needed.

    You will be extending the schema for ZfS 3.0.2 on this tree. The ZfS 2 schema extensions will remain so that you can run both versions concurrently in your network.

  7. If necessary, update your server with the required support pack to ensure that you have the correct JVM (see Meeting Policy and Distribution Services Requirements for NetWare and Windows Servers).

  8. Continue with Using the Upgrade Wizard.


Using the Upgrade Wizard

To upgrade ZfS 2 to ZfS 3.0.2:

  1. On the upgrade workstation, insert the ZENworks for Servers Program CD or the ZENworks 6 Server Management Program CD.

    The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, run WINSETUP.EXE at the root of the CD.

    IMPORTANT:  If you copied the Program CD structure to the upgrade workstation's hard drive, the path between the root of the hard drive and the first CD directory can contain only directory names that conform to the 8.3-character DOS file naming convention. If any long directory names exist in the path, the upgrade program will not work.


    Schema Extensions option on the Installation page

  2. Click Schema Extensions > follow the prompts.

    To upgrade ZfS 2 to 3.0.2, you must extend the schema on the trees where you will be updating ZfS objects.


    Policy-Enabled Server Management option on the Installation page

  3. Click the Policy-Enabled Server Management option.


    Upgrade from ZfS 2 option on the Policy-Enabled Server Management page

  4. Click the Upgrade from ZfS 2 option to start the Upgrade Wizard.

  5. If you agree with the Software License Agreement, click Accept > Next.


    Upgrade Options page

  6. On the Upgrade Options page, click the Pause File Copying check box if you want to unload Java where it is running during the upgrade process.

    Java cannot be running on a target NetWare server during the upgrade.

  7. On the Upgrade Options page, click one of the following radio buttons > click Next:

    You can upgrade only one type of object at a time.

    IMPORTANT:  You must upgrade Distributors first, because ZfS 3.0.2 Subscribers cannot receive Distributions from ZfS 2 Distributors; however, ZfS 2 Subscribers can receive Distributions from ZfS 3.0.2 Distributors, except as explained concerning NAL/TED Distributions (see Determining Whether to Upgrade Incrementally).

  8. Browse for a target tree > click Next.

    The Objects to Upgrade page is displayed, where you can select which Distributor or Subscriber objects to upgrade.

    The objects displayed in the Available Objects box are all ZfS 2 objects in the current tree of the type your are upgrading (Distributor or Subscriber).


    Objects to Upgrade page with an object to select

  9. Select one or more objects in the Available Objects box > click Add.

    The Add button moves the selected objects to the Selected Objects box.


    Objects to Upgrade page with a selection made

  10. Repeat Step 9 until you have selected all the objects you want to upgrade at this time > click Next.


    File Installation Paths and Options page

  11. On the File Installation Paths and Options page, select one or more objects in the Selected Servers list.

    Select objects individually or in groups, depending on whether their servers share the same installation paths and ZfS software launching methods.

  12. To have servers for the selected objects automatically start ZfS 3.0.2 on server startup, click the Launch Policy and Distribution Services On Startup check box.

  13. To change the default, browse for or enter the new installation directory for the selected objects.

    ZENWORKS is the default installation directory for the ZfS 3.0.2 software. For example, SYS:\ZENWORKS or C:\ZENWORKS. This is a different path than where the ZfS 2 software was installed. You should use a different path than was used for ZfS 2.

    IMPORTANT:  Do not use double-byte or extended characters in any part of an installation path, including a NetWare volume name.

    If you select multiple server objects, the Browse button is dimmed. You must enter a directory that will be used by all of the selected servers.

  14. Repeat Step 11 through Step 13 for each group of selected objects > click Next.


    Upgrade Summary page

  15. On the Upgrade Summary page, click Finish to begin the upgrade process.

    IMPORTANT:  You should not reboot the server at this time, because this would start ZfS before you have completed the upgrade process. You will be starting ZfS later (see Starting ZENworks for Servers).

  16. If you upgraded Distributors and now need to upgrade Subscribers, repeat Step 4 through Step 15.

  17. Continue with Completing the Upgrade.


Completing the Upgrade

To complete the upgrade process, do the following in order:

  1. Installing the New Snap-Ins to ConsoleOne
  2. Starting ZENworks for Servers
  3. Verifying That the Policy and Distributions Services Agents Are Loaded on NetWare Servers
  4. Verifying That the Policy and Distributions Services Agents Are Loaded on Windows Servers
  5. Updating ZfS Policies
  6. Re-creating Desktop Application Distributions
  7. Disabling the Port Broker
  8. Turning Off Security in Mixed JVM Environments

Installing the New Snap-Ins to ConsoleOne

Make sure you have already upgraded to the newest version of ConsoleOne from the ZENworks for Servers Companion CD or ZENworks 6 Companion 1 CD (see Installing ConsoleOne 1.3.5 from the Companion CD). This is required before installing the ZfS 3.0.2 snap-ins to any instance of ConsoleOne on a workstation or server.

To install the ZfS 3.0.2 snap-ins for ConsoleOne for each upgraded instance of ConsoleOne:

  1. On the installation workstation, insert the Program CD.

    The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, run WINSETUP.EXE at the root of the CD.


    Policy-Enabled Server Management option on the Installation page

  2. Click Policy-Enabled Server Management.


    Install/Upgrade option on the Policy-Enabled Server Management page

  3. Click Install/Upgrade to start the installation program.

  4. If you agree with the Software License Agreement, click Accept > Next.


    Installation Type page

  5. Click Next to perform a new installation.


    Components to Install page

  6. Click Next to install Policy and Distribution Services.


    Installation Options page

  7. On the Installation Options page, click the Create eDirectory Objects and Pause File Copying check boxes to disable those options > click Next.


    Add Servers dialog box

  8. Click Add > browse for all server objects where you installed ConsoleOne to the server.


    Server Selection page

  9. For these servers where you installed ConsoleOne, click the ConsoleOne Snap-ins check box.

  10. If you installed ConsoleOne on your current workstation, click the ConsoleOne Snap-ins check box for Local Machine.

  11. When you have finished configuring the selected servers, click Next.


    Installation Summary page

  12. On the Installation Summary page, click Finish to install the ZfS 3.0.2 snap-ins to each copy of ConsoleOne you identified in Step 9 through Step 10.

  13. After the installation program has finished, review the installation log file to determine whether any components failed to install.

    The log file is located at:

    C:\TEMP\_RESNumber.TXT

    where Number is increased incrementally each time a new installation log is created.

  14. If necessary, rerun the installation program.

    Select only the components that failed to install.

  15. Repeat Step 1 through Step 14 for each workstation where you need to update ConsoleOne with the new ZfS 3.0.2 snap-ins.

  16. Continue with Starting ZENworks for Servers.


Starting ZENworks for Servers

You must start ZfS 3.0.2 on servers where you have upgraded from ZfS 2 in order to complete the upgrade process for servers that are managed using policies.

  1. On a server where you upgraded from ZfS 2 to 3.0.2, do the appropriate procedure for your platform:

    Server Platform Procedure

    Windows NT 4
    or
    Windows 2000

    Do the following on each Windows server:

    1. Open the Control Panel.
    2. On Windows NT, double-click Services.
      or
      On Windows 2000, double-click Admin Tools > double-click Services.
    3. Start the Novell ZfS Policies service.

      This will also start the Novell ZfS Distribution service, and the Novell Zen Web Server service. The Novell Sybase Database service is automatically started by the installation program.

    NetWare 5.1 and NetWare 6

    To start ZfS, enter the following command at the server's console prompt:

    sys:\zenworks\pds\smanager\zfs.ncf

    If you used a different volume, or added other path information before the ZENWORKS directory, replace the SYS: portion with the alternate path information. Enter the complete path.

    After you have started ZfS in this manner, and after the server has rebooted once, the full path will no longer be needed for start the software---you will only need to enter zfs thereafter.

    TED.NCF and ZWS.NCF are started automatically by the ZFS command. The database is automatically started by the installation program.

  2. Repeat Step 1 for each server that you upgraded.

  3. Continue with Updating ZfS Policies.


Verifying That the Policy and Distributions Services Agents Are Loaded on NetWare Servers

  1. On the target server's console, press Ctrl+Esc to view the loaded software programs.

  2. If the ZfS item (Policy/Package Agent) is not displayed, review the ZFSINIT.TXT file (under ZENWORKS\PDS\SMANAGER), which contains information about why the agent did not start.

    Use this information to reinstall ZfS to the server.

    This file is used to log startup problems only.

  3. If the TED item (TED Agent) is not displayed, review the DEFAULTLOG.TXT file (under PDS\TED), which contains information about why the agent did not start.

    Use this information to reinstall ZfS to the server.

    This file is used to log startup problems only.

  4. Repeat Step 1 through Step 3 for each NetWare server.

  5. Rerun the installation program as necessary (see Installing Policy and Distribution Services).


Verifying That the Policy and Distributions Services Agents Are Loaded on Windows Servers

  1. On the target server, open the Control Panel > double-click Services (on Windows 2000, double-click Admin Tools > click Services) > determine if the following services are running:

    Novell ZfS Policies
    Novell ZfS Distribution
    Novell Zen Web Server
    Novell Sybase Database

  2. Repeat Step 1 for each Windows server.

  3. Rerun the installation program as necessary (see Installing Policy and Distribution Services).


Updating ZfS Policies

If a server that was upgraded to ZfS 3.0.2 is managed using policies, you must create a Policy Package Distribution for those policies. ZfS 3.0.2 distributes policies to enforce them, whereas ZfS 2 associated those policies.

To update a policy:

  1. Create a Distributed type of policy package. For steps, see "Creating a Policy Package" in "Server Policies" in "Policy and Distribution Services" in the Administration guide.

  2. Create a Policy Package Distribution for the policy package you created in Step 1. For steps, see "Distributions" in "Tiered Electronic Distribution" in "Policy and Distribution Services" in the Administration guide.

  3. Create a Channel for the Distributed Policy Package you created in Step 1. For steps, see "Creating and Configuring Channels" in "Tiered Electronic Distribution" in "Policy and Distribution Services" in the Administration guide.

  4. Associate the affected Subscribers with the new Channel. For steps, see "Associating Subscribers with Channels" in "Policy and Distribution Services" in the Administration guide.

  5. Repeat Step 1 through Step 4 for each ZfS 2 associated policy that needs to be replaced with a distributed policy.

  6. If necessary, continue with Re-creating Desktop Application Distributions.


Re-creating Desktop Application Distributions

Because the software for the Desktop Application Distributions was changed, you will need to re-create all of your ZfS 2 NAL/TED Distributions.

Desktop Application Distributions must be built using a ZfS 3.0.2 Distributor and distributed to a ZfS 3.0.2 Subscriber.

For information on creating a new Desktop Application Distribution, see "Desktop Application Distribution" in "Policy and Distribution Services" in the Administration guide.


Disabling the Port Broker

The port broker is not used in ZfS 3.0.2. Therefore, you must disable it on all ZfS 2 Subscriber servers where Distributions will be received from ZfS 3.0.2 Distributors. Do this for all ZfS 2 Subscriber servers that need to be part of the ZfS 3.0.2 community, but have not yet been upgraded.

IMPORTANT:  For each server where the port broker is disabled, ZfS 2 policies cannot be run for the server. You will need to reissue the server's policies via ZfS 3.0.2 Distributions. Also, this disables the Remote Web Console capability of ZfS 2 for the server. This capability has been replaced by the Novell iManager Web management role in ZfS 3.0.2.

To disable the port broker on ZfS 2 machines:

  1. On a ZfS 2 server, open SYS:\TED2\SUB.NCF in a text editor.

  2. Locate the line similar to the following (usually at the end of the file):

    java -mx128M -envDISPLAY=127.0.0.1:0 -noclassgc -ns -jstedexit -snTed -classpath $tedpath com.novell.application.zenworks.ted.Receiver ZFS_TREE

  3. Between the ...ted.TED phrase and your server's name, insert the -nobroker switch.

    The line should now appear as:

    java -mx128M -envDISPLAY=127.0.0.1:0 -noclassgc -ns -jstedexit -snTed -classpath $tedpath com.novell.application.zenworks.ted.Receiver -nobroker ZFS_TREE

  4. In this file, locate and remove the line that starts the port broker.

    For example, search for "pbroker.ncf" and remove the line containing that text.

  5. Save the configuration file.

  6. Open SYS:\TED2\DIST.NCF in a text editor > locate and remove the line that starts the port broker.

  7. Save the configuration file.

  8. Open SYS:\SMANAGER\ZFS.NCF in a text editor > locate and remove the line that starts the port broker.

  9. Save the configuration file > exit the text editor.

  10. Unload Java and restart the ZfS 2 processes (ZFS.NCF or DIST.NCF or SUB.NCF).

    This will make ZfS run without the port broker.

  11. Repeat these steps on each ZfS 2 server.


Turning Off Security in Mixed JVM Environments

The security feature provides Subscribers with the ability to verify that a Distribution is being sent from a trusted Distributor.

However, if you are running TED in a mixed JVM environment (for example, some Distributors or Subscribers are running with JVM 1.1.7b, and others have JVM 1.2.2, JVM 1.3, or JVM 1.3.1), you must turn off the security feature of TED before Distributions can be sent successfully from ZfS 3.0.2 Distributors.

To turn off the security feature:

  1. Delete or rename the security subdirectory.

    On NetWare servers, this subdirectory is located at SYS:\TED2\SECURITY.

    On Windows NT or Windows 2000 servers, the TED2 directory is located on the drive containing the SYS share. The default location is C:\NOVELL\TED2\SECURITY, with C:\NOVELL being shared as SYS.

    IMPORTANT:  If you fail to rename or delete the TED2\SECURITY subdirectory, the Subscriber will detect the presence of the security certificates and will start with security turned on.

  2. In the TED2 subdirectory, locate and edit the SUB.NCF or SUB.BAT file:

    1. In the .NCF or .BAT file, find the line at or near the bottom of the file that reads:

      SUB.NCF 

      java -mx128M -noclassgc -ns -jssexit -snSubscriber -classpath $tedpaths com.novell.application.zenworks.ted.Receiver TREENAME

      or

      SUB.BAT 

      jre -mx128M -noasyncgc -cp %tedpaths% com.novell.application.zenworks.ted.Receiver TREENAME

    2. After the ted.Receiver text, insert the command:

      -nosecurity

      The line should now read:

      SUB.NCF 

      java -mx128M -noclassgc -ns -jssexit -snSubscriber -classpath $tedpaths com.novell.application.zenworks.ted.Receiver -nosecurity TREENAME

      or

      SUB.BAT 

      jre -mx128M -noasyncgc -cp %tedpaths% com.novell.application.zenworks.ted.Receiver -nosecurity TREENAME

    3. Save the SUB.NCF or SUB.BAT file.

  3. Restart the Subscriber.

    When you restart the Subscriber, the following message will be displayed:

    WARNING: Security measures are disabled!