4
Administration Tools Overview

A full range of administration tools are provided with Oracle Files to configure Oracle Files, start and stop domains and nodes, configure nodes, manage service and server objects, work from the command line, migrate data and users to Oracle Files, and monitor domain, service, and node performance. These include:

• Oracle Files Configuration Assistant
• Management Tools
• Scripts
• Bulk Administration Tools for Oracle Files

Oracle Files Configuration Assistant

The Oracle Files Configuration Assistant wizard is used during installation to initially set up the Oracle Files domain and specify an Oracle Internet Directory credential manager to associate with the domain. As you work with Oracle Files, you may wish to change these default settings. You can do this by running the Oracle Files Configuration Assistant.

The Configuration Assistant is specific for the release of Oracle Files. The tool performs these important functions:

• Set up the domain controller.
• Set up the nodes.
• Configure protocol servers.
• Create an Oracle Files schema and all associated objects in the Oracle9i database.

You can launch the Oracle Files Configuration Assistant from the command line by executing the ifsca script, located in the following directory:

$ORACLE_HOME/ifs/files/bin

You can also prepare or modify a response file and pass the filename to the Oracle Files Configuration Assistant as a parameter, for a non-interactive, or "silent," configuration. See the Oracle Collaboration Suite Installation and Configuration Guide for details.

Management Tools

Which management tool you use will depend on the function to be performed, and whether you want to work with the Oracle Files domain as one of several middle-tier applications integrated with the Oracle Enterprise Manager Console:

• Oracle Enterprise Manager Web Site
• Administration Tabs in Oracle Files
• Oracle Directory Manager

Oracle Enterprise Manager Web Site

Oracle Enterprise Manager Web site provides Web-based management tools designed specifically for Oracle9i Application Server. You can monitor and configure the components of your Oracle9i Application Server installations as well as access basic Oracle Files domain and node functions. It also allows administrators to monitor and dynamically tune the domain's nodes, services, and servers. Using Oracle Enterprise Manager Web site, you can:

• Start and stop the domain, nodes, services, and servers using a Web browser from any machine on the network.
• Configure protocol servers, agents, nodes, services, and change settings dynamically, for the current runtime session; change settings permanently; and change default settings to be used as the basis for new servers.
• Display runtime operational data about the domain, nodes, hosts, and servers at runtime, so you can monitor performance and change system configuration, if necessary.

Accessing Oracle Enterprise Manager Web site

From your Web browser, access Oracle Enterprise Manager Web site by pointing your browser to:

http://hostname:1810/

The page you see depends on the components you configured and the choices you made during Oracle 9iAS installation.

Administration Tabs in Oracle Files

When you log in to Oracle Files as either a Site or Subscriber Administrator, you can see the administration tabs in the Oracle Files Web interface. The Site Administrator and the Subscriber Administrator log in to Oracle Files through the Administration Login Page. This page can be found at:

http://<host>:<port>/files/app/AdminLogin

See "Site Administration" and "Subscriber Administration" in the Online Help for Oracle Files for detailed information about administrative operations in the Oracle Files Web interface.

Oracle Directory Manager

Oracle Directory Manager is the administrative tool for Oracle Internet Directory.

See the Oracle Internet Directory Administrator's Guide for more information about Oracle Directory Manager.

Scripts

Administrators who want to work directly from the command line can use the scripts listed in the following table:

Table 4-1  Scripts

Script Name	Location	Description
ifsca	$ORACLE_HOME/ifs/files/bin/	Runs the Oracle Files Configuration Assistant.
ifsctl	$ORACLE_HOME/ifs/files/bin/	Starts, stops, and monitors Oracle Files domains and nodes. See "Starting Oracle Files from the Command Line Using ifsctl" for more information.
emctl	$ORACLE_HOME/bin/	Manages Oracle Enterprise Manager.
opmnctl	$ORACLE_HOME/opmn/bin/	Manages Oracle Process Management and Notification.
ifsbulkadmintools	$ORACLE_HOME/ifs/files/bin/	Runs the Bulk Administration tools.

Bulk Administration Tools for Oracle Files

A Subscriber Administrator can use the Bulk Administration tools to manage users and Workspaces in Oracle Files.

Each tool works in a similar manner: it reads an XML file containing a list of "actions" (such as creating a workspace or updating users), processes the list, and executes the actions.

The Bulk Administration tools include:

• User Administration Tool
• Workspace Administration Tool

Running the Bulk Administration Tools

To run the Bulk Administration tools, the Subscriber Administrator must run the ifsbulkadmintools script, located in the following directory:

$ORACLE_HOME/ifs/files/bin/

When you run the Bulk Administration tools, the following parameters must be specified in the following order:

1. The type of tool you want to use:
   • users for the User Administration Tool
   • workspaces for the Workspace Administration Tool
2. An Oracle Files Domain. For example:

   ifs://user-sun.us.company.com:1521:seamus:ifuser
   
   

3. A service configuration name. The default service configuration names are:

   SmallServiceConfiguration
   MediumServiceConfiguration
   LargeServiceConfiguration
   
   

4. The Oracle Files schema password.
5. The Site Administrator user name (site_admin).
6. The Site Administrator password.
7. The Subscriber Administrator user name.
8. The Subscriber Administrator password.

   Note: See "Administrative Accounts" for more information about steps 5 - 8.

   
   
9. The name of the XML file defining the list of actions to perform.

For example, to invoke the User Administration tool, you could enter the following:

ifsbulkadmintools users ifs://user-sun.us.company.com:1521:seamus:ifuser MediumServiceConfiguration ocsv2 site_admin mgr filessba welcome1 user.xml

To invoke the Workspace Administration tool, you could enter the following:

ifsbulkadmintools workspaces ifs://user-sun.us.company.com:1521:seamus:ifuser MediumServiceConfiguration ocsv2 site_admin mgr filessba welcome1 workspace.xml

User Administration Tool

The User Administration tool updates the profile of each user listed in an XML file, unless the user does not exist in the Subscriber.

Note: You cannot change user passwords with the User Administration tool.

Sample XML File

This XML file contains one action for updating users:

<?xml version="1.0" encoding="UTF-8" ?>
<users>
  <action label="update">
    <class>oracle.ifs.files.admin.bulk.user.action.UpdateNormalUsersAction
    </class> 
    <user>
      <userid>test.user</userid> 
      <quota>25</quota> 
      <locale>us</locale> 
      <publicfolder enabled="yes" /> 
    </user>
  </action>
</users>

Note: The User Administration tool performs DTD validation. For this reason, your XML file must include the DTD, either inline or referenced externally.

DTD for the User Administration Tool

<!DOCTYPE users [

  <!ELEMENT users (defaults?, (action|condition)+)>

  <!ELEMENT defaults (property+)>

  <!ELEMENT condition (condition|action)+>
  <!ATTLIST condition type NMTOKEN #REQUIRED>
  <!ATTLIST condition op NMTOKEN #REQUIRED>
  <!ATTLIST condition left CDATA #REQUIRED>
  <!ATTLIST condition right CDATA #REQUIRED>

  <!ELEMENT action (class, property*, user+)>
  <!ATTLIST action label ID #REQUIRED>
  <!ATTLIST action description CDATA #IMPLIED>

  <!ELEMENT class (#PCDATA)>

  <!ELEMENT property EMPTY>
  <!ATTLIST property name NMTOKEN #REQUIRED>
  <!ATTLIST property value CDATA #REQUIRED>

  <!ELEMENT user (userid, email?, firstname?, lastname?, quota?, locale?, 
  publicfolder?)>

  <!ELEMENT userid (#PCDATA)>
  <!ATTLIST userid enabled (yes|no) #IMPLIED>

  <!ELEMENT email (#PCDATA)>

  <!ELEMENT firstname (#PCDATA)>

  <!ELEMENT lastname (#PCDATA)>

  <!ELEMENT quota (#PCDATA)>

  <!ELEMENT locale (#PCDATA)>

  <!ELEMENT publicfolder EMPTY>
  <!ATTLIST publicfolder enabled (yes|no) "yes">
]>

Troubleshooting the User Administration Tool

You should be aware of the following limitations of the User Administration tool:

• Quota: The User Administration tool does not update a user's quota should the quota exceed the granted limit. Also, a user's quota is not updated if the new value is below that of the user's consumed storage.
• Enabling or Disabling Public Folders: A user's Public Folder that is not empty cannot be disabled.

Workspace Administration Tool

The Workspace Administration tool creates or updates workspaces. The class of the action specified in the referenced XML file determines which operation is performed. For example, if the class is CreateWorkspacesAction, one or more workspaces are created. If the class is UpdateWorkspacesAction, one or more workspaces are updated.

Sample XML File

This XML file contains one action for updating workspaces and another action for creating workspaces:

<?xml version="1.0" encoding="UTF-8" ?>
<workspaces>

  <action label="create">
  <class>oracle.ifs.files.admin.bulk.workspace.action.CreateWorkspacesAction
  </class>
    <workspace name="test_workspace" type="public">
      <description>Test Workspace for the administration tool</description> 
      <member name="test.user" access="admin" /> 
    </workspace>
  </action>

  <action label="update">
  <class>oracle.ifs.files.admin.bulk.workspace.action.UpdateWorkspacesAction
  </class>
    <workspace name="test_workspace">
      <quota>40</quota> 
      <publicfolder enabled="no" /> 
    </workspace>
  </action>

</workspaces>

Note: The Workspace Administration tool performs DTD validation. For this reason, your XML file must include the DTD, either inline or referenced externally.

DTD for the Workspace Administration Tool

<!DOCTYPE workspaces [

  <!ELEMENT workspaces (defaults?, (action|condition)+)>

  <!ELEMENT defaults (property+)>

  <!ELEMENT condition (condition|action)+>
  <!ATTLIST condition type NMTOKEN #REQUIRED>
  <!ATTLIST condition op NMTOKEN #REQUIRED>
  <!ATTLIST condition left CDATA #REQUIRED>
  <!ATTLIST condition right CDATA #REQUIRED>

  <!ELEMENT action (class, property*, workspace+)>
  <!ATTLIST action label ID #REQUIRED>
  <!ATTLIST action description CDATA #IMPLIED>

  <!ELEMENT class (#PCDATA)>

  <!ELEMENT property EMPTY>
  <!ATTLIST property name NMTOKEN #REQUIRED>
  <!ATTLIST property value CDATA #REQUIRED>

  <!ELEMENT workspace (description?, quota?, publicfolder?, member*)>
  <!ATTLIST workspace name CDATA #REQUIRED>
  <!ATTLIST workspace type (public|private) #IMPLIED>

  <!ELEMENT description (#PCDATA)>

  <!ELEMENT quota (#PCDATA)> 

  <!ELEMENT publicfolder EMPTY>
  <!ATTLIST publicfolder enabled (yes|no) "no">

  <!ELEMENT member EMPTY>
  <!ATTLIST member name CDATA #REQUIRED>
  <!ATTLIST member access (admin|RW|RO|delete) #REQUIRED>
]>

Note the following about the Workspace Administration DTD:

• The type attribute of the workspace element defaults to Private if not specified.
• If the quota element is not specified, the quota property setting defaults to the Subscriber's default Workspace quota.
• If the public folder element is not specified, the public folder property setting defaults to Enabled, if the Workspace type is public. Otherwise, it defaults to Disabled.
• The delete value for the member access property is valid only for the update action of the Workspace Administration tool.

Troubleshooting the Workspace Administration Tool

The following sections provide troubleshooting information about creating and updating workspaces using the Workspace Administration tool.

Troubleshooting Workspace Creation

You should be aware of the following limitations when you create workspaces using the create action of the Workspace Administration tool:

• A Workspace name may not already exist in the Subscriber.
• A Workspace name may not contain the following characters: \ / : * ? " < > |
• A Workspace Administrator must be specified in the list of members.
• Creation of the Workspace(s) in the Subscriber may not exceed the Subscriber's total quota.
• A Workspace name may not end in a period.

Troubleshooting Workspace Updating

You should be aware of the following limitations when you update workspaces using the update action of the Workspace Administration tool:

• Quota: A workspace cannot be updated if the new value causes the Subscriber's total quota to exceed the granted limit, or if the new value is less than the workspace's consumed storage.
• Public Folder: A workspace public folder that is not empty cannot be disabled.
• Members: A workspace must have at least one Administrator. If not, the Workspace cannot be updated.