Make sure that the Oracle users you use for this step meet the required configuration and that you follow these instructions closely. Using Oracle users that do not meet
the required configuration or choosing the wrong values during setup can lead to unrecoverable
errors in configuration or even data loss on upgrade!
-
In the Database Server section, provide location and name information for the database.
-
Server Type - The database type: Oracle.
-
Server Name - The name of the database server.
-
Port - The port on the database server used to connect to the database. If left blank, the default port is used (1521).
-
Service Name - The SERVICE_NAME that identifies the database on the server.
For Oracle 12c (or later), the service you specify depends on whether you are using a CDB (container database) configuration:
-
For a CDB configuration - Specify the service name for a pluggable database running in the container.
-
For a non-CDB configuration - Simply enter the service name for the database.
If the Oracle database instance has been created with a domain_name (or db_domain), the corresponding SERVICE_NAME includes the domain. For example, a database instance named SAM with a domain_name of acme.com results in the service name SAM.acme.com.
You can use the lsnrctl status command on the Oracle server to verify service names.
-
-
-
In the System Administrator Account section, choose the kind of credentials you configured as the Oracle administrator user. These credentials are used to create or modify the database structure or schema.
These credentials must meet the requirements of the Oracle administrator user, as
defined in Configure Oracle users.
-
Use Windows authentication - The Configuration Utility will connect to the database using your current Windows credentials. This is uncommon.
-
Use user name / password - The Configuration Utility will connect to the database using an Oracle administrator user.
-
-
Click Test to ensure the connection is successful with the provided credentials.
-
In the Runtime Account section, choose the Use user name / password option and provide credentials for the sam user. These credentials are used by the Configuration Utility, and later by Smart API Manager itself, to connect to the database.
These credentials must meet the requirements for the runtime user (sam), as defined in Configure Oracle users.
-
Click Test to ensure the connection is successful with the provided credentials.
-
Click Next, and continue with Step 4: Runtime configuration.