VOL1:GRAPHICS\

Share Name: Enter the name by which the sharepoint will be displayed to Windows computers. For example, if you enter "Lots of Pics" as the share name associated with VOL1\GRAPHICS, then Windows workstations browsing the network will see "Lots of Pics" instead of "VOL1\GRAPHICS." Connections: Enter the number of connections that will be allowed to access the sharepoint. Or, check Unlimited to allow an unlimited number of connections. Comment: Enter a description for the sharepoint that appears in Network Neighborhood.
7 At the Context Setup screen, specify the NDS contexts for your Windows (CIFS) users who
need access to this NetWare server and then click Add. NDS contexts added here are saved in a list in the CIFS context search file (SYS:\ETC\CIFSCTXS.CFG). When the Windows user enters a username, the Novell Native File Access Pack software searches through each context in the list until it finds the correct User object. For example, if you had users with full NDS distinguished names such as Robert.sales.acme, Maria.graphics.marketing.acme, Sophia.graphics.marketing, and Ivan.marketing.acme, then you would enter the following contexts: sales.acme graphics.marketing.acme marketing.acme
NOTE: If User objects with the same name exist in different contexts, each user object attempts
authentication in order until one succeeds with the corresponding password.
The CIFSCTXS.CFG context search file can be edited manually after installation. For more information, see Specifying Contexts in the Context Search File on page 28.
8 Check the Summary screen and then click Finish.
The installation program copies the required files to your server.
9 Restart the server by entering the following command at the server console:

RESTART SERVER

Starting and Stopping AFP and CIFS Protocols Service
Each time the server starts, the Novell Native File Access Protocols are loaded from commands that were automatically added to the AUTOEXEC.NCF configuration file by the installation program. You can also load and unload the Native File Access Protocols service manually at the server console.
Macintosh (AFP) Protocols 1 At the server console, enter AFPSTRT to load the Macintosh (AFP) protocols on the server.
Any changes made in the AFP configuration files since the last time you started the service are applied when the AFP protocols are reloaded.
2 At the server console, enter AFPSTOP to unload the Macintosh (AFP) protocols on the server. Windows (CIFS) Protocols 1 At the server console, enter CIFSSTRT to load the Windows (CIFS) protocols on the server.
Any changes made in the CIFS configuration files since the last time you started the service are applied when the CIFS protocols are reloaded.
2 At the server console, enter CIFSSTOP to unload the Windows (CIFS) protocols on the

server.

Whats Next?
After installing the Native File Access Pack software, you must create simple passwords for Macintosh, Windows, and UNIX users before they can access files on the server using their native protocols. To set up and manage Macintosh users, see Chapter 3, Working with Macintosh Computers, on page 17. To set up and manage Windows users, see Chapter 4, Working with Windows Computers, on page 23. To set up and manage UNIX users, see Chapter 6, Working with UNIX Machines, on page 49.
Working with Macintosh Computers
This chapter contains the following information: Administrator Tasks for Native File Access for Macintosh Services (page 17) Macintosh End User Tasks (page 19)
Administrator Tasks for Native File Access for Macintosh Services
Native File Access for Macintosh provides several ways to simplify your administration tasks and customize how Macintosh workstations interact with the network: Creating Simple Passwords for Several Macintosh Users (page 17). Editing the Context Search File (page 17). Creating a Guest User Account (page 18). Renaming Volumes (page 18).
Creating Simple Passwords for Several Macintosh Users
You can create simple passwords for users one at a time using ConsoleOne. But if you want to create passwords for several Macintosh users at once, you can add the CLEARTEXT option to the LOAD AFPTCP command at the server console. For example: LOAD AFPTCP CLEARTEXT When the CLEARTEXT option is added to the AFPTCP command, users logging in to the server from a Macintosh workstation are prompted to provide their NDS username and NDS password. Once the NDS password is verified, a simple password is automatically created and stored in NDS. The simple password is the same as the NDS password. The CLEARTEXT option is meant to be a temporary way to create simple passwords for many Macintosh users. After Macintosh users have created simple passwords, the AFPTCP NLMTM should be loaded without the CLEARTEXT option.
WARNING: The CLEARTEXT option allows unencrypted passwords to be sent over the network. If you are
concerned about someone capturing your password over the network, you should not use this option. Instead, you should manage passwords using ConsoleOne on the Administrator Workstation.
Editing the Context Search File
A context search file allows Macintosh users to log in to the network without specifying their full context. The context search file contains a list of contexts that are searched when no context is provided or the object cannot be found in the provided context. When the Macintosh user enters a username, the server searches through each context in the list until it finds the correct User object.
Macintosh allows only 31 characters for the username. If the full NDS context and username are longer than 31 characters, you must use a search list to provide access.

Working with Windows Computers 29
2 Run CONSOLEONE.EXE (located in \PUBLIC\MGMT\CONSOLEONE\1.2\BIN\). 3 Right-click the Server object and then click Properties. 4 Click the CIFS tab and select one of the three CIFS pages: Config, Attach, or Shares. 5 Enter the desired parameters in the fields provided.
See the page description sections below for details.
6 Click Apply to save your settings. Config Page Parameters
The following parameter fields appear on the Config Page under the CIFS tab in ConsoleOne: Server Name is the name of the server running Novell Native File Access Protocols. The length can be a maximum of 15 characters. This name is displayed in Network Neighborhood. This server name must be different from the NetWare Server name. Comment is the comment associated with the server name discussed above. This comment is displayed when viewing details. WINS Address is the address of the WINS server to be used to locate the PDC, if the PDC and the server running Novell Native File Access Protocols are on different subnets. Unicode specifies whether Unicode character support is enabled. Unicode characters are used in double-byte languages.
IMPORTANT: To support Unicode, an additional file named UNINOMAP.TXT must be created and saved
in the SYS:\ETC directory. When the -UNICODE value is set to On, the UNINOMAP.TXT file is used to resolve Unicode-to-ASCII "no-map" problems. To specify "no-map" cases in the UNINOMAP.TXT file, enter the first Unicode value to watch for and then the second value representing the ASCII replacement code. For example:
OpLocks is not functional in the NetWare 6 Support Pack 1 software release. Authentication Mode indicates the method of authentication used by Novell Native File Access Protocols. You can select either Domain or Local from the drop-down list: DomainClients are members of a domain. A Windows domain controller performs user authentication.The username and password on the domain controller must match the username and password used to log in to the Windows workstation. LocalClients are members of a workgroup. The server running Novell Native File Access Protocols performs the user authentication. The username and password on NetWare must match the username and password used to log in to the Windows workstation. Authentication Workgroup Name is the domain or workgroup that the server will belong to. Workgroup and Domain can be used intergchangeably. Primary Domain Controller Name is the name of the PDC server. This is needed if the PDC is on a different subnet. This option should be used only when there is a valid reason for overriding WINS or DNS.

installation.

4 Select the server running Novell Native File Access Protocols.
Although it is the same computer, the Novell Native File Access server name is not the same as the NetWare server name. For more information, ask your network administrator.
TIP: You can enter the server name or the server IP address in Find Computer to quickly access the
server running Novell Native File Access software.
5 Browse to the desired folder or file.
Mapping Drives from a Windows Computer
1 Enter your username and local password for Microsoft* Networking. 2 Click Map Network Drive.
There are several ways to access Map Network Drive. For example, you can use the Tools menu in Windows Explorer or you can right-click Network Neighborhood.
3 Browse to or enter the following path:
\\server_running_Novell_Native_File_Access_software\sharepoin t | volume | directory\
Although it is the same computer, the Novell Native File Access server name is not the same as the NetWare server name. For more information, contact your network administrator.
5 Complete the on-screen instructions for mapping the drive.
Changing Passwords from a Windows Computer
Windows users can change and synchronize their local password and their simple password. When users change the local password, they also change and synchronize their simple password.
From a Windows 2000/NT Computer 1 Press Ctrl+Alt+Delete. 2 Click Change Password. 3 In the Domain field (or the Log On To field in Windows 2000), enter the name of the server
running Novell Native File Access Protocols. If your Windows computer is running Novell Client software, click Show All Resources and select the appropriate server.
4 Enter the username, old password, and new password as prompted.
The NetWare password and the simple password will be synchronized only if the old simple password matches the NetWare password. If they are different, the NetWare password will not be changed and access to the network will be denied. To change and synchronize the NetWare password, you must use the Administrator Workstation running Novell Client software.
From a Windows 95/98/ME Computer 1 Change the local password. 1a Click Start > Control Panel > Passwords. 1b Click Change Passwords > Change Windows Password. 1c Enter the username, old password, and new password as prompted. 2 Change the simple password. 2a Click Start > Run. 2b Enter
NET PASSWORD server_running_Novell_Native_File_Access_software For example: NET PASSWORD NetWare1
WARNING: The Windows NET PASSWORD utility sends unencrypted text (called clear text) over the network. If you are concerned about someone capturing your password over the network, you should manage passwords using ConsoleOneTM from the Administrator Workstation. For more information on why this issue exists, contact Microsoft Corporation.

Setting Up for Macintosh

To set up the Macintosh portion of Novell Native File Access Protocols in an environment running Novell Cluster Services:
1 Ensure AFPTCP.NLM is loaded on all servers in the cluster by entering MODULES at the
server system console and reviewing the list of loaded modules. AFPTCP.NLM is loaded automatically on the server by the AFPSTRT.NCF file, which is automatically added to the AUTOEXEC.NCF file during the Native File Access Protocols portion of the NetWare 6 installation.
2 Cluster enable the shared-disk pools or volumes by following the procedures described in
"Create Shared Disk Partitions" in the Novell Cluster Services Overview and Installation Guide (http://www.novell.com/documentation/lg/ncs6p/index.html).
When you create and cluster enable an NSS pool or volume by following the abovereferenced procedures, a screen appears that lets you choose the advertising protocols. Ensure AFP is selected on this screen. This will cause an AFPBIND command to be added automatically to the cluster-enabled pool volume load script, which ensures that your clusterenabled pools are highly available to Macintosh clients. AFPBIND allows AFP virtual server names to be advertised via SLP.
3 (Optional) Rename cluster-enabled volumes so Macintosh users will see the same volume
name regardless of what server has the volume mounted. For instructions, see Renaming Volumes on page 18. Volumes are displayed as ServerName.VolumeName. If the server fails over, the user sees the next failover server with the same volume name. For example, Server1.VOL1 becomes Server2.VOL1. Renaming each ServerName.VolumeName to a common name displays the common name regardless which server is providing the volume. For example, renaming Server1.VOL1 to Graphics, Server2.VOL1 to Graphics, and Server3.VOL1 to Graphics displays Graphics regardless which server is providing VOL1. Macintosh clients should now be able to access files on the server cluster by entering the IP address or server name of the cluster-enabled volume.
NOTE: Novell Native File Access Protocols does not support automatic reconnect for Macintosh computers.
If the network connection between a Mac computer and one of the servers in the cluster fails, the user must reconnect using the same IP address for the cluster-enabled volume.

Setting Up for Windows

CIFS should be configured to work with Novell Cluster Services in ACTIVE/ACTIVE mode. ACTIVE/ACTIVE mode is the recommended configuration because it provides faster recovery after a failure. ACTIVE/ACTIVE mode signifies that CIFS is running simultaneously on multiple servers in the cluster. When a server fails, the cluster volumes mounted on that server fail over to other servers in the cluster and users retain access to files and directories. We recommend that you have NetWare 6 Support Pack 2 installed prior to configuring CIFS for ACTIVE/ACTIVE mode with Novell Cluster Services. To configure CIFS for ACTIVE/ACTIVE mode with Novell Cluster Services:

1 Ensure the CIFSSTRT.NCF command is in the AUTOEXEC.NCF file of each server in the
cluster that will run CIFS.
2 Create and cluster enable pools by following the instructions in the Cluster Enable Pools and
Volumes section of the Novell Cluster Services Overview and Installation documentation. When you create and cluster-enable pools, ensure the CIFS check box that appears in ConsoleOne during the pool creation process is checked, and enter the CIFS Server Name in the field provided. This will make the pool accessible and highly available to CIFS clients. The CIFS server name is the server name CIFS clients see when they browse the network. A default server name is listed, but you can change the server name by editing the text in the field. When you cluster enable a pool and make the pool accessible to CIFS clients, the CIFS ADD command along with the Fully Distinguished Name (FDN) of the virtual server (clusterenabled pool) is automatically added to the pool load script and the CIFS DEL command is
automatically added to the pool unload script. These commands are necessary to allow clients to connect to the cluster-enabled pool. If you already have pools that are cluster enabled, go to Step 3 on page 45.
3 (Conditional) To make pools that have already been cluster enabled
(virtual servers) accessible to CIFS clients, you must manually add an NFAP auxillary class attribute to the Virtual Server object and also manually add the CIFS ADD and CIFS DEL commands to the cluster volume load and unload scripts.
3a Using ConsoleOne, browse to and click the Cluster object of the
cluster that contains the cluster-enabled pool you want to make available to CIFS clients.
3b In the right pane, right-click the cluster-enabled pool, then click

Properties.

3c Click the Scripts tab and add the CIFS ADD and CIFS DEL
commands along with the Fully Distinguished Name (FDN) of the virtual server to the load and unload scripts. The FDN must include the eDirectoryTM tree name and leading and ending dots. For example, if the virtual server name is CLUSTER1_SALESPOOL_SERVER, the tree name is CAJU, and the context of the Virtual Server object is sales.novell, you would add
CIFS ADD.CN=CLUSTER1_SALESPOOL_SERVER. OU=SALES.O=NOVELL.T=CAJU.

Administration Utilities

The following administration utilities are provided with Novell Native File Access for UNIX:

SCHINST

This utility is run automatically during the installation of Native File Access for UNIX. This utility extends the schema necessary for storing the UNIX information of objects. If the directory services are reinstalled or if the NISUserDef/NFAUUser object is deleted, run this utility manually. The syntax is as follows:

schinst [ -f filename]

The -f filename is an optional parameter. It is the name of the file that contains the list of schema files that need to be extended. If a filename is not specified, the default file, SYS:\ETC\UNIXSCH, is used. SCHINST takes the administrator's FDN and password as input for extending the schema. SCHINST extends the UAM schema. It creates NFAUUser object and also adds the UNIX Profile of the root user as UID=0, GID=1, Home Directory=/home to this object. It updates the parameter NIS_ADMIN_OBJECT_CONTEXT in the configuration file NFS.CFG with the context where the object is present.
NOTE: You also have to run nisinst after this.
All log messages generated by SCHINST are written to the SYS:\ETC\SCHINST.LOG file. All information regarding schema extension can be found in SYS:\SYSTEM\DSMISC.LOG.

NISINST

This utility creates an eDirectory object with the name NISSERV_Servername by default or whatever name was specified with the -s option. NIS Server uses this object to store the domains served by the NIS Server. NIS Server validates every request against the list of domains specified in this object. It serves the request only when the domain in the request is present in the above list. The syntax is as follows:
nisinst [-s name] [-x context] [ -i ip address]
The parameter -s is optional. It specifies the name to be given to the nisserver object. The parameter -x is also optional. It specifies the context where the object should be created in eDirectory. The optional command line option -i is to specify the IP address to be attached to the NISServ Object. This option is useful in a cluster environment and for servers with multiple NIC cards. Run the NISINST manually, if the nisserver object is deleted.

WARNING: After the Novell Native File Access for UNIX installation, two objects are created in the tree:
NFAUUser / NISUserDef and NISSERV_Servername. These objects should not be deleted.

File-Based Configuration

The configuration (.CFG) files are used to configure the services. All of these files have the following format:

PARAMETER_NAME = VALUE

Within the.CFG files, a pound sign (#) indicates a comment. In addition to these configuration files, there are specific files for exported volumes for the NFS Server and for the migration utility. All the configuration files are usually located in the SYS:\ETC directory. To configure the modules, you need to change the desired parameter value in the corresponding.CFG file and restart the module.
NOTE: In a cluster environment, the configuration files will be located in the ETC directory of the shared

volume.

Configuring Server General Parameters
The server general parameters required by Native File Access for UNIX are located in the NFS.CFG file. These parameters are common to NFS and NIS. When modifying this file, make sure you stop the services using nfsstop and restart using nfsstart.
File-Based Configuration of Server General Parameters
The following table lists the configuration parameters in NFS.CFG.

Table 1

Novell Native File Access for UNIX General Parameters Parameter Default Value Description

NDS_ACCESS

Lets you set the default access to eDirectory or NIS. To set the default access to eDirectory and retrieve all information from eDirectory, set this parameter to 1. (This is the default value.) Set this parameter to 0 to retrieve information from NIS server. Lets you enable or disable NIS client. By default, NIS client access is enabled. To disable NIS client access, set this parameter to 0. Sets the NIS domain for NIS client access. No default can be provided. Provides the NIS server servicing the domain. If a specific server is needed for the domain, this parameter must be set. Otherwise, the NIS server is discovered using the broadcast. No default can be provided.

NIS_CLIENT_ACCESS

NIS_DOMAIN NIS_SERVER

SEARCH_ROOT

Contains a list of fully distinguished names of containers separated by commas. These containers indicate where the search for users and groups should start. The NDSILIB module uses this parameter. The value can be either 25 containers or a string whose length should not exceed 2000 bytes, whichever is less. If you do not set any search containers, search will start from the bindery and then in the servers default context.
ConsoleOne-Based Configuration of Server General Parameters
This section explains the following tasks: Viewing the Server General Parameters (page 60) Configuring the Server General Parameters (page 61)

Viewing the Server General Parameters 1 In the ConsoleOne main menu, right-click the server you want to configure and then click
Properties. The following panel appears:

Figure 3

Server General Parameters Panel
These are the general parameters. The fields are read-only. Host NameThe name of the NetWare server. IP AddressThe primary IP address of the NetWare server. Subnet MaskThe subnet mask that, when added to the IP address, provides the IP network number. Server NameThe name of the NetWare server. Operating SystemThe version of the operating system being used by the host. ContextThe context or logical position of the server within the eDirectory tree. TreeThe current eDirectory tree. Time ZoneThe world time zone reference for your area. The time zone is used for time stamps and to set time synchronization. The time zone reference is set during the NetWare installation.
Configuring the Server General Parameters 1 In the ConsoleOne main menu, right-click the server you want to configure and then click
Properties > Directory Access. The following panel appears:

Figure 4

Server General Parameters - Directory Access Panel
This panel contains the parameters that can be configured to set the directory access of NetWare NFS Server.
2 Modify the following Directory Access parameters as necessary:
NDSSets the access to eDirectory. Search RootLists the Fully Distinguished Name of containers from where the search should start for users and groups only. The names are separated by commas. Make sure that the parameter has valid values whenever the eDirectory structure changes. NISEnables remote NIS. Enable NIS ClientSpecifies whether the NIS Client is enabled or not. NIS ServerSpecifies the remote NIS server name. NIS DomainSpecifies the domain served by that remote NIS.
3 Click OK. 4 Modify the following parameters as necessary:
SNMP Alert LevelThe level of SNMP alerts reported to SNMP management stations. Select an alert level from the drop-down list. You can also turn off SNMP reporting from this list. NoneSuppresses SNMP reporting. CriticalWarns you about urgent problems that require immediate action to prevent widespread failure. MajorWarns you about serious problems that require prompt action to prevent failure of the object and possibly some related objects. MinorProvides information about problems that can be addressed as work schedules permit. InformationalProvides descriptive information that can be used for such things as trend analysis and planning. Each level incorporates the information from the levels listed above it. For example, if you select Minor, you also receive messages about major and critical alerts.
NOTE: Administering NetWare 5 NFS Services on NetWare 5 from ConsoleOne on NetWare 6 is not supported.

Migration of NIS Maps

If you already have an UNIX NIS Server (text-based) and you want the new NetWare NIS Server to serve the same data served by the old NIS server, you can copy all those text files into the specified location and then run the migration utility to create eDirectory entries for a specified domain. The migration utility creates the Domain object in the default context as well as two other containers in the same context with the names domainname_U and domainname_G. During the migration, the utility searches for existing eDirectory users and groups under the containers specified by the SEARCH_ROOT configuration parameter (specified in NFS.CFG) and, based on the migration option specified, modifies the UNIX information of those objects. If the objects are not found, the users are migrated to domainname_U and the groups are migrated to domainname_G. The rest of the data is migrated under the Map objects created under the Domain object.

IMPORTANT: The User and Group objects will not be created under the passwd and group Map object. They will spread across the eDirectory tree and DomainName_U, DomainName_G depending upon the SEARCH_ROOT configuration parameter.
Maps can be migrated using the following three options: UPDATE(Default) Updates all existing objects' information with the new information. If no objects exist, it creates new ones. REPLACEDeletes all existing objects and creates new ones. For passwd and group maps, the old objects are not deleted. MERGERetains all existing objects' information and logs them as conflicting records in the MAKENIS.LOG file. If no objects exist, it creates new ones. Before migrating the users and groups, remove the password field ("*", "x", or "!") from the corresponding text file and then migrate. After doing this, you can set the UNIX password. This is done by making the UNIX machine an NIS client to the NetWare machine, logging in as that NIS user, and running an NIS client utility named YPPASWD to set the UNIX password.
NOTE: The password for a migrated UNIX user (one who already has the password) cannot be set from an NIS client. A password can be set only for users who do not have a password.
For more information on UNIX user management, see UNIX User Management Using eDirectory on page 54.

File-Based Migration

Migration, by default uses the makefile SYS:ETC/NIS/NISMAKE, which contains the location of the text file for every map. The general syntax of the migration utility is: makenis [-r resultfilename -[r]d domainname [-n context] [-f nismakefilename] {[mapname -[l|b]p line or byte object in mapname].}
NOTE: All options should be used only in the specified order.
In general, to create a domain and migrate data or to use the existing domain object, use the following format:

makenis -d domainname

The parameter domainname is mandatory. To capture the results of the migration, use the following format:
makenis -r resultfilename -d domainname
To remove the existing domain data and then migrate, use the following format:

makenis -rd domainname

To specify the context where you want to create your Domain object and data, enter it as the contextname:
makenis -d domainname -x contextname
Edit the context parameter by prefixing each of the dots in the Relative Distinguished Names with a backslash (\) to distinguish them from eDirectory names. To specify an NIS makefile other than the default SYS:ETC/NIS/NISMAKE, use the following format:

makenis -d domainname -f makefilepath
To specify the text files that you want to migrate, modify the NIS makefile. The NIS makefile is in the following format:
map name full path parameters (if any)
The comment character is the pound sign (#). If nothing is specified, all the files in the makefile are migrated. For each map, you can specify the SECURE parameter so that only requests coming from secure ports are able to access the data. You can also specify the migration options: UPDATE, REPLACE, or MERGE. For the Password map, you can specify two additional parameters: -u uid (which stops users with a UID less than a particular value from migrating to eDirectory) and AUTOGEN (which generates a UID from the program itself). You must specify the text file in the full path in DOS name format. To migrate specific maps, use the following format:
makenis -d domainname mapname1, mapname2
To migrate a map from a particular offset in a specified map text file, use the following format:
makenis -d domainname mapname -lp lineoffset
makenis -d domainname mapname, -bp byteoffset
Line offset is used to start migration from a particular line from the map text file. If the migration fails while migrating large maps, instead of migrating it again from the beginning, you can specify the byteoffset to start from the offset specified in the migration log file. For more details on this offset, refer to the description of the configuration parameter FILEMARK_LOG_FREQ in NIS.CFG. Makenis adds users to the Members attribute, gives the user the rights equivalent to that of the group, and updates its Group Membership attribute.
ConsoleOne-Based Migration 1 In the left panel of ConsoleOne, click The Network.
2 Select the servers tree where you want to manage the domains and maps. 3 Click the toolbar M icon.
The following panel appears:

Figure 5 Migration Panel

4 To migrate a domain, enter the NetWare Host Name/IP Address, Domain Name, and Domain

4 To specify the advanced parameters, click Advanced on the NFS Server Options panel.
The following panel, which shows the NFS Server advanced parameters and their default values, appears.
Working with UNIX Machines 73

Figure 11

Advanced Parameters in the NFS Server Options Panel
5 Modify the following parameters as necessary:
NFS V2 ThreadsNumber of NFS Server threads servicing the NFS 2 protocol. Default = 5. Range = 1 - 150. NFS V3 ThreadsNumber of NFS Server threads servicing the NFS 3 protocol. Default = 5. Range = 1 - 150. Mount V2 ThreadsNumber of NFS Server threads servicing the Mount V2 Requests. Default = 1. Range = 1 - 150. Mount V3 ThreadsNumber of NFS Server threads servicing the Mount V3 Requests. Default = 1. Range = 1 - 150. NFS V2 TCP Send Q EntriesSize of the TCP send queue for the NFS 2 protocol. Default = 30. Range - 1 - 150. NFS V3 TCP Send Q EntriesSize of the TCP send queue for the NFS 3 protocol. Default = 30. Range = 1 - 150. NFS V2 Q EntriesSize of the receive queue for the NFS 2 protocol. Default = 20. Range = 1 - 150. NFS V3 Receive Q EntriesSize of the receive queue for the NFS 3 protocol. Default = 20. Range = 1 - 150. Log File PathDirectory that NFS Server creates the log file in. Default directory is SYS:\ETC. Log File NameName of the NFS Server Log File. Default name is NFSSERV. A.LOG extension is automatically added. NFS Server Log LevelIndicates the types of messages to be logged.

6 Click OK.

Exporting a directory enables NFS client users to view NetWare volumes and directories as part of the client file system. You can export a NetWare path and manage it.
1 Make sure you have added the NFS name space, and then select Export New Path from the
NFS Server drop-down list. The Export New Path panel appears.
Figure 12 NFS Server Export New Path Panel
2 To export a new directory, click the Browse icon in the upper-right corner of the panel.
The Export Path panel appears.
Figure 13 Browse Panel for exporting NetWare Volumes and Directories
3 Double-click the server name to see the volumes with NFS name space. 4 Select the volume or directory you want to export and click OK. 5 On the Export New Path panel, modify the following fields as necessary:

Load Script

To the load script, add the following at the end of the existing script:
nfsclust AAA.BBB.CCC.DDD shared_vol_name shared_pool_name_SERVER shared_vol_name:\ETC\NFSSTART
For the example names used in this document, the specific commands would be:
nfsclust 10.2.3.4 VOL1 NFSP_SERVER VOL1:\ETC\NFSSTART

Unload Script

To the unload script, add the following at the beginning of the existing script:
shared_vol_name:\ETC\NFSSTOP #(VOl1:\ETC\NFSSTOP, for our example) unload nfsclust unload nfsadmin delay 2 unload pkernel
NOTE: A small delay might be needed before PKERNEL can unload, to allow dependant modules to finish unloading first. If the unload pkernel command fails, the pool may go comatose rather than migrate successfully. The delay command serves this purpose.
Setting the Start, Failover, and Failback Modes
The following table explains the different resource modes.

Mode Setting Description

AUTO, MANUAL
AUTO allows Native File Access for UNIX to automatically start on a server when the cluster is first brought up. MANUAL lets you manually start Native File Access for UNIX on a server whenever you want. Default = AUTO

Failover

AUTO allows Native File Access for UNIX to automatically start on the next server in the Assigned Nodes list in the event of a hardware or software failure. MANUAL lets you intervene after a failure occurs and before Native File Access for UNIX is moved to another node. Default = AUTO

Setting

Failback

AUTO, MANUAL, DISABLE

AUTO allows Native File Access for to UNIX automatically move back to its preferred node when the preferred node is brought back online. MANUAL prevents Native File Access for UNIX from moving back to its preferred node when that node is brought back online until you are ready to allow it to happen. DISABLE causes Native File Access for UNIX to continue running in an online state on the node it has failed to. Default = DISABLE
To view or change the Start, Failover, and Failback modes, do the following:
1 In ConsoleOne, double-click the cluster object container. 2 Right-click the cluster resource object shared vol name_SERVER and select Properties. 3 Click the Policies tab on the property page. 4 View or change the Start, Failover, or Failback mode.

About This Guide

This guide describes how to install, configure, and customize iPrint. This guide is intended for network administrators and is divided into the following sections: Chapter 1, Overview, on page 5 Chapter 2, Setting Up iPrint on Your Server, on page 9 Chapter 3, Setting Up iPrint on Client Workstations, on page 13 Chapter 5, Customizing iPrint, on page 21

Additional Documentation

For documentation on installing and running Novell Distributed Print Services, the foundation of iPrint, see the Novell Distributed Print Services Administration.

Documentation Updates

The latest documentation is available at Novell documentation Web site. (http://www.novell.com/ documentation)
Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. Also, a trademark symbol (, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a thirdparty trademark.

Overview

iPrint lets mobile employees, business partners, and customers access printers from a variety of remote locations using existing Internet connections. Whether users are located in an office building, telecommuting from home, or attending a sales meeting in another country, iPrint ensures that they can print documents quickly, easily, and reliably. Using a Web browser, users point to a Web page that displays the available printers. By clicking a printer, the iPrint client is installed (if not installed previously), the printers driver is downloaded, and a printer is created in the users Printer folder, enabling the user to send documents to the printer from any application on the desktop. Using iPrint, mobile users no longer have to contact a busy network administrator to find out a printers name and context and the required print driver. Instead, mobile users work within a Web browser to locate nearby printers and download and install the latest print drivers. Companies can reduce communication costs by reducing the need to fax documents between offices. Instead, companies can use their existing Internet connections to print documents to remote printers.

Mobile Users

Gail is visiting her companys branch office in Paris. She needs to print a handout for an upcoming meeting. Gail knows she can print to the branch office printer, even though she does not know the printers name, eDirectory context, make, model, or required print driver. 1. Gail connects her laptop to the company network, clicks the iPrint link on the companys intranet Web page, and then clicks a link for the branch office she is visiting. A map of the branch office and iPrint printers displays. 2. Gail locates the office she is using and clicks the icon for the printer just outside her office. 3. The print driver is downloaded and a printer is created in the her laptops Printer folder. She didnt need to install the iPrint client software again because she had used iPrint previously at a different branch office.
4. From her application, Gail prints her handouts for the upcoming meeting.
Printing Instead of Faxing
Dan has just returned to his hotel room in Chicago after visiting with some clients. While checking his e-mail, he is reminded that he needs to submit a report to his boss in the corporate office in New York. The report is due by 8 a.m. Although he could send the report by fax, he wants a high-quality printout in color and he does not want to incur long distance telephone charges. 1. Dan uses his laptop to dial in to a local Internet Service Provider. 2. Using his Web browser, Dan accesses the companys intranet Web page. Using the iPrint map pages, he locates an iPrint color printer adjacent to his boss office. 3. After downloading and installing the print driver, Dan uses his application to send the report to the printer. 4. Dan returns to the iPrint Web page and clicks the printer again to display printer management options. He monitors the printer job list to see that his print job is completed. 5. Dan sends an e-mail to his boss telling him that the report is available at the printer.

Whats New

The following features have been added to NetWare 6 Support Pack 3:

iPrint Map Designer

Multiselect printer icons and simultaneous property modifications. Set print driver default properties such as paper size, orientation, color, collate, etc. Set an attribute on a printer so that after it is installed, the printer is removed from the workstation upon the next reboot. Obtain a list of printers from the Print Services Manager without having to authenticate.

Novell iManager

View and manage retained print jobs Remove or set holds on print jobs. Move printer agents to a different Print Services Manager. Load and unload the Print Services Manager and Broker from iManager. Additional management screens have been added to iManager such as printer settings, and editing gateway load strings. Display SNMP traps from the Novell Gateway.

iPrint Client

Install printers from the command line. Capture LPT ports and redirect print jobs to an iPrint printer using the icapture.exe command or LPT Port Redirection Windows utility. Install printers on a Windows NT/2000/XP workstation without having PowerUser or Administrator rights.

Enabling DNS on the Print Manager
To configure a DNS name for the print manager, use the print services manager command line startup switch, /dnsname=DNS_name.

Syntax

ndpsm NDPS_Manager_Object_Name /dnsname=NDPS_Manager_DNS_Name

Example

ndpsm PrintManager1 /dnsname=Printing.MyCompany.Com
where PrintManager1 is the print services manager name and Printing.MyCompany.Com is the desired DNS name.
You need to use the DNS startup switch only once. After the startup switch is used, the NDPS Manager will remember the DNS name. To change the DNS Name, use the switch with the new DNS name.
If you do not specify an IP address or DNS name when you load the NDPS Manager, the manager uses the address stored in sys:\etc\hostname. If either the IP address or DNS name specified on the command line or in the hostname file is invalid, you will receive the following error:
IP Address xxx.xxx.xxx.xxx, specified at load time, is not bound. Program execution cannot continue normally. Press Escape to continue.
To resolve this error, use a valid DNS name or IP address at the system console prompt or edit the sys:\etc\hostname file to contain a valid address.

Configuring iPrint

With your print system setup, you can configure iPrint printers. Using Novell iManager for Network Management on page 11 Configuring iPrint Printers on page 11 Other Management Tasks on page 11
Using Novell iManager for Network Management
Novell iManager is the Web-based management utility used to manage iPrint. Using iManager, you can create, delete, and modify printers and other NDPS objects. The iPrint Management plug-in for Novell iManager works only with Internet Explorer 5.5 with Service Pack 2 or later.
Configuring iPrint Printers
Complete the following steps for printers that are already set up in NDPS. To create printers to be used in iPrint, see "Creating a NDPS Printer" in the Novell Distributed Print Services Administration Guide. In Novell iManager, click iPrint Management > Manage Printer. Browse to and select the printer you want to enable IPP printing for. Click Client Support > IPP Support. Check the Enable IPP Access check box. The URL that appears in the Accepted IPP URL(s) box is the URL used when the printer is created on a workstation. This is also the URL you should use when creating iPrint maps. For more information, see Using the iPrint Map Designer on page 21. (Optional) For secure printing, check the Require Security check box. For more information, see Chapter 6, Setting Up a Secure Printing Environment, on page 27 This requires users to authenticate to eDirectory using their usernames and passwords. To update the printer settings, click Apply or OK.

Other Management Tasks

Disabling iPrint Services
In Novell iManager, click iPrint Management > Manage Printer.
Browse to and select the Printer you want to modify. Click Client Support > IPP Support. Uncheck the Enable IPP Access check box. To update the printer settings, click Apply or OK.
Enabling iPrint on All Printers Simultaneously
If you have a large number of printers that you want to enable iPrint on, use this iManager task to avoid enabling iPrint on each individual Printer object. In Novell iManager, click iPrint Management > Enable iPrint Access. Browse to and select the print service manager you want to enable IPP printing on. To enable all printers associated with this print services manager, check the first check box next to Enabled. To select printers individually, check the check box next to each printer in the Enabled column. (Optional) To enable all printers associated with this print services manager to use Secure printing, check the first check box next to Secure. To select secure printers for specific printers, check the check box next to each printer in the Secure column. For more information on implementing secure printing, see Secure Printing Using SSL on page 27. To update the printer settings, click Apply or OK.
In order for users to use iPrint, they need to install the Novell iPrint Client software and a printer. When a user selects a printer to be installed by iPrint, iPrint checks to see if the Novell iPrint Client software is installed and then installs it if necessary. Then the printer driver is downloaded and the printer is installed in the users Printer folder. iPrint Client files and printers can be installed from a Web page, or they can be distributed using ZENworks. For more information, see Using ZENworks to Distribute iPrint on page 14. This chapter helps you with the following: Client Requirements on page 13 Using the Default Printer Lists Generated by iPrint on page 13 Creating Location-based Printing on page 14 Using ZENworks to Distribute iPrint on page 14 Uninstalling the Novell iPrint Client on page 15

Client Requirements

In order for iPrint to work properly, workstations should have the following: Windows 95/98/ME or Windows NT*/2000/XP
To install a printer on Windows NT/2000, you must have Administrator rights or be a Power User and Administrator rights on Windows XP.

Using ZENworks to Distribute iPrint
You can use ZENworks to distribute the Novell iPrint Client and printers to users workstations. You take a snapshot of a workstation before installing the client and another snapshot after. ZENworks creates a list of files to install and makes the necessary changes to the Windows Registry. You could also use ZENworks to install an HTML file on the users workstations that would take them to your iPrint Web site. This would save you from having to distribute a URL to your users. Many other implementations are at your fingertips depending on your specific needs. For more information on using ZENworks, see the ZENworks online documentation (http:// www.novell.com/documentation).

Auto-client Update

Periodically, users will need to update their Novell iPrint client. When a user boots his machine, iPrint checks the default printer to ensure the user is using the latest Novell iPrint Client. When needed, a newer client is installed. Using a configuration file, you can control how this update takes place. An iprint.ini file is located in sys:\login\ippdocs on each server where iPrint is installed. This file controls whether the user should be prompted before the updated client is installed or the updated
client is installed without user intervention. When the client is installed without user intervention, the user will still see the installation program. Using a text editor, edit the iprint.ini file to reflect the settings you want. Information on the different settings is contained in the file.
The iprint.ini file should be synchronized across all servers where iPrint and a NDPS Manager
Saving Passwords for Secure Printers
When users print to a secure printer, they are prompted for the eDirectory username and password. Users can select to have their workstations remember their password for printing. For Windows NT/2000 users, passwords are saved on a per-user basis. By default ,the Remember Password feature is enabled. To disable it, use a text editor to edit the sys:\login\ippdocs\iprint.ini file to reflect the settings you want. Information on the settings is contained in the file.
Uninstalling the Novell iPrint Client
To remove the Novell iPrint Client, use Remove Programs option in the Windows Control Panel, or use the uninstall program that is available under the Novell iPrint program group in the Start menu.

are running.

The following iPrint featuers will help you to install and configure printers. Using Novell iCapture LPT Port Redirector Utility on page 17 Using a Proxy Server on page 17 Using DOS Commads on page 18 Installing User Printers on page 19 Setting Printer Persistence on page 19

volatile-date-time

This chapter describes how to customize iPrint for your company by using the iPrint Map Designer and modifying the HTML pages and iPrint Client interface. Setting Up Location-based Printing on page 21 Changing Printer Driver Default Install Options on page 25
Setting Up Location-based Printing
Using the iPrint Map Designer tool, you can quickly create a map showing printer locations. The tool lets you import floor plans that can be used to drag and drop printers to actual locations. These maps are then published on a Web server so users can install printers that are closest to their location.
Creating Location-based Maps with iPrint Map Designer

Prerequisites

Microsoft Internet Explorer 5.5 or later Novell iPrint Client installed on the workstation
Using the iPrint Map Designer
Use the iPrint Map Designer to create location-based maps using background images of your buildings. When the map is created, you must use the iPrint Map Designer to modify or update your maps. Changes to a map file that are made outside of the iPrint Map Designer are not supported. If you need to add links to a map, you should create a frameset file and then display the map file in one frame and display your links in a different frame. Creating a Map for Printing on page 21 Adding Printers from Different Print Service Managers on page 22 Hosting Maps on a Web Server on page 23
Creating a Map for Printing
Before creating the map, ensure the following: Ippsrvr.nlm must be loaded. All of your background images (maps) are copied to sys:\login\ippdocs\images\maps on the server, and any custom printer icon images are copied to sys:\login\ippdocs\images\printers. A default set of printer icons is included. These files are autodected by iPrint Map Designer at startup.
File types that can be used for background and printer icon images are JPEG, GIF, and BMP. To start iPrint Map Designer, open http://server_address:port/login/ippdocs/maptool.htm where server_address is the servers IP address or DNS name of the server where the printer agent is running.
Save the map to a local drive, then copy the map to sys:\login\ippdocs.
If you click Refresh or exit Internet Explorer without saving the map, all changes made since the last time the map was saved will be lost.
To retrieve and modify an existing map file, click Open and browse to the directory where the map is located.
Adding Printers from Different Print Service Managers
You can add printers from different print services managers to the same map. First, add the printers from one print services manager. Then click the Browse icon and select a different manager. If you need to add or modify printers from a previously used print services manager, click a Printer icon from that manager and the Printer List will be populated with printers from that manager.

<!-- ipp_printer_1--> <DIV id="ipp_printer_1" style="position:absolute;left:505;top:373;" ALIGN="center"> <A name="ipp_printer_1" href="http://print.mycompany.com:631/login/ippdocs/ ISINSTF.HTM?ippPrinterURL=ipp://print.mycompany.com/ipp/corporatehp4050n&onInstalled=status&onNotInstalled=install"> <IMG name="ipp_printer_1" src="images/printers/p1e.gif" alt="CORPORATE-HP4050N" border=0></A> <DIV ID="ipp_printer_1_caption"></DIV></DIV>
<A name="ipp_printer_1" href="http://print.mycompany.com:631/login/ippdocs/ ISINSTF.HTM?ippPrinterURL=ipp://print.mycompany.com/ipp/corporatehp4050n&onInstalled=status&onNotInstalled=install&driveroptions=papersize:legal;duplex:yes;persistence=volatile-reboot">
For more information on these settings, see Changing Printer Driver Default Install Options on page 25 and Setting Printer Persistence on page 19.
Using the Keyboard with iPrint Map Designer
You can use the keyboard to create maps using iPrint Map Designer. The following table lists the tasks to complete and the corresponding keystrokes required.
Edit the code using either or both of the following syntaxes:
&driver-options=parameter:value; &persistence=parameter:value;
The resulting code will look like this:

Save the file.

Move between fields Insert printer icon Before you can insert a printer, your focus must be the design area.

:E TO N

Tab Insert
Move printer icon within the design area Select a field

Arrow keys Enter

Creating Printer Lists
Printer lists allow users to select printers using categories that are meaningful to them. For example, you could create a list of printers by building location, department names, eDirectory Context, etc. iPrint provides a default list of printers organized by print services manager. To create a custom list, you must use an HTML editor and create links to the printers IPP URL. This URL is displayed when you enable IPP for a printer. To view a printers URL: From Novell iManager, click iPrint Management > Manage Printer. Browse to and select the printer you want. Click Client Support > IPP Support. The printers URL is displayed under Accepted IPP URL.
Customizing the HTML Interface
You can edit any of the HTML files provided or you can create your own to customize iPrint for your environment. The HTML files are installed in the sys:login\ippdocs directory. For information on the HTML interface, see Appendix A, Configuring the HTML Interface, on page 29. Some examples of ways to present printers to users are located in the sys:login\ippdocs\examples directory: Example 1 shows a fully graphical interface for locating and installing printers using standard HTML. This type of approach can also be created using the iPrint Map Designer. For more information, see Using the iPrint Map Designer on page 21. Using your Web browser, view this example from sys:\login\ippdocs\examples\example1\innerweb.htm Example 2 shows a lower maintenance approach for locating and installing printers using standard HTML. Using your Web browser, view this example from sys:\login\ippdocs\examples\example2\innerweb.htm

Secure Printing Using SSL
Secure printing takes advantage of SSL, which requires users to authenticate using their eDirectory usernames and passwords. Users authenticate once per eDirectory tree per session. The print data is encrypted, and all print communication uses port 443. Without secure printing, the printer is available to anyone inside the firewall on the network and the print data is not encrypted. Secure printing works in conjunction with the security level set for the printer. The following table shows how access is determined, depending on the level of printer security and if secure printing is enabled or disabled.
Table 1 Effects of Printer Security Printer Security Level Secure Printing Disabled (No SSL) Secure Printing Enabled (With SSL)

Low Medium (Default)

Full access Users granted access as if they had been assigned the User role. Users must use SSL and authenticate to eDirectory Users might receive an error if SSL is not enabled. (See High Security Requires User Authentication on page 28.)
eDirectory authentication eDirectory authentication and check users effective rights eDirectory authentication, check users effective roles, and connection verification SSL is automatically enabled when a printers security is changed to High when using Novell iManager.
For more information on printer security levels, see "Setting Printer Security Levels" in the Novell Distributed Print Services Administration Guide.
Considerations When Changing Printer Security
High Security Requires User Authentication
If you change the printer agent security level to high, the Requires Security check box (enabling SSL) on the IPP Support page of the printers Client Support Page in Novell iManager is enabled automatically.
When setting printer agent security at the server console, SSL is not enabled automatically, and users might receive the following error
Error message: iPrint Client - "The request requires user authentication."
To avoid the error, ensure that the Requires Security check box is checked when a printer agents security is changed to High. For more information, see Enabling SSL on page 28.

Enabling SSL Changes the Printer URL
When you check the Requires Security check box, the URL for the associated printer will change. Users who have already installed this printer will have to delete and reinstall the printer in order to use the updated URL.
Lowering Printer Security
Once a printers security is set to High and SSL is enabled with the Requires Security check box, SSL remains enabled even if the security level is lowered. If SSL is disabled, then the URL will change and users will have to reinstall the printer.

Enabling SSL

From Novell iManager, click iPrint Management > Manage Printer. Browse to and select the Printer object you want to modify. Click Client Support > IPP Support. Check/Uncheck the Requires Security check box. Click Apply or OK to update the printer settings.
This appendix discusses the HTML parameters and operations used in the iPrint interface. This information is provided to give administrators insight into how to customize their HTML files. Using this information, HTML developers can create and edit iPrint Web pages to customize them for their companies. The iPrint HTML files are located in the SYS:\LOGIN\IPPDOCS directory.
iPrint Client HTML Interface Description
The list of operations and identifiers is the same for each browser. The printer name and the operation to be performed are required parameters for all operations except op-client-interface version on page 34 and op-client-version-info on page 35. All other parameters are operationspecific or optional. Operation-specific parameters that are used out of context are ignored. If the desired output from the plug-in is HTML, a frameset needs to be used. This is to prevent some browsers from failing when they try to write to the document that invoked the plug-in. The name of the frame to receive the HTML page generated by the plug-in can be passed in using the target frame option. This target frame needs to be a named frame in the same frameset as the frame invoking the plug-in.
Internet Explorer Browser Customization
HTML Script Example on page 29 HTML Code Example on page 30

HTML Script Example

The ExecuteRequest() entry point simplifies HTML coding when working with Internet Explorer. It lets you pass/get information from the iPrint without having to reload a Web page. A result type called object is implemented and should be used only in conjunction with ExecuteRequest(). You can use ExecuteRequest and have it return results via HTML, URL, message box, or cookie. All data can be passed via the ExecuteRequest() second parameter. The first parameter is the operation. Both of the parameters are strings. Syntax: variable=variable.ExecuteRequest("operation_string",additional_operation strings);

<object ID=iPrintAccess classid=clsid:36723f97-7aa0-11d4-8919-ff2d71d0d32c> </object> <script Language="javascript1.1"> var pStatus;
var params; params = "printer-url=" + printerNameHere + "&result-type=object" pStatus=iPrintAccess.ExecuteRequest("op-printer-get-status", params); alert(pStatus); </script>

HTML Code Example

The following defines the interface between HTML pages and the browser plug-in. The HTML element <OBJECT> is used to invoke the Internet Explorer plug-in (IENIPP.OCX).
<OBJECT ID=TESTID CLASSID="clsid:36723f97-7aa0-11d4-8919-FF2D71D0D32C" CODEBASE=v:\src\work\bart\ipp\ieNIpp\final\novipp.ocx> <PARAM NAME=operation VALUE=op-printer-get-status> <PARAM NAME=printer-url VALUE=http://100.100.100.100/ipp/lpr> <PARAM NAME=result-type VALUE=html> <PARAM NAME=target-frame VALUE=displayFrameName> </OBJECT>
Netscape Browser Customization
The following defines the interface between HTML pages and the browser plug-in. The HTML element <EMBED> is used to invoke the Netscape plug-in (NPNIPP.DLL).
<EMBED TYPE=application/x-Novell-ipp width=100 height=30 operation=op-printer-get-status printer-url=http://1100.100.100.100/ipp/lpr result-type=html target-frame=displayFrameName >

HTML Parameters

The following parameters can be used to enhance the iPrint HTML pages. The parameters are used in the HTML files as PARAM NAME=parameter VALUE=identifier statements. call-back-url (page 31) debug (page 31) driver-options (page 31) error-type (page 31)
file-path-name (page 32) job-list (page 32) job-list-options (page 32) persistence (page 32) printer-url (page 33) result-type (page 33) target-frame (page 33)

call-back-url

Used to target the results from the onchange JavaScript function associated with selecting jobs from the job list. The JavaScript function causes the browser to reload the indicated control frame passing the list of selected jobs as a parameter. Example: PARAM NAME=call-back-url VALUE=CONTROL.HTM
If debug is set to True, message boxes with debug and profiling information are displayed. Example: PARAM NAME=debug VALUE=true

driver-options

As a printer is being installed, the plug-in can optionally set some default driver options. For a list of driver options, see Changing Printer Driver Default Install Options on page 25. Example: PARAM NAME=driver-options VALUE=papersize:A4;duplex:vertical;color:false

error-type

Used to tell the plug-in how to report errors associated with the requested operation. The plug-in has the ability to return the errors in.

Option Description

none msgBox html cookie url
No response. Display results in a message box. Display results as an HTML page generated by the plug-in. Put the error information in a cookie. Pass the results as a url parameter.

The plug-in defaults to the same reply mechanism that is specified in results-type if error-type is not specified.
Example: PARAM NAME=error-type VALUE=html

file-path-name

Specifies a printer ready file that can be passed to the plug-in for printing. This mechanism bypasses the print provider and the print driver. The printer does not need to be installed on the workstation to use this operation. Example: PARAM NAME= file-path-name VALUE=directory path\filename

job-list

The plug-in can perform several operations on jobs. job-list is a comma-delimited string of job IDs to indicate which jobs to operate on. A job list with the job ID of -1 is equivalent to selecting all jobs Example: PARAM NAME=job-list VALUE=3,5,7

job-list-options

When the plug-in creates the HTML for job-list, it can add buttons to allow the user to hold, resume, delete, or display information for selected jobs. This parameter is used to specify which buttons to display and support. The following are the possible buttons: op-job-hold (page 35) op-job-hold-release (page 36) op-job-cancel (page 35) op-job-get-info (page 35) Example: PARAM NAME=job-list-options VALUE= op-job-hold,op-job-hold-release,op-job-cancel, opjob-get-info

persistence

Printer installation can be temporary or permanent. If not specified, persistence defaults to persistent. Persistence is used to indicate the duration the printer is to be installed for. The choices include the following:
Printer will not be removed. Printer will be removed as the workstation reboots.
Printer will be removed at the indicated time (year, month, day, hour, minute). This option is not currently implemented.

:E TON

Examples: PARAM NAME=persistence VALUE=volatile-reboot PARAM NAME=persistence VALUE=volatile-date-time:2001,3,22,8,30

printer-url

Indicates which printer the operation should be directed to. Example: PARAM NAME= printer-url VALUE=ipp://DNS name/ipp/printername

result-type

Used to tell the plug-in how to report the results of the requested operation. The plug-in has the ability to return the results in one of the following ways:

none msgBox html

No response. Displays results in a message box. Displays results as an HTML page generated by the plug-in. Puts the results in a cookie. Passes the results as a url parameter.

cookie url

The plug-in defaults to none if results-type is not specified. Example: PARAM NAME=result-type VALUE=html

target-frame

Used to specify the name of the frame in which to put the results and/or error information into. If the operation results type is url, the target frame will be the one reloaded with the indicated URL. Example: PARAM NAME=target-frame VALUE=FrameName
Supported Operations Strings
All requests to the plug-in have two required parameters. The first is operation, and the second is results-type. All operations except op-client-interface-version and op-client-version-info require the parameter printer-url. All requests support the optional parameter error-type. With the exception of op-printer-send-test-page and op-printer-remove the printer does not need to be installed to use the following operations: op-client-interface version (page 34) op-client-is-printer-installed (page 34) op-client-version-info (page 35) op-job-cancel (page 35) op-job-get-info (page 35) op-job-hold (page 35) op-job-hold-release (page 36) op-printer-get-info (page 36) op-printer-get-status (page 36) op-printer-install (page 36) op-printer-list-all-jobs (page 37) op-printer-pause (page 37) op-printer-purge-jobs (page 37) op-printer-remove (page 37) op-printer-resume (page 38) op-printer-send-file (page 38) op-printer-send-test-page (page 38)
op-client-interface version
Description: Determines a version associated with the plug-ins HTML interface. Can also determine if a client upgrade needs to be invoked or for any other client plug-in/HTML file compatibility issues. None
Required information: Supported return types:

URL, Cookie, Object

op-client-is-printer-installed
Description: Determines if the indicated printer is installed on the workstation.

Printer URL

op-client-version-info
Description: Determines the version of the Novell iPrint Client files running on the workstation. None

Cookie, URL, Object

op-job-cancel
Description: Required information Supported return types: Deletes the indicated jobs. Printer URL, job-list
None, Message box, HTML, URL, Cookie

op-job-get-info

Description: Gets job information for indicated jobs. The information returned depends on the printer's capabilities. This information can include job name, ID, owner, size, bytes processed, hold until, priority, time created, time started printing, and time finished printing. Printer URL, job-list
Message box, HTML, URL, Cookie

op-job-hold

Description: Put sa hold on the indicated jobs. A job that is printing might not be held. Printer URL, job-list

Required information:

Supported return types:
Supported parameter is indefinite.

op-job-hold-release

Description: Required information: Supported return types: Removes the hold on the indicated jobs. Printer URL, job-list

op-printer-get-info

Description: Gets additional information about the printer. The information returned depends on the printer's capabilities. This information can include printer location, printer make and model, and supported document formats (PDLs). Printer URL

op-printer-get-status

Description: Gets status information from the indicated printer. The information returned depends on the printers capabilities. Status can include printer state, printer state reasons, printer state message, printer accepting jobs, and printer job count. Printer URL

op-printer-install

Description: Required information: Installs the indicated printer to this workstation. Printer URL
Optional information: Supported return types:
driver-options, persistence

op-printer-list-all-jobs

Description: Required information: Supported return types: Lists jobs for this printer. Printer URL

op-printer-pause

Description: Pauses the printer. If results are requested for this operation, the op-printer-get-status operation is executed to provide the new printer status. Printer URL