A User Interface

Displays the current Content Server status on the Admin Server home page. Use the Oracle WebLogic Server Administration Console to start, stop, or restart the Content Server instance.

Displays the Component Manager Page, which is included as part of the Admin Server page. Use this page to view, enable, and disable Content Server components. From this page you also can access the Advanced Component Manager Page.

Displays the Admin Server General Configuration screen, which contains the same settings as shown on the System Properties: Options Tab. Use this page to view or modify general Content Server configuration.

Displays the Admin Server Content Security screen, which contains the same settings as shown on the System Properties: Content Security Tab. Use this page to view or modify Content Server security configuration.

Displays the Admin Server Internet Configuration screen, which contains the same settings as shown on the System Properties: Internet Tab. Use this page to view or modify internet configuration for the Content Server instance.

Displays the Admin Server Output screen. Use this page to view console output.

Displays the list of Content Server log files.

Displays the Providers Page.

Displays the System Audit Information Page, which provides general information about the Content Server instance, plus information on localization, tracing sections, cache, configuration entry, and component reports.

If selected, JDBC is enabled. This is the default.

Choose one of the driver options:

• JTDS JDBC Driver: JDBC Driver name and JDBC Connection String entered automatically.

• Oracle Thin JDBC Driver: JDBC Driver name and JDBC Connection String entered automatically.

• Oracle OCI Driver: JDBC Driver name and JDBC Connection String entered automatically.

• Sybase JDBC Driver: JDBC Driver name and JDBC Connection String entered automatically.

• Informix JDBC Driver: JDBC Driver name and JDBC Connection String entered automatically.

• Other JDBC Driver: You must enter the correct JDBC Driver Name and JDBC Connection String.

If unselected, JDBC is disabled.

If selected, the database is case sensitive (such as Oracle or Informix).

If unselected, the database is not case sensitive.

If selected, a database driver classpath must be specified in the Database Driver Classpath field to support a database connection.

If unselected, no database driver classpath is required.

Classpath for the database driver.

Name of the JDBC driver.

• For all options except Other JDBC Driver, the correct name is entered automatically.

• For the Other JDBC Driver option, you must enter the correct driver name.

Connection string for the JDBC driver.

• For all options except Other JDBC Driver, the correct connection string is entered automatically.

• For the Other JDBC Driver option, you must enter the correct connection string.

The connection string format is JDBC:ODBC:name, where name is the System Data Source Name. To find this name on a Windows system, perform the following steps:

1. Click Programs in the Start menu.

2. Click Administrative tools in the Programs menu.

3. Click Data Sources in the Administrative tools to open ODBC screen.

4. Select the system DSN tab on the ODBC Data Source Administrator screen. The System Data Source Names are displayed on this tab.

User name that owns the tables inside the database.

Password for the user name that owns the tables inside the database.

Select how the Content Server instance handles several language-specific issues such as the language of the user interface, stemming rules, sort order, and date/time format.

Select the time zone in which the Content Server instance is located. The specified time zone can be used to present times relative to other time zones, such as correcting for Daylight Savings Time, or presenting the date and time of a content item on a Content Server instance in North America to users in Europe.

If the Detect timezone automatically option is selected, a time zone is not specified in the configuration file, and the Content Server instance uses the time zone set for the computer's operating system.

The instance name that is displayed in the Windows Start menu.

Not currently used.

Restricts access to the Content Server instance to computers with the specified IP address.

• By default, this field is pre-filled with the IP address of the local host (127.0.0.1).

• You can specify multiple IP addresses, separated by pipes ( | ). Make sure that there are no spaces on either side of the pipe character. (For example, 127.0.0.1|10.10.50.143)

• You can use wildcards in this field, * for zero or many characters, and ? for any one character. (For example, 10.10.3.*)

• Generally, use only the IP Address Filter field or Hostname Filter field, not both. (IP Address Filter is more commonly used.)

Enter the password for the proxy.

Re-enter the password for the proxy.

If selected, internal JSP support is enabled in the Content Server instance.

If unselected, internal JSP support is disabled.

For details, see Java Server Page and JavaBean Guide.

In the Admin Server, this checkbox is displayed on the Admin Server: General Configuration Page.

Enter the security groups that are enabled for internal JSP support.

For details, see Java Server Page and JavaBean Guide.

In the Admin Server, this field is displayed on the Admin Server: General Configuration Page.

Location of the browser executable that will be used to display the online help from the standalone administration utilities and applications.

• For Windows 2000 systems, the default is c:/Program Files/Internet Explorer/iexplore.exe.

• For UNIX systems, the path for the web browser is requested during installation.

Click Browse to navigate to the executable file for the Help browser.

The path to the Java class files.

• By default, the CLASSPATH points at classes/, shared/classes/, and shared/classes/server.zip.

• If an Oracle or Informix database is used, the CLASSPATH will include a JDBC driver zip file, such as shared/classes/classes111.zip.

The path to the shared directory.

• This directory contains shared files for the Content Server instance, such as resource files, template files, and binaries such as mkvdk.

• If the Inbound Refinery is installed, this directory contains the conversion engines, and all Inbound Refinery temp work is done in this directory and its subdirectories.

• The default is IdcHomeDir/resources/.

Incrementally updates the index database automatically approximately every five minutes, regardless of whether an event (such as file checkin) has triggered the Indexer.

The search index is entirely rebuilt, and the old index collection is replaced with a new index collection when the rebuild is successfully completed.

Current place in the indexing cycle:

Initialization: The indexing cycle is being initialized.

Adding to collection...: Revisions are being indexed.

Finished: The indexing cycle is completed or has been canceled.

Status of the indexing cycle:

Idle: No indexing cycles are in process.

Active: An indexing cycle is currently running.

Interrupted: The indexing cycle was interrupted, either by a suspension or an unexpected event (such as a power, database, or file system failure).

Suspending: The indexing cycle is being suspended.

Cancelling: The indexing cycle is being canceled.

Date and time the last indexing cycle started.

Date and time the last indexing cycle finished.

If the indexing cycle is currently active, the date and time the cycle became active.

Counter values for the current indexing cycle.

Total: The total number of documents indexed.

Full Text: The number of full-text indexed documents.

Meta Only: The number of documents for which only metadata has been indexed.

Delete: The number of documents deleted from the search index.

Begins the indexing cycle, or restarts a cycle that was suspended or interrupted. Corresponds to the Start index update and Start index rebuild links in the Actions section of the Administration tray. These links enable you to remotely manage indexing functions.

Stops the indexing cycle and permits a restart. Corresponds to the Suspend index update and Suspend index rebuild links in the Actions section of the Administration tray. These links enable you to remotely manage indexing functions.

Stops the indexing cycle but does not permit a restart. Corresponds to the Cancel index update and Cancel index rebuild links in the Actions section of the Administration tray. These links enable you to remotely manage indexing functions.

Displays either the Automatic Update Cycle Screen or the Collection Rebuild Cycle Screen, which enable you to adjust the files per batch, checkpoint, and debug level.

The maximum number of files that the search index will process simultaneously. The default is 25. For example, 25 files are indexed together, then the next 25 files are indexed. However, if one item fails, then the batch is processed again.

Thus, if you set this value to 2000 and a document fails, the entire batch would be reprocessed. This would take longer than if you use the default setting and an item fails. But, if there are no failures in the batch, then setting this value higher accelerates the process.

The only time you would change this setting to one (1) is if you are experiencing problems with the search engine indexing large and complicated files.

The number of files that will go through all relevant indexing states at a time. You can have multiple batches of files indexed per checkpoint. After the checkpoint is reached, some merging of the collection is done before the next batch is processed.

If this is set to a high value and you try to cancel a rebuild or an update cycle, the Repository Manager does not stop processing until the checkpoint is reached. However, setting the value too low slows down the indexing process.

The Indexer debug level. The more debug information listed in the server window, the slower the indexing progresses. The following list shows the debug levels from the least to the most debug information:

none: No information for each file access is displayed, and no log will be generated.

verbose: Displays information for each file accessed. Indicates indexed, ignored, or failed, and generates a full report.

debug: Displays the medium level of information, which is specifically functional.

trace: Displays the lowest level of information for each activity performed.

all: Displays the highest level of debug information.

If selected, the index database is updated automatically.

The maximum number of files that the search index will process simultaneously. The default is 25. For example, 25 files are indexed together, then the next 25 files are indexed. However, if one item fails, then the batch is processed again.

Thus, if you set this value to 2000 and a document fails, the entire batch would be reprocessed. This would take longer than if you use the default setting and an item fails. But, if there are no failures in the batch, then setting this value higher accelerates the process.

The only time you would change this setting to one (1) is if you are experiencing problems with the search engine indexing large and complicated files.

The number of files that will go through all relevant indexing states at a time. You can have multiple batches of files indexed per checkpoint. After the checkpoint is reached, some merging of the collection is done before the next batch is processed.

If this is set to a high value and you try to cancel a rebuild or an update cycle, the Repository Manager will not stop processing until the checkpoint is reached. However, setting the value too low will slow down the indexing process.

The Indexer debug level. The more debug information listed in the server window, the slower the indexing progresses. The following list shows the debug levels from the least to the most debug information:

none: No information for each file accessed is displayed.

verbose: Displays information for each file accessed. Indicates indexed, ignored, or failed.

debug: Displays the medium level of information.

trace: Displays the lowest level of information.

all: Displays the highest level of information.

Database and Database Full-Text Search do not support indexer debug levels, so only the none option is displayed if you use a database for search and index.

Displays status information and actions for weblayout publishing. You can publish dynamic layout files, or publish static layout files, or view trace.

Displays status information and actions for schema publishing. You can publish schema configuration, or publish schema configuration and data, or view trace.

Displays status information and actions for localization indexing. You can build string index.

Displays status information and actions for the document index update cycle. You can start, suspend, and cancel an update cycle.

Displays status information and actions for the document index rebuild cycle. You can start, suspend, and cancel a rebuild cycle.

The search engine to be used to search the zone text fields (either Database or DatabaseFullText).

List of the zone text fields for the selected search engine. You can use the [Ctrl] and [Shift] keys on your keyboard to select multiple fields.

List of the available text fields for selected search engine.

By default, text fields with a field length of 20 or less characters are not included in the Text Fields list. You can change this setting by modifying the MinFullTextFieldLength configuration variable.

Use the arrows to move selected fields between the Zone Text Fields and Text Fields lists.

Enables text fields in the Zone Text Fields list as zone text fields, and disables text fields in the Text Field list. Parses the text within all zone text fields and creates a full-text index that can be queried using the Contains search operator.

Changing a text field to a zone text field can be a very time-consuming operation. The amount of time it takes to parse the text and create the full-text index depends on the number of content items in the Oracle WebCenter Content Server instance and the amount of text stored in the text field. However, when the text field has been indexed, you should not experience significant performance issues when updating and adding content items.

Reverts the Zone Text Fields and Text Fields lists to the last saved lists.

Displays the Hint Rules Configuration Page.

Displays the Query Converter Page.

Displays the Hint Cache Updater Page.

Key: Unique name to identify the rule.

Table: The specific database table.

Column: The specific column within the database table listed in the Table column.

Operator: A comma-delimited list of allowable operators.

Index: The specific index to use in the optimized queryif the condition meets the hint rule requirements.

Order: The preferred order to use when the rule is included in the Hint Rules Table.

Values: This column is Idoc Scriptable. This column can only be defined when the Operators column has one of two specific values.

AllowMultiple: Indicates whether the defined index is used with other indexes.

Disabled: Indicates whether a hint rule has been disabled.

Unique name that identifies the hint rule.

The database table associated with the hint rule. The menu lists the current database tables. Selecting a table from the menu automatically populates the Column field, Column menu options, Index field and Index menu options.

The database table column associated with the hint rule. Selecting a column from the menu automatically populates the Index field and Index menu options.

The index associated with the hint rule.

The specific operator(s) associated with the hint rule. Valid options include:

equal: Compares records to find equal values.

like: Compares records to find similar values.

in: Compares records to find values equal to any member of the specified item(s). Using this operator enables you to define the Values field.

greater: Compares records to find larger values on the left.

ge: (greater than or equal to) Compares records to find equal values or larger values on the left.

le: (less than or equal to) Compares records to find equal values or smaller values on the left.

less: Compares records to find larger values on the right.

notEqual: Compares records to find different values.

notIn: Compares records to find values that are not equal to any member of the specified item(s). Using this operator enables you to define the Values field.

notLike: Compares records to find dissimilar values.

generic: This operator is necessary if multiple operators are used in the conditions and are connected by an OR conjunction. For example: dIndexerState IS NULL OR dIndexerState IN ('N', 'Y').

range: This operator can be applied to an Integer field or a Date field. This operator is necessary when the Values field is defined with a valid range of values that would cause the hint to be applied. Using this operator enables you to define the Values field.

In descending order from 5 to 1, indicates the preference value of the hint rule. During the optimization process, the highest ranked hint rule that meets the condition's requirements is selected.

Applicable quantities when used with the operators in, notIn, and range; see the Operators field.

Specifies whether multiple indexes can be used.

Yes: The defined index can be used with other indexes.

No: The defined index must be used alone.

Add a hint rule or activate a disabled hint rule.

Deactivate the selected rule.

Toggles to display or hide the fields related to converting a data source.

f selected, on the Query Converter page, displays all the fields.

If unselected, on the Query Converter page, hides the DS Name menu and text area and the Additional Parameters field on the Hint Cache Updater Page.

Available data source names. When you choose a name, the text area displays the current contents of the data source query.

One or more variables that are evaluated for the data source used to generate a query related to a specific environment.

where Clause: This field is displayed when the Use Data Source checkbox is selected. Enables you to enter additional conditions that are appended to the existing WHERE clause in the data source. You can copy and paste an existing WHERE clause or enter it manually.

Query: This field displays when the Use Data Source checkbox is unselected. Enables you to enter a full query to be evaluated. You can copy and paste an existing query or enter it manually.

Submits the information for the data source or query to be evaluated using the Query Optimization Process. The submitted data source or query is converted from a standard query to an optimized query that uses customized hints.

Toggles to display or hide the fields related to managing the data source-based entries in the hint cache.

If selected, the Hint Cache Updater page displays all the fields.

If unselected, the Hint Cache Updater page hides the DS Name menu and text area and the Additional Parameters field.

Available data source names. When you select a name, the text area displays the current contents of the data source query.

One or more variables that are evaluated for the data source used to generate a query related to a specific environment.

where Clause: This field is displayed when the Use Data Source checkbox is selected. Enables you to enter additional conditions that are appended to the existing WHERE clause in the data source. You can copy and paste an existing WHERE clause or enter it manually.

Query: This field displays when the Use Data Source checkbox is unselected. Enables you to enter a full query to be evaluated. You can copy and paste an existing query or enter it manually.

Additional hints for the data source or query. If you enter one or more Content Server Hints, the Oracle Query Optimizer component will consider them as default hints and they will not go through the Query Optimization Process. If you enter multiple hints, the feature will look for the best hint and, if possible, select multiple hints.

Evaluates the submitted query and checks the hint cache to determine if matching hints already exist. If so, they are returned. If not, the message, Hint does not exist in cache is displayed.

With data source: Combines the WHERE clause and hints and applies the additional parameters before submitting the query for evaluation.

Without data source: Combines the query and hints before submitting the query for evaluation.

Ensures that the data source or query will always use the specified hints because the hint cache is updated. Thus, clicking this button results in a manual overwrite of the previously defined hint cache. From now on, the new hints will be used with this particular query.

Removes the information entered into any of the fields for the specified query.

Name of the partition as defined when the partition was created using the Add/Edit Partition Page. The partition name is part of the path expression used by the Content Server instance when storing content.

Root level to where content is being stored for this partition and is one of the arguments passed to the algorithm used by the Content Server instance to choose a storage location for content. This value can be a static string, such as C:/vault, an expression, such as $#env.VauldDir$, or an Idoc Script variable, such as $HttpWebRoot$.

Whether a partition is active (TRUE) or not (FALSE). Active partitions are available to store content.

Item action menu for each partition, from which you can choose to edit or delete the partition.

Displays the Add/Edit Partition Page, which can be used to add and activate a new partition for use by the Content Server instance.

Unique name of the partition. The partition name is displayed on the Partition Listing Page and is part of the path expression used by the Content Server instance to store content. As such, it must be unique for each partition created, and has the same character limitations as Idoc Script and HTML path expressions.

Root level of the path to where content is stored for this partition and is one of the arguments passed to the algorithm used by the Content Server instance to choose a storage location for content.

Interval used in determining the disk space available for use by this partition. Expressed in seconds. This argument may not work on all platforms.

Point at which a partition is full and can no longer accept content. If the available space on the partition is lower than the specified number of slack bytes, the partition no longer accepts new content.

How native files are treated when not converted to a web-viewable rendition. For example, many image files do not require a rendition to be web-viewable. Linking to the native file instead of copying them to the web path helps manage storage space.

copy (default): copies the native file to the web path.

link: Resolves the web path to the native file in the vault

If selected, the partition is active and available for new content.

Submits the information specified creates or updates the partition.

Resets the information to the previous state before updating the partition.

Name of the provider.

Descriptive phrase displayed on the Providers Page identifying the provider.

Path to the Java class file governing provider functionality. The default class file is BaseFileStore.

A path to a Java class file that is not applicable to the Content Server instance. Do not enter a value.

Path to the Java class file used to configure file store provider functionality.

Path to the Java class file called to access content.

Path to the Java class file called when describing content.

Path to the Java class file called when implementing an event, such as indexing or searching.

Path to the Java class file called when needing information about content.

Storage rules used for the provider. Select Add rule to create additional rules.

Displays the Storage Rule Name Dialog for adding or modifying storage rules.

If selected, content checked into the Content Server instance will be stored only on a specified file system, and not in a database. This includes both the native and web-viewable files unless the Is Webless File Store option is enabled.

If selected, content checked into the Content Server instance will be stored only in a database, and not on a file system. This includes both the native and web-viewable files unless an option is selected from the Renditions choice list.

If selected, a web-viewable rendition content will not be created.

Expands the screen to display detailed information about the metadata used for constructing paths used by the provider.

Expression defining the path to the vault location where native content checked into the Content Server server is stored for the provider using this rule.

Expression defining the path on the file system to the weblayout directory.

Expression defining the dispersion of content on the file system. $endDispMarker$ cannot be changed.

Note: If the file system has been upgraded from an earlier Content Server release, this field is blank by default to support the existing configuration. If the file system has any existing documents, it will keep dispersion blank (empty).

Expression defining the path on the file system to the web-viewable rendition. Do not edit $dispersion$ and $endDispMarker$ in this path.

Expression defining the weblayout directory and URL prefix for the root level to where content is being stored for the partition.

URL used to access the web-viewable rendition in a browser. Do not edit $dispersion$ and $endDispMarker$ in this path.

Name of a field in the current path metadata configuration.

Brief description of the function of a field.

Algorithm associated with a field.

Amount of time in minutes that the web server holds user credentials. To maintain the Content Server user credentials, you should select a finite time for the web server to cache user data.

The first time a user logs in to the Content Server instance, a cookie is sent to the filter. If you change the default authentication from the default Basic to NTLM, the first time a user logs in to the Content Server instance the user will not be prompted to log in again because their credentials will automatically be authenticated.

For optimal performance, the Content Server instance compresses the HTML response pages. This option is useful for debugging purposes.

TRUE: Prevents the Content Server instance from compressing HTML response pages.

FALSE: Configures the Content Server instance to compress HTML response pages. This is the default setting.

If selected, enables logging of high-level information that is passed through the web server filter. This is helpful in determining password and user authentication problems.

If selected, enables logging of all incoming data that is passed through the web server filter.

Enables logging of all outgoing data that is passed through the web server filter.

If selected, enables logging of events that occur inside the web server filter.

If selected, enables logging of events that occur inside any web server plug-in filters that understand this flag.

Abbreviation that is used as a filter to evaluate whether a URL should be processed using a defined mapping script.

Script used to process applicable URLs and map them to the resulting URL.

Saves the changes made in the Prefix and Map fields.

Reverts the values of the Prefix and Map fields to their previously saved settings. Any values entered but not saved are removed from the fields.

Name of the provider that establishes connection to outside entities.

Description of the provider that establishes connection to outside entities.

Type of provider: This list includes standard providers such as ServletIncomingProvider, SystemDatabase, SystemServerSocket, JpsUserProvider, and DefaultFileStore.

Possible states are:

• good

• down

• requires restart

• misconfigured

Last date and time that the provider was active.

Info: Displays the Provider Information Page for the provider.

Test: Refreshes the Connection State and Last Activity Date columns for the provider.

Type of provider:

• outgoing (see Outgoing Socket Provider Page)

• database (see Database Provider Page)

• incoming (see Incoming Provider Page)

• preview (see Preview Provider Page)

• ldapuser (see LDAP Provider Page)

• keepaliveincoming (see keepaliveincoming Provider Page)

• keepaliveoutgoing (see keepaliveoutgoing Provider Page)

• sslincoming (see sslincoming Provider Page)

• ssloutgoing (see ssloutgoing Provider Page)

• jpsuser (see JPS User Provider Page)

• httpoutgoing (see Outgoing Http Provider Page)

Description of the provider type.

Add: Displays the Add/Edit Provider Page for the provider type listed in that row.

Displays information about the provider. The information shown depends on the type of provider and the Content Server configuration. For a description of each field, see "Add/Edit Provider Page".

Displays the Add/Edit Provider Page for the provider. This button is not displayed for the default system providers.

Disables or enables the provider. The Content Server instance must be restarted after a provider is disabled or enabled.

This button is not displayed for the default system providers.

Deletes the provider. This button is not displayed for the default system providers.

Name of the provider, which will become a subdirectory in the IntradocDir/data/providers/ directory.

User-friendly description of the provider.

Name of the Java class for the provider. For example, intradoc.provider.SocketOutgoingProvider.

Name of the Java class that implements the provider connection. For example, intradoc.provider.SocketOutgoingConnection.

Name of a Java class that performs some extra configuration. This class is very useful for database providers, where the connection classes are already providers.

Server host name of the other Content Server instance.

HTTP address of the other Content Server instance. For example, intradoc:90.

Port number on which the provider communicates with the other Content Server instance.

Name (IDC_Name) of the other Content Server instance.

Relative web root of the other Content Server instance. For example, /_install_dir__instance_dir__2/.

If selected, the target server can require a password in order to connect. The target server can allow connection through either a global proxy password or it can provide "named" password connections

Name of the connection password. The name can either be a blank value (which will select the global password) or a specific name to choose one of the target's proxied connections.

Connection password.

Client IP addresses that are allowed to use the connection to the target server.

If selected, Inbound Refinery is used by this provider.

If selected, prevents the Content Server instance from sending new conversion jobs to Inbound Refinery with this provider.

Saves the provider information.

Resets the provider information to the last saved values.

Name of the provider, which will become a subdirectory in the IntradocDir/data/providers/ directory.

User-friendly description of the provider.

Name of the Java class for the provider. For example, intradoc.jdbc.JdbcWorkspace.

Name of the Java class that implements the provider connection. For example, intradoc.jdbc.JdbcConnection.

Name of a Java class that performs some extra configuration. This class is very useful for database providers, where the connection classes are already providers.

Database type. Types include ORACLE, MSSQLSERVER, DB2, SYBASE.

JDBC driver name for the database type. When the database type is selected, an appropriate driver is automatically filled.

JDBC connection string for the database type. When the database type is selected, an appropriate string is automatically filled.

If selected, specifies that the provider use a data source.

Data source.

Test query will be used to test the provider when the Test link on the Providers page is clicked. When the database type is selected, a test query is automatically filled. You can choose to enter a different test query.

Directory that contains the Content Server database information. For example, IntradocDir/database. Used only by DAO databases.

Used only by DAO databases.

Your JdbcUser.

Your JdbcPassword.

Number of database connections the provider maintains. This is used only by JDBC databases.

Extra storage keys required for the connection. A system storage key is automatically filled.

Any additional configuration settings for the database provider.

Saves the provider information.

Resets the provider information to the last saved values.

Name of the provider, which will become a subdirectory in the IntradocDir/data/providers/ directory.

User-friendly description of the provider.

Name of the Java class for the provider. For example, intradoc.provider.SocketIncomingProvider.

Name of the Java class that implements the provider connection. For example, idc.provider.SocketIncomingConnection.

Name of a Java class that performs some extra configuration. This class is very useful for database providers, where the connection classes are already providers.

Port the provider listens on for incoming connections. For example, the incoming system provider listens on port 4444 by default.

Saves the provider information.

Resets the provider information to the last saved values.

Name of the provider, which will become a subdirectory in the IntradocDir/data/providers/ directory.

User-friendly description of the provider.

Name of the Java class for the provider. For example, intradoc.provider.SocketOutgoingProvider.

Name of the Java class that implements the provider connection. For example, intradoc.provider.SocketOutgoingConnection.

Name of a Java class that performs some extra configuration. This class is very useful for database providers, where the connection classes are already providers.

Server host name of the other Content Server instance. For example, localhost.

HTTP address of the other Oracle WebCenter Content Server instance. Use the value listed for HTTP Server on the Configuration Information page. For example, intradoc:90.

Port on which the provider communicates with Oracle Content Publisher. Typically, this port is 4441.

Saves the provider information.

Resets the provider information to the last saved values.

(Required) Name of the provider.

(Required) Description of the provider.

(Required) Name of the Java class for the provider. For example: idc.provider.ExtendedSocketIncomingProvider

Name of the Java class that implements the provider connection. For example: idc.provider.KeepaliveSocketIncomingConnection

Name of a Java class that performs some extra configuration. This class is very useful for database providers, where the connection classes are already providers.

Name of the Java class for keepalive server threads. For example: idc.provider.KeepaliveIdcServerThread

(Required) Port the provider listens on for incoming connections. For example, the incoming system provider for WebCenter Content listens on port 4444 by default.

Saves the provider information.

Resets the provider information to the last saved valued.

(Required) Name of the provider.

(Required) Description of the provider.

(Required) Name of the Java class for the provider. For example: idc.provider.KeepaliveSocketOutgoingProvider

Name of the Java class that implements the provider connection. For example: idc.provider.KeepaliveSocketOutgoingConnection

Name of a Java class that performs some extra configuration.

Name of the Java class that implements the server request. For example: idc.provider.KeepaliveServerRequest

Maximum number of connections. For example, 3.

(Required) Server host name of the other Content Server instance. For example, localhost.

HTTP address of the other Content Server instance.

(Required) Port on which the provider communicates with the other Content Server instance.

(Required) Name of the other Content Server instance.

(Required) Relative web root of the other Content Server instance.

If selected, the target server can require a password in order to connect. The target server allows connection through either a global proxy password or it can provide "named" password connections.

Connection password name. The name can either be a blank value (which will select the global password) or a specific name to choose one of the target's proxied connections.

Connection password.

Possible client IP addresses who can use this connection to the target.

Options if the provider uses Inbound Refinery.

• Handles Inbound Refinery Conversion Jobs

• Inbound Refinery Read Only Mode

Number of jobs allowed in the pre-converted queue.

Saves the provider information.

Resets the provider information to the last saved values.

(Required) Name of the provider.

(Required) Description of the provider.

(Required) Name of the Java class for the provider. For example: idc.provider.ssl.SSLSocketIncomingProvider

Name of the Java class that implements the provider connection. For example: idc.provider.KeepaliveSocketIncomingConnection

Name of a Java class that performs some extra configuration. This class is very useful for database providers, where the connection classes are already providers

Name of the server thread for incoming connections. For example: idc.provider.KeepaliveIdcServerThread

(Required) Port the provider listens on for incoming connections. For example, the incoming system provider listens on port 4444 by default.

If selected, the provider requests client authentication from the incoming connection.

If selected, the provider requires client authentication from the incoming connection.

The keystore file path. To use the default keystore file path, select Use Default.

Keystore password.

Alias name.

Alias password.

Truststore file path. To use the default truststore file path, select Use Default.

Truststore password.

Saves the provider information.

Resets the provider information to the last saved values.

(Required) Name of the provider.

(Required) Description of the provider

(Required) Name of the Java class for the provider. For example: idc.provider.KeepaliveSocketOutgoingProvider

Name of the Java class that implements the provider connection. For example: idc.provider.KeepaliveSocketOutgoingConnection

Name of a Java class that performs some extra configuration.

Name of the Java class that implements the server request. For example: idc.provider.KeepaliveServerRequest

Maximum number of connections. For example, 3.

(Required) Server host name of the other Content Server instance. For example, localhost.

HTTP address of the other Content Server instance.

(Required) Port on which the provider communicates with the other Content Server instance.

(Required) Name of the other Content Server instance.

(Required) Relative web root of the other Content Server instance.

Keystore file path. To use the default keystore file path, select the Use Default checkbox.

Keystore password.

Alias name.

Alias password.

Truststore file path. To use the default truststore file path, select the Use Default checkbox.

Truststore password.

If selected, the target server requires a password to allow the connection.

The target server may provide named password connections. A blank value selects the global password. A specific name chooses one of the target's proxied connections.

Connection password.

Possible client IP addresses who can use this connection to the target. The wild card symbols * = match 0 or many and | = match either or can be used to match more then one potential client.

Options to have the provider use Inbound Refinery.

• Handles Inbound Refinery Conversion Jobs: Use only if this provider is an Inbound Refinery instance.

• Inbound Refinery Read Only Mode: Use this option to prevent this Content Server instance from sending new conversion jobs to this Inbound Refinery instance.

Saves the provider information.

Resets the provider information to the last saved values.

Name of the provider, which will become a subdirectory in the IntradocDir/data/providers/ directory.

User-friendly description of the provider.

Name of the Java class that implements the provider.

Name of the Java class that implements the connection to the LDAP server.

Name of a Java class that performs some extra configuration. This class is useful for database providers, where the connection classes are already providers.

Unique string that identifies the provider. The first time a user requests credentials through the provider, this string is stored with the user information so it can be used to match the user with the provider the next time the user asks for credentials. Try using the name of the provider as the Source Path.

Host name of the Oracle JPS server.

Select a JPS attribute to be mapped to a Content Server user information field.

Select a Content Server user information field to be mapped from the JPS attributes field.

• All Content Server user information fields for which you can change the value are listed.

• Standard user information fields begin with a "d".

• Custom user information fields begin with a "u".

Adds the JPS Attribute and User Attribute as a colon-separated clause in the Attribute Map box.

List of the Attribute Map clauses that will be used to map user attributes to Content Server information fields.

• This box can be edited directly.

• If this field is left blank, the default is:

  mail:dEmail
  cn:dFullName
  title:dUserType
  

Default role or roles assigned to a user who enters through this provider. For example, contributor or guest.

If this field is blank, the default format is to include the permissions within parenthesis after the account name. For example: @account(RW)

If this field is non-blank, it specifies an alternate delimiter that separates the account name from the permissions. For example, if the field contains $ then the delimiter appears as: @account$RW

Default network accounts accessed through this provider. The default value is #none

Prefix used for accounts accessed through this provider. The default is @ (the "at" sign).

Saves the provider information.

Resets the provider information to the last saved values.

Name of the provider.

User-friendly description of the provider.

Name of the Java class for the provider. For example: proxyconnections.HttpOutgoingProvider

Name of the Java class that implements the provider connection. For example: proxyconnections.HttpOutgoingConnection

Name of a Java class that performs some extra configuration. Leave this blank.

URL for the proxy server.

Instance name of the proxy Content Server instance.

Relative web root of the Content Server instance.

Name of a password connection (this can be an existing name or a name for a password connection that you will create on the proxy server). The name must specify one of the target master server's proxied connections. The target server requires a named password.

Password for the named password connection.

Client IP address or addresses that can use this connection to the target server.

Conversion options for Inbound Refinery. Enter the number of jobs allowed in the pre-converted queue. The default is 100.

• Handles Inbound Refinery Conversion Jobs: Select this checkbox to prevent the Content Server instance from sending new conversion jobs to this Inbound Refinery. This Inbound Refinery returns conversion jobs as the jobs are finished.

• Inbound Refinery Read Only Mode: Select this checkbox to prevent this Content Server instance from sending new conversion jobs to this Inbound Refinery.

Saves the provider information.

Resets the provider information to the last saved values.

Save Configuration: Saves the current Batch Loader settings in the DomainHome/ucm/cs/bin/intradoc.cfg file.

Build Batch File: Displays the BatchBuilder Screen.

Exit: Closes the Batch Loader screen.

Contents: Displays the Content Server online help.

About Content Server: Displays version, build, and copyright information for the Content Server instance.

Path and file name of the batch load file. If settings have not been saved to the intradoc.cfg file, the default is IntradocDir/samples/Batchloader/batchinsert.txt.

Click Browse to locate and select the batch load file.

Number of errors after which the Batch Loader stops processing records from the batch load file. The default is 50.

If you plan to run the Batch Loader with a large number of files overnight, consider increasing this number so that the process does not stop prematurely.

If you are monitoring the Batch Loader closely, consider decreasing this number so you are notified of errors as they occur.

If selected, deletes each file from the hard drive after it is successfully checked in or updated.

If selected, creates a text file containing the file records that failed during batch loading. You can fix the errors in this content and rerun it as the batch load file.

Displays the progress of the batch loading process.

Starts the batch loading process.

N/A

Save Configuration: Saves the current BatchBuilder settings in the DomainHome/ucm/cs/bin/intradoc.cfg file.

Load Batch Loader: Displays the Batch Loader Screen.

Yes

Directory that contains the content to be included in the batch load file. All files in sub-directories of this directory will also be included in the batch load file.

Yes

Path and file name of the batch load file to be created. If you enter the name of an existing file, the file will be replaced by the new batch load file.

Click Browse to locate and select the batch load file.

Yes

Mapping file to be used to specify metadata values.

Click Edit to display the BatchBuilder Mapping List Screen.

No

Files to be included or excluded from the batch load file.

If this field is blank, all files in the specified directory and sub-directories are included.

If files are specified in this field and Exclude Filter is unselected, only the specified files are included in the batch load file.

If files are specified in this field and Exclude Filter is selected, all files except the specified files are included in the batch load file.

Whole file names or file extensions can be specified.

Separate file names and extensions with a comma.

Extensions can be entered as *.ext, .ext, or ext.

N/A

Creates a batch load file using the specified parameters.

List of the available mapping files.

Short description of each mapping file.

Displays the Add BatchBuilder Mapping Screen.

Displays the Edit BatchBuilder Mapping Screen.

Deletes the selected mapping file.

Closes the BatchBuilder Mapping List screen.

Unique name for the mapping file. Maximum field length is 30 characters. The following are not acceptable: spaces, tabs, linefeeds, carriage returns, and ; ^ ? : @ & + " # % < * ~ |

Short description of the mapping file.

Displays the Edit BatchBuilder Mapping Screen.

Closes the Add BatchBuilder Mapping screen without creating a new mapping file.

Short description of the mapping file.

List of metadata fields that have values defined in the mapping file.

Values that will be assigned to the metadata fields in the batch load file.

Displays the Add/Edit BatchBuilder Mapping Field Screen.

Displays the Add/Edit BatchBuilder Mapping Field Screen.

Deletes the selected metadata field from the mapping file.

Saves the current settings in the mapping file.

Closes the Edit BatchBuilder Mapping screen without applying any changes.

Name of the metadata field to be defined, such as dDocType or xComments.

Value to be used in the batch load file. You can type directly in this field or insert predefined variables from the column to the right.

Inserts the variable selected from the right column into the Value field.

List of predefined variables you can use as values in the batch load file.

Applies the field and value settings to the mapping file.

Closes the Add/Edit BatchBuilder Mapping Field screen without applying any changes.

Performs all checks on the database, ensures the integrity of the database columns, and confirms the consistency of data between the DocMeta, Revision, and Documents tables.

Ensures the accurate data synchronization between the dRevClassID and dDocName tables.

Removes inconsistent rows from the database. Extra entries in the DocMeta table are deleted, inadequately defined entries in the Document table are deleted, and entries without a corresponding reference in the Revisions table are deleted.

Analyzes the search index to ensure its integrity and checks for duplicate data records for indexed documents and any documents that might be missing from the search collection.

Re-indexes the search index and replaces missing data records of any omitted documents.

Analyzes the file system (weblayout and vault file repositories) to ensure all necessary files are present.

Permanently deletes extra files that were found during the file system analysis.

Creates a safe delete directory in the logs/ directory and copies the extra files that were found during the file system analysis into this directory.

Identifies any possible extra files that might be in the file system.

Uses the console window to report statistics about the content items in the repository. It includes information pertaining to the status, release and processing states of content items in the file system and provides prior and current totals. Progress and error messages are also logged to the console window.

Range (first and last) of the criteria to analyze.

Default directory used by Content Server Analyzer is DomainHome/ucm/cs/bin/logs/. Optionally, you can also enter a custom directory name. If the Safe delete option is selected, the files are moved to this directory.

Starts analyzing Content Server integrity.

Displays the combined progress of the specific analysis tasks selected on the Configuration tab.

Displays the overall progress of the analysis process.

Area that displays the information collected and summarized during the analysis processes. Displays applicable information for each selected option. Also displays progress and error messages generated during the analysis processes.

Starts the Content Server analysis.

Displays the type of log file entry:

• Info: Displays basic status information.

• Error: Displays errors that occur but do not stop the software from functioning.

• Fatal: Displays errors that stop the software from functioning.

Displays the date and time of the log file entry.

Displays information about the log file entry. The level of detail depends on the type of entry.

Displays the type of log file entry:

• Info: Displays basic status information.

• Error: Displays errors that occur but do not stop the software from functioning.

• Fatal: Displays errors that stop the software from functioning.

Displays the date and time of the log file entry.

Displays information about the log file entry. The level of detail depends on the type of entry.

Displays the type of log file entry:

• Info: Displays basic status information.

• Error: Displays errors that occur but do not stop the software from functioning.

• Fatal: Displays errors that stop the software from functioning.

Displays the date and time of the log file entry.

Displays information about the log file entry. For more information, click Details.

If selected, includes Unix 'etc' log directory information in the zip file.

If selected, includes the server data State directory information in the zip file.

If selected, includes the search engine State directory information in the zip file.

If selected, includes the schema resources directory information in the zip file.

If selected, includes Content Server log information in the zip file.

If selected, includes Archiver log information in the zip file.

If selected, includes Verity log information in the zip file.

If selected, includes database log information in the zip file.

All Files: includes the custom component directory in the zip file.

Digests Only: includes just the digests for the custom component directory in the zip file.

All Files: includes all Classes directory files in the zip file.

Digests Only: includes just the digests for the classes directory in the zip file.

All Files: includes all weblayout common directory for applets files in the zip file.

Digests Only: includes just the digests for the weblayout common directory for apples files in the zip file.

All Files: include Layout and Skin Web resources in the zip file.

Digests Only: includes just the digests for layout and skin Web resources in the zip file.

All Files: includes wwResourcesDir in the zip file.

Digests Only: includes just the digests for wwResourcesDir in the zip file.

Starts the environment packaging process for the selected items.

Resets the selected items to their default settings.

Tracing: Opens the Tracing Configuration screen, from which you can perform features related to system-wide tracing.

Exit: Closes the User Admin application.

Displays options to set:

Permissions by Group: Displays the Permissions By Group Screen.

Permissions by Role: Displays the Permissions By Role Screen.

Predefined Accounts: Displays the Predefined Accounts Screen. This option is available only if accounts are enabled.

Used to open other administration applications. The other applications open in the same mode (applet or standalone) as the current application.

Contents: Displays the Content Server online help.

About Content Server: Displays version, build, and copyright information for the Content Server instance.

Used to add, edit, and delete user logins. See User Admin Screen: Users Tab.

Used to add, edit, and delete user aliases. See User Admin Screen: Aliases Tab.

Used to add, edit, and delete user information fields. See User Admin Screen: Information Fields Tab.

Select one or more checkboxes to activate the filter fields.

The Users list on the original screen will be filtered based on the criteria entered in the fields for selected checkboxes. The following wildcards can be used in these fields:

• With MS Access or MSDE:

  * = one or more characters

  ? = single character

• With all other databases:

  % = one or more characters

  _ = single character

User login.

Full name that corresponds to the user login.

Attribute defined by the system administrator as a way to classify users.

User authorization type, either Local, Global or External.

E-mail address associated with the user. This is used for workflow and subscription notifications.

User's locale, which specifies the language of the user interface and date/time format.

User's Organization Path value, which can be defined by the system administrator as a way of classifying global users.

LDAP user provider used to retrieve user information. Also, this field specifies if the user came from a NTLM or ADSI integration with the value: MSN.

Any custom user information fields will be available as filter fields.

If selected, the field is displayed in the Users list on the original screen.

If unselected, the field is not displayed on the Users list.

For field descriptions, see the Define Filter Screen.

If selected, the column settings are applied every time the original screen is displayed.

If unselected, the column settings apply only until the original screen is closed.

List of existing security groups

List of the roles associated with existing security groups.

Enables you to edit permissions for a security group and role.

This button is available when you select a group and role.

Displays the Add New Group Screen.

Enables you to delete an existing security group. (You will not be able to delete a security group if content still exists in that security group.)

Name of the new security group.

• The Group Name is limited to 30 characters.

• The following characters are not allowed: spaces, tabs, linefeeds, returns, and ; : ^ ? & + " # % < * ~ |

• Uppercase accented letters are not allowed; lowercase accented letters are acceptable. (For example, Älvdalsån will not work, but älvdalsån will.)

Brief description of the security group.

• The Description is limited to 80 characters.

• This field is displayed only in the User Admin Screen.

List of existing roles.

List of the security groups and the rights associated with the selected role.

Enables you to edit permissions for a security group and role.

This button is available when you select a role and a group/right.

Enables you to edit rights for the role. This button is available when you select a role.

Displays the Add New Role Screen, on which you can set up a new role for users. Add the role name, and click OK.

Enables you to delete the selected role. (You will not be able to delete a role if any users are assigned to that role.)

Name of new role.

• The Role Name is limited to 255 characters.

• The following characters are not allowed: spaces, tabs, linefeeds, returns, and ; : ^ ? & + " # % < * ~ |

• Initially, a role is assigned Read (R) permission to the Public security group and no permissions to any other security groups.

If selected, allows users to view files.

If selected, allows users to view, check in, check out, and obtain a copy of files.

If selected, allows users to view, check in, check out, get a copy, and delete files.

If selected, allows users to view, check in, check out, get a copy, and delete files, and check in files for other users. In addition, if the user has Workflow rights, they can start or edit a workflow.

List of the predefined accounts.

Displays the Add New Predefined Account Screen.

Deletes the selected account.

You can delete an account even if content with that account still exists. The account value will remain assigned to the content item, but will be considered a user-defined account.

Name of the account to be added. Keep the names short and consistent. For example, set up all of your accounts with a three-letter abbreviation by location or department (MSP, NYC, and so on). Account names can be no longer than 30 characters, and the following are not acceptable: spaces, tabs, linefeeds, carriage returns, and the symbols: ; ^ ? : & + " # % < > * ~.

Select a predefined account from the list, or enter a user-defined account.

Select one or more Predefined Permissions that a user will have to access the account.

• Read

• Write

• Delete

• Admin

If selected, narrows the Users list as defined by the Define Filter Screen.

Displays the Define Filter Screen.

Displays the Show Columns Screen.

List of the users that match the filter settings. Double-clicking a user name displays the Add/Edit User Screen for that user.

Displays the Choose/Change the Authorization Type Screen.

If you highlight a user and click this button, the system displays the Add/Edit User Screen with some fields already populated.

Displays the Add/Edit User Screen for the selected user.

Displays the Choose/Change the Authorization Type Screen for the selected user.

Enables you to delete a user login.

Type of user.

Local: Users defined by an administrator within the Content Server instance. Administrators assign these users one or more roles, which provide the user with access to security groups. Undefined users are assigned the guest role.

Global: Lightly managed users. Both local and global user credentials can extend to multiple Content Server instances.

Displays the Add/Edit User Screen: Info Tab (Local User) or the Add/Edit User Screen: Info Tab (Global User), depending on which Authorization Type is selected.

Name of the new user.

• This field has a 50-character limit.

• User names are case-sensitive.

Entire name of the new user. This field has a 50-character limit.

Password for the new user login.

• This field has a 50-character limit.

• Passwords are case-sensitive.

Re-enter the password from the previous field to confirm the spelling.

E-mail address associated with the user. This is used for workflow and subscription notifications.

Select a user type from the list of attributes which can be defined by the system administrator as a way to classify users.

List: Displays the Option List Screen.

User's locale, which specifies the language of the user interface and date/time format. Locale options must be enabled by the system administrator.

If you change the user locale for a user who has the sysmanager role, you must restart the Admin Server service for the Admin Server interface to appear in the user's locale language.

Select a time zone for the user.

Name of the new user. This field has a 50-character limit.

Select from a list that can be defined by the system administrator as a way of classifying users.

List: Displays the Option List Screen.

Password for the new user login. This field has a 50-character limit.

Re-enter the password from the previous field to confirm the spelling. The same limit applies.

Entire name of the new user. This field has a 50-character limit.

E-mail address associated with the user. This is used for workflows and subscriptions.

Select from a list of attributes that can be defined by the system administrator as a way to classify users.

List: Displays the Option List Screen.

User's locale, which specifies the language of the user interface and date/time format. Locale options must be enabled by the system administrator.

If you change the user locale for a user who has the sysmanager role, you must restart the Admin Server service for the Admin Server interface to appear in the user's locale language.

Select a time zone for the user.

These settings apply only if the user is changed from a global user to an external user, or if user information is automatically assigned by a custom plug-in to the Content Server instance.

If selected, the user information assigned in the Add/Edit User screen overrides any externally assigned user information (such as user attributes from a LDAP server).

If unselected, the user information assigned in the Content Server instance is overridden by any externally assigned user information.

List of existing roles.

List of the security group permissions associated with the selected role.

Displays the Add Role Screen, on which you can select a role from a drop-down list.

Removes the selected role from the user login.

Select a role from the list to assign to the user.

List of the accounts that are assigned to this user login. By default, all new users are assigned Read, Write, Delete, and Admin permission to documents that are not in an account.

Displays the Add/Edit Account Permissions Screen.

Displays the Add/Edit Account Permissions Screen.

Deletes the selected account.

Select the account that will be entered as the default value on the Content Check In Form page for this user. All accounts for which the user has at least RW permission are available on the list.

Enter the values that can be selected for the User Type or Organization Path. Each value must be on a separate line, with a carriage return between values.

If selected, sorts the list in alphabetical order.

If selected, sorts the list in reverse alphabetical order.

If selected, sorts the list in alphabetical order, regardless of case.

If unselected, values that start with uppercase letters are grouped separately from values that start with lowercase letters.

Sorts the list in the manner specified by the Ascending, Descending, and Ignore Case options.

Lists the alias names.

Description of each alias.

Displays the Add New Alias/Edit Alias Screen.

Displays the Add New Alias/Edit Alias Screen.

Enables you to delete the selected alias.

The alias name is limited to 30 characters. The following are not allowed: spaces, tabs, line feeds, returns and ; : ^ ? @ & + " # % < * ~ |

Name of the alias that appears on a display.

Maximum 80 characters.

List of the user logins that are included in the alias.

Displays the Select Users Screen.

Deletes the selected user login from the alias.

If selected, this checkbox narrows the Users list as defined by the Choose/Change the Authorization Type Screen.

Displays the Choose/Change the Authorization Type Screen.

Displays the Show Columns Screen.

List of users that match the filter settings. For column descriptions, see the Choose/Change the Authorization Type Screen.

Assigns sub-administration rights to the User Admin application.

Assigns sub-administration rights to the Web Layout Editor application.

Assigns sub-administration rights to the Repository Manager application.

Assigns sub-administration rights to the Workflow Admin application.

Moves the selected user information field up in the list.

Moves the selected user information field down in the list.

Name of the user information field.

No: Indicates a system (predefined) user information field.

Yes: Indicates a custom user information field.

Type of field:

Text: 30 characters.

Long Text: 200 characters.

Date: Date format (such as dd/mm/yyyy or dd/mm/yy for the English-US locale).

Memo: 255 characters.

Integer: -231 to 2 31 (-2 billion to +2 billion). By definition, an integer is a natural number, so decimal values and commas are not permitted.

Field label that appears on Content Server pages.

False: The user information field does not have an option list.

True: The user information field has an option list.

Displays the Add Metadata Field Name Screen, on which you can add a new field name.

Displays the Edit Metadata Field Screen.

Deletes the selected custom user information field. (System user information fields cannot be deleted.)

Displays the Update Database Design Screen.

Duplicate names are not allowed. Maximum field length is 29 characters. The following are not acceptable: spaces, tabs, line feeds, carriage returns and ; ^ ? : @ & + " # % < * ~ |

When you add a custom user information field, the system automatically prefixes the name with a "u" to ensure that it is unique and does not conflict with any reserved names. However, you must be careful not to inadvertently use restricted names for columns in the user logins table because they may conflict with reserved names in databases.

For example, if you try to use "ID" to name a new custom user information field, the result will be "UID" when the system adds the prefix. This causes an error because UID is a reserved database name.

Similarly, when you define a custom metadata field, the system automatically prefixes the name with a "x" to ensure that it is unique and does not conflict with any reserved names.

Displays the Edit Metadata Field Screen.

Label for the field that is displayed on Content Server pages.

Text: 30 characters.

Long Text: 100 characters.

Date: Date format (such as dd/mm/yyyy or dd/mm/yy for the English-US locale).

Memo: 255 characters.

Integer: -2³¹ to 2³¹ (-2 billion to +2 billion). By definition, an integer is a natural number, so decimal values and commas are not permitted.

For internal use.

If selected, the field is not displayed on the User Profile pages. However, the field is visible to an admin user through the User Admin applet.

If unselected, the field is displayed on the User Profile page.

If selected, the field is displayed on the User Profile page, but cannot be edited by the user.

If the Administrator Only Edit checkbox is unselected, the View Only field can be edited by the user on the User Profile page.

If selected, the field has an option list that is defined by the Option List Type and Option List Key. Values shown in the Information Fields tab Is Option List are True or False.

The user information fields that were added since the last time the database was updated.

List of user information fields that were changed since the last time the database was updated. Select the checkboxes for the fields to delete.

If selected, the user information fields will be deleted from the database.

If unselected, the user information field will not be deleted from the database. The field remains hidden on the User Admin screen and User Profile pages, but it still exists in the database.

Adds the listed user information fields and deletes the selected user information fields.

Enter the unique identifier for the credentials map.

Enter the credential values in two columns with a comma used as a separator between the columns, and a carriage return between rows. The first column specifies input values. The second column specifies output values.

Inputs the credential values specified in the Credential Maps page.

Name given to the proxied connection.

Brief description of the proxied connection.

Password assigned to the proxied connection.

Password assigned to the proxied connection.

IP address number of the client Content Server instance.

HTTP IP address filter, applied to the IP address of the client Content Server instance.

Updates the page with any modified information.