Oracle Internet File System Setup and Administration Guide Release 1.1 A81197-05 |
|
Server Manager is a tool that provides managing and monitoring capabilities for the Oracle iFS servers and agents. Custom agents can be written to perform specific tasks on behalf of a user or the system. Topics include:
Using Server Manager, you can start, stop, suspend, resume, and list information for the various servers and agents. You can also use Server Manager to manage the servers and agents remotely from other machines from which the agents and servers may be running. In this way, it is possible to have protocol servers running on different machines, yet managed from a single Server Manager. Server Manager itself is a server, so one Server Manager can manage any other Server Managers in the system.
The default installation is configured for three pre-defined servers to run with Server Managers:
IfsAgents
--Loads and manages all agents; runs in the background.
IfsProtocols
--Loads and manages External Server agents that start up protocol servers; runs in the background.
DefaultManager
--Used to monitor the agents and servers in the system; runs in interactive mode.
In the following diagram, three Server Managers are displayed. The first Server Manager is managing the protocol servers; the second is managing the agents; and the third Server Manager is running interactively, monitoring the servers. In addition, Oracle iFS Manager is running. These Server Managers can be running on either the same or on different machines. All three Server Managers are able to monitor any registered server or agent running in the system.
Another important tool are the log files. The log files detail the activity on the protocol server. Some servers have the option to output verbose logging. As the administrator, you will need to manage these files because over time, these files can become quite large depending upon the activity and type of logging selected. By default logging will be appended to the current log.
To use Oracle iFS Manager to manage the Server Manager instances, you use Oracle iFS Monitor. Oracle iFS Monitor uses the same Server Manager commands you use on a command line, but through a graphical interface. You still have the option of issuing Server Manager commands on the command line, but now there is an easier way of managing the servers and agents monitored by Server Manager through Oracle iFS Manager.
The Oracle iFS Monitor is only used to monitor the servers and agents started by Server Manager. You cannot use Oracle iFS Monitor to start Server Manager; you must start Server Manager from the machine where Oracle iFS was installed. However, you can use Oracle iFS Monitor to stop the agents and the Server Manager instance that is monitoring the agents.
Oracle iFS Monitor displays the servers registered with the database and the agents managed by Server Manager.
The Oracle iFS Monitor window has the following parts:
Where:
The buttons on the right side of the Oracle iFS Monitor window are used to perform Server Manager tasks. The following table describes the buttons and their purpose.
The buttons at the bottom of the Oracle iFS Monitor window are used to perform Oracle iFS Monitor window tasks. The following table describes the buttons and their purpose.
Button | Purpose |
---|---|
Refresh |
Refresh the data displayed in the Oracle iFS Monitor. |
Close |
Closes the Oracle iFS Monitor window. |
Oracle iFS Monitor is accessed through Oracle iFS Manager by selecting Monitor from the File menu. A window displays containing the Server Manager instances and agents. If you are starting Oracle iFS Monitor before starting an instance of Server Manager, no information is displayed as shown here:
When a Server Manager instance is started, select the Server Manager for which you want to view agents. The agents display in the Agents box as shown here:
All agents are displayed, even if they are have a status of Stopped.
See AlsoBefore you can use Oracle iFS Monitor, you must start at least one instance of Server Manager. For more information on starting a Server Manager instance, see Chapter 2, "Starting Oracle iFS".
If an agent has been specified in the definition file to start automatically with Server Manager, then the status of that agent displays as ACTIVE and a green light is displayed when the Oracle iFS Monitor is started. To start an agent manually, do the following:
This action may take several minutes. A yellow light and a status of Starting indicates the in the process of starting. When the agent is started, the status changes to ACTIVE and a green light is displayed.
To stop an agent, do the following:
This process may take several minutes. A yellow light and a status of Stopping indicates the agent is in the process of starting. When the agent has been stopped, the status changes to Stopped and a red light is displayed.
To stop a Server Manager instance, do the following:
This process may take several minutes. Each agent managed by the selected Server Manager is stopped and finally the Server Manager instance is stopped.
You can also perform these same tasks on the machine where Oracle iFS is installed through a command line. For more information on these commands, see "Using the Command Line to Manage Server Manager".
The Server Manager provides the ability to manage agents and protocol servers with the following commands, invoked at the command line:
Server Manager also provides good monitoring functionality. If you issue the LIST AGENTS
command, the following would be returned:
The following list describes the sort of information that is provided when issuing the LIST SERVER
command:
When the DESCRIBE
command is issued, more detailed information is provided on an agent or server, although the information returned depends upon the agent or the server.
The complete list of commands and their syntax are below. The parameters:
<agent>
--The name of the agent.
<server>
--The name of the server.
<manager>
--Either the name of the Server Manager or its ID.
<priority>
--An integer value, ranging from 1 to 10, representing the thread priority.
Oracle iFS provides agents that perform required tasks to support the Oracle iFS system. Agents run in the same process as the Server Manager that started it. Custom agents can also be written to perform specific tasks. There are four different types of agents:
Server Manager can be configured to automatically start up any agent. Any agent that is not started automatically can be started manually. Each Server Manager should have its own definition file. The definition file contains information specific to the Server Manager and the list of agents to load and manage. Once Server Manager has started and loaded the agents, any change to the definition file, including modifying the list of agents, will not be picked up until the Server Manager is shut down and restarted.
The following information is found in the definition file:
InteractiveCredentials
to true.
The following agents are provided with Oracle iFS:
All public objects have an attribute called ExpirationDate. Once this date passes, the public objects are automatically deleted. This is handled by the Expiration agent, which periodically deletes expired objects. If the expiration date of a public object passes, the agent deletes the public object. This agent runs at specific times of the day as specified in the definition (.def) file by the parameter activationtimes
.
The following information must be included in the definition file to run the Expiration agent:
The Garbage Collection agent runs at specific times of the day as specified in the definition (.def) file. Currently, this agent fixes invalid public object owners, creators, deletors, and modifiers. It uses the following four parameters for this purpose, which are specified in the definition file:
For example, a document is created and modified by "ssmith." The creator, owner, and last modifier attribute of document are set to ssmith's object id. If "ssmith" is deleted, the attribute value becomes invalid. The agent replaces these invalid attribute values with the ID of the replacement owner, creator, or deletor specified in the definition file.
The following information must be included in the definition file to run the Garbage Collection agent:
Content is stored separately from file attributes. The Content Garbage Collection agent identifies unreferenced content and deletes it. For performance reasons, the content of a document is not deleted when the document is deleted. The Content Garbage Collection agent deletes the unreferenced content. This agent runs at specific times of the day as specified in the definition (.def) file.
The following information must be included in the definition file to run the Content Garbage Collection agent:
This agent is similar to the Garbage Collection agent. This agent cleans up dangling object type references and identifies all invalid object references, such as references to objects that no longer exist, and sets these references to null for array type attributes and zero for scalar attributes. For example, this agent cleans up the owner attribute of a document pointing to directory object which was deleted and is now invalid.
The following information must be included in the definition file to run the Dangling Object AV Cleanup agent:
This agent periodically purges expired events from the event queue. The following information must be included in the definition file to run the Event Exchanger agent:
This is a special kind of agent used to start protocol servers. The External Server agent reads the command for starting up a server, and executes that command in a separate process. It also re-starts the protocol servers if they go down unexpectedly.
The default entries in the definition file are specific to the protocol server this agent is managing. This example is the External Server agent for the FTP server:
The Service Watchdog agent works together with the External Server agents. This agent cleans up after server failures. Immediately after a server failure, the failed server will show up in the list of servers. After a few minutes of server failure, the Service Watchdog agent detects that the server is no longer running and removes it from the list of servers. The following information must be included in the definition file to run the Service Watchdog agent:
The Quota agent is triggered by an event to check for any users who may have used up their quota. This agent also periodically checks all users who are active, according to a specified timer period. The agent updates the user's consumed storage. When the consumed storage is over the allocated quota, then the user will not be able to add any more documents to Oracle iFS.
A user's quota is calculated upon the content already consumed. Therefore, a user will go over quota by adding the final file that pushes the consumed storage over the allocated storage. When setting users' allocated quota, remember that a users' last file will put them over quota before being denied.
Quotas will not be enforced if:
The following information must be included in the definition file to run the Quota agent:
The Outbox Agent provides a mechanism to deliver Oracle iFS e-mail created programmatically. Oracle iFS applications creating e-mails will place the messages in the system outbox (/ifs/outbox
). The Outbox agent is notified every time an event is received indicating the insertion of an e-mail into the outbox folder. The agent sends the e-mail to the mail transfer agent (Sendmail) via SMTP.
The following information must be included in the definition file to run the Outbox agent:
After setting up the Server Manager's definition file, you may want to modify the definition files for each of the protocol servers. Each definition file contains information specific to the protocol server. If you will be running multiple copies of the same protocol server, it is strongly recommended that you have a uniquely named definition file for each instance of that protocol.
The following definitions files are discussed:
The Windows Client Protocol (WCP) is the main protocol used by the Oracle iFS Utilities on Windows 95, Windows 98, Windows NT 4.0, and Windows 2000. Only one WCP server is required for each Oracle iFS schema. If you start more than one instance of the WCP server, only the last instance started will take into effect. Make sure the correct instance of the WCP server is available.
The WCP port assignment is different from other protocols used by Oracle iFS because it does not run on any designated port. Each time it is started, the WCP finds an open port on the machine on which it is running. Exactly one WCP server should run in a system.
The following parameters must be included in the definition file to run the WCP server. To include these parameters, edit the WcpServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
The NT File System Protocol Server allows the Oracle iFS repository to appear as a local hard drive on the server machine. When using the NT File System Protocol Server, the Oracle iFS repository will be mapped to a drive letter on the server machine and can be accessed using the file system as if it were a local hard drive.
The following parameters must be included in the definition file to run the NTFS server. To include these parameters, edit the NtfsServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
This is a base implementation of the Simple Mail Transfer Protocol. Oracle iFS uses Sendmail as the mail transfer agent. The SMTP server is used as the mail delivery agent for Oracle iFS. Sendmail connects to the SMTP server via the SMTP protocol and uses it to check if inboxes for e-mail recipients exist in Oracle iFS and to deliver mail to those inboxes.
The following parameters must be included in the definition file to run the SMTP server. To include these parameters, edit the SmtpServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
This is an implementation of Internet Mail Access Protocol. This provides a mechanism for mail clients to access mail from Oracle iFS accounts.
The following parameters must be included in the definition file to run the IMAP server. To include these parameters, edit the ImapServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
The SMB server allows Windows users to easily copy files between their local drives and the Oracle iFS repository. It also allows users to browse and edit files and even execute programs directly from the Oracle iFS repository. SMB is best suited for interactive browsing and modifying documents.
The following parameters must be included in the definition file to run the SMB server. To include these parameters, edit the SmbServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
The FTP server allows users to easily transfer files between one file system and the Oracle iFS repository. FTP is particularly useful when performing bulk transfers; in regards to both ease and performance. In addition to the common FTP commands, the Oracle iFS server also has built-in parsing and versioning support.
The following parameters must be included in the definition file to run the FTP server. To include these parameters, edit the FtpServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
The CUP server responds to the requests from the Oracle iFS command line utilities, a set of low-level development tools. Since the command line utilities allow direct access to the objects and their attributes, the user must be familiar with the Oracle iFS class hierarchy to manipulate the objects. The utilities target users with deeper knowledge and understanding of the Oracle iFS objects and their relationships with one another. It is not meant to be an end-user tool.
The following parameters must be included in the definition file to run the CUP server. To include these parameters, edit the CupServer.def
file located in the $ORACLE_HOME/ifs<version>/settings
directory.
|
![]() Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|