For Imaging and WebCenter Content Dynamic Converter to work best on a UNIX operating system, you can set up TrueType fonts on the machine where Imaging, Inbound Refinery, or the Dynamic Converter is running. If these fonts are not available on your system, you need to install them. Inbound Refinery and Content Server default to the TrueType fonts in the JRE, at JAVA_HOME/lib/fonts.

1. Sign in to Inbound Refinery.
2. Select Conversion Settings, then Third-Party Application Settings, and then General OutsideIn Filter Options.
3. Click Options
4. Enter the path to the TrueType fonts in the Path to fonts field. For example, /usr/share/x11/fonts/FTP
5. Click Update.

For languages other than English, the following installation steps need to be done on a UNIX operating system before you start a Managed Server:

You can reassociate the identity store for an Oracle WebLogic Server domain with Oracle Internet Directory and migrate users from the embedded LDAP directory to Oracle Internet Directory. The following procedure describes how to reassociate the identity store with Oracle Internet Directory.

1. Ensure that there is no user in Oracle Internet Directory with the same name as the administrator of the Oracle WebLogic Server domain, which is weblogic by default.
2. Set the embedded LDAP provider to SUFFICIENT.
3. Configure the Oracle Internet Directory authentication provider:
   1. Start the Administration Server for your Oracle WebLogic Server domain.
   2. Sign in to the Oracle WebLogic Server Administration Console as the domain administrator user, at this URL: http://adminServerHost:adminServerPort/console
   3. Under Domain Structure on the left, select Security Realms.
   4. In the Realms table on the Summary of Security Realms page, click myrealm in the Name column to open the Settings for myrealm page.
   5. Click the Providers tab, and then click New under the Authentication Providers table on the Authentication tab.
   6. In the Create a new Authentication Provider dialog box, enter a provider name in the Name field, change the type to OracleInternetDirectoryAuthenticator, and then click OK.
   7. In the Authentication Providers table, click Reorder, move the provider you just created to the top of the list, and then click OK
   8. Click DefaultAuthenticator, change the Control Flag value to OPTIONAL, and then click Save
   9. Click Providers in the breadcrumb trail along the top of the page to navigate back to the Providers tab.
   10. Click the name of the authentication provider you just created to navigate to the Configuration tab for the provider. On the Common tab, change the Control Flag value to SUFFICIENT, and then click Save.
       SUFFICIENT means that if a user can be authenticated against Oracle Internet Directory, no further authentication is processed.
       REQUIRED means that the authentication provider must succeed even if another provider already authenticated the user. If the embedded LDAP has been set to OPTIONAL and Oracle Internet Directory has been set to REQUIRED, the embedded LDAP user is no longer valid.
   11. Click the Provider Specific tab. Set Provider Specific values in the following fields, and leave default values in the other fields:
       - Host: The host name or IP address of the LDAP server.
       - Port: The Oracle Internet Directory Port, 389 by default.
       - Principal: The Distinguished Name (DN) of the LDAP user that Oracle WebLogic Server should use to connect to the LDAP server; for example cn=orcladmin
       - Credential: The credential used to connect to the LDAP server (usually a password)
       - Confirm Credential: The same value as for the Credential field.
       - User Base DN: The base distinguished name (DN) of the tree in the LDAP directory that contains users; for example cn=users,dc=example,dc=com. In Oracle Internet Directory, this is the value of the User Search Base attribute, which you can look up in the OIDDAS administration dialog.
       - Use Retrieved User Name as Principal: Specifies whether or not the user name retrieved from the LDAP server should be used as the Principal value.
       — Group Base DN: The base distinguished name (DN) of the tree in the LDAP directory that contains groups; for example: cn=groups,dc=example,dc=com. In Oracle Internet Directory, this is the value of the Group Search Base attribute, which you can look up in the OIDDAS administration dialog.
       Note: Use an exact DN rather than a top-level DN. Using a top-level DN would provide access to all the default users and groups under the DN, giving access to more users than required by the application.
       - Propagate Cause For Login Exception: Propagates exceptions thrown by Oracle Internet Directory, like password expired exceptions, to Oracle WebLogic Server so they show in the console and the logs.
   12. Click Save.
4. Restart the Administration Server.
   Note: Authentication providers in an Oracle WebLogic Server domain are chained. This means that user authentication needs to run successfully through all authentication providers. With the Control Flag value set to OPTIONAL for the default provider, it is allowed to fail without a server startup or user authentication failure.
5. After the server is up again, sign in to the Administration Console again, and click Security Realms under Domain Structure.
6. In the Realms table on the Summary of Security Realms page, click myrealm in the Name column to open the Settings for myrealm page.
7. Click the Users and Groups tab to see a list of users contained in the configured authentication providers, on the Users subtab, and then click the Groups subtab to see a list of groups. You should see user names from the Oracle Internet Directory configuration, which implicitly verifies that the configuration is working
8. Check that you have switched the security provider successfully.

You might want to use an external data source so you can put the search engine on another system or in another database. Before you can use an external data source with OracleTextSearch, you need to create a search schema in a database other than the system database and configure the data source.

1. Run RCU to create a search schema (prefix_OCSSEARCH in the database where you want the search engine,
2. Create a JDBC data source that points to the search schema. You can use the Administration Console, WebLogic Scripting Tool Command, or Fusion Middleware Control to create a data source.
3. Use the Administration Console to target the data source to the WebCenter Content Managed Server (UCM_server1 by default).

If you did not configure OracleTextSearch on the configuration page for Content Server or you want to change the configuration, you can configure this search option in the DomainHome/ucm/cs/config/config.cfg configuration file for the Content Server instance.

1. Open the DomainHome/ucm/cs/config/config.cfg file for the Content Server instance in a text editor.
2. Set the following values:

   SearchIndexerEngineName=OracleTextSearch
   
   IndexerDatabaseProviderName=SystemDatabase

   Note:

   • You can specify a separate Oracle Database as the value of IndexerDatabaseProviderName, instead of SystemDatabase. The driver jar ojdbc6.jar is provided by Oracle in the MW_HOME/wlserver_10.3/server/lib directory. Before Oracle Text Search can function properly with the separate Oracle Database, however, you need to manually copy the ojdbc6.jar file from the MW_HOME/wlserver_10.3/server/lib directory to the DomainHome/lib directory.

   • OracleTextSearch requires a JDBC driver version of 10.2.0.4 or higher. The component will not work with older JDBC driver versions.

3. Save the file.
4. Restart Content Server.
5. Rebuild the search index using the Indexer tab of the Repository Manager, located under Administration, in Admin Applets.

You can use several command-line parameters to automate part of the installation process. If you need to pass any public property to MSI through desktop_content_setup.exe, you can do that with the following command:

The Desktop installer provides a number of command-line options to disable specific software integrations. If the installer detects that an integration can be applied to existing software on the computer (Microsoft Word, PowerPoint, Excel, and so on), it usually will automatically attempt to install an integration. To prevent an integration from being installed for a specific software product, you can disable that integration using one of these command-line switches:

The Desktop installer enables an administrator to roll out the Desktop client software to multiple client machines with the help of third-party tools such as SMS or netOctopus, which are capable of executing one executable on many machines. The installer for the Desktop client software supports a silent installation option that you can configure with SMS.

desktop_content_setup.exe /s UI=user_interface_level

desktop_content_setup.exe /s UI=1 /msi OUTLOOK=0 POWERPOINT=0 NOTES=0

desktop_content_setup.exe /s UI=2 /msi OUTLOOK=0 
POWERPOINT=0 NOTES=0 REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable

msiexec

start /wait msiexec /i contentdesktop_x64.msi OUTLOOK=0 WORD=0 EXCEL=0 
POWERPOINT=0 NOTES=0 REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /l*v DISUpgrade_x64.log /qn

You can add Content Server connections by creating a registry file on a Windows system. The file is not included as part of the standard installation files; you must create it.

REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\WebCenter Desktop\Content\WebDAV\Servers\Corporate]
"ServerType"="ucm"
"ServerURL"="http://corporate/cs/idcplg/webdav"

[HKEY_LOCAL_MACHINE\Software\ORACLE\WebCenter Desktop\Content\Shared\Config\Corporate]
"HostCgiUrl"="http://corporate/cs/idcplg"
"ServerAuth"=REG_DWORD:0x00000000 (0) 
"RememberMetaData"=REG_DWORD:0x00000000 (0)

[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\WebCenter Desktop\Content\WebDAV\Servers\Department]
"ServerType"="dav"
"ServerURL"="http://corporate/content/app/explorerPage.jspx"
"Single Sign-On Url"="http://section/content/app/explorerPage.jspx"
"Use Single Sign-On"=REG_DWORD:0x00000001 (1)

[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\WebCenter Desktop\Content\WebDAV\Servers\Section]
"ServerType"="cdb"
"ServerURL"="http://section/content/dav"
"Single Sign-On Url"="http://section/content/app/explorerPage.jspx"
"Use Single Sign-On"=REG_DWORD:0x00000001 (1)