19 Important Notes

During Oracle Access Manager 10g (10.1.4.0.1) installation you may be directed to this appendix for some important notes. Topics include:

Enabling Java and JavaScript On The Client
Changing MIME Type Settings
Choosing a Unique ID for Each User
Contacting Oracle

19.1 Enabling Java and JavaScript On The Client

Oracle Access Manager components make extensive use of Java and JavaScript. To ensure that Oracle Access Manager works properly, both Java and JavaScript must be enabled in the browser.

To enable Java and JavaScript on the client

Enable Java in your browser using specific instructions from your browser vendor.
Enable JavaScript in your browser using specific instructions from your browser vendor.

19.2 Changing MIME Type Settings

Oracle Access Manager components allow users to publish and share files of any type of ASCII or binary files (.doc, .txt, .gif, and so on). For a user to view these files using appropriate products, the server must map each file to the corresponding MIME type. Oracle ships a set of MIME type mappings for most popular file formats in the following file:s:

IdentityServer_install_dir\identity\oblix\apps\admin\bin\mime_types.lst
IdentityServer_install_dir\identity\oblix\apps\admin\bin\mime_types.xml

WebPass_install_dir\identity\oblix\apps\admin\bin\mime_types.lst
WebPass_install_dir\identity\oblix\apps\admin\bin\mime_types.xml

The .xml version of the file is used by the Identity Server. The .lst version of the file is used by the WebPass Java applet. Both versions of the file must match. Both versions of the file must reside in the IdentityServer_install_dir and in the WebPass_install_dir.

Since most of the popular file types are already included in the mime_types.lst file, you should not need to modify the file. However, if you do need to modify mime_types.lst, be sure to use the instructions that follow.

To edit mime_types files

Locate the following file and open it with a text editor:

IdentityServer_install_dir\identity\oblix\apps\admin\bin\mime_types.lst
Add your new mapping (ensure that each line contains only one mapping and that your MIME type and extension are separated by a ':'), then save the file. For example:
```
image/gif:gif
```
Locate and open the following file with a text editor:

IdentityServer_install_dir\identity\oblix\apps\admin\bin\mime_types.xml
Add your new mapping (ensure that each line contains only one mapping and that your MIME type is expressed as shown), then save the file. For example:
```
<NameValPair ParamName="image/gif" Value="gif" />
```
Copy the two files into your WebPass installation directory. For example:

From:

IdentityServer_install_dir\identity\oblix\apps\admin\bin\mime_types.lst
IdentityServer_install_dir\identity\oblix\apps\admin\bin\mime_types.xml

To:

WebPass_install_dir\identity\oblix\apps\admin\bin\mime_types.lst
WebPass_install_dir\identity\oblix\apps\admin\bin\mime_types.xml

19.3 Choosing a Unique ID for Each User

Each Oracle Access Manager user must have a unique identifier (separate from the login or account name). Typically, the unique identifier will be the Employee Number, or Social Security Number, or some other type of identifier.

There are no particular restrictions on the unique ID. It does not need to be a numeric value, for example. However, choose the unique ID carefully. Not only does the system require this ID to be embedded in the data files, it also expects all users to know their ID.

19.4 Contacting Oracle

There are several ways to get in touch with Oracle.

For information:

http://www.oracle.com/corporate/contact/index.html

For Support Services:

http://www.oracle.com/support/contact.html

For the latest support information, see details under the Certify tab on:

http://www.metalink.oracle.com

Log in to MetaLink.
Click the Certify tab.
Click View Certifications by Product.
Select the Application Server option and click Submit.
Choose Oracle Application Server and click Submit.