Oracle Business Intelligence Infrastructure Installation and Configuration Guide > Configuring Oracle Business Intelligence Scheduler > Configuring Oracle BI Presentation Services to Communicate With Oracle BI Scheduler >

Adding Scheduler Administrator Credentials to Oracle BI Presentation Services Credential Store

This topic is part of Configuring Oracle BI Presentation Services to Communicate With Oracle BI Scheduler.

Oracle BI Presentation Services must be able to identify the Scheduler administrator and obtain the credentials to establish a connection with the Scheduler. Presentation Services stores the credentials that it uses in a Presentation Services Credential Store. The Scheduler administrator credentials must be added to the credential store, under the alias admin. To obtain the Scheduler Administrator credentials, Oracle BI Presentation Services searches the credential store for a username-password credential with the alias admin. For more information on the Presentation Services Credential Store, refer to the Oracle Business Intelligence Enterprise Edition Deployment Guide.

Use the following procedure to add the Scheduler administrator credentials to the Presentation Services Credential Store with the admin alias. This procedure adds the Scheduler administrator credentials to a proprietary XML file credential store called credentialstore.xml. The default location of this file is OracleBIData_HOME\web\config on Windows and OracleBIData_HOME/web/config on Linux.

To add Scheduler administrator credentials to the credential store

1. Open a command prompt window or command shell on the machine where Oracle BI Presentation Services has been installed.
2. Navigate to the directory OracleBI_HOME\web\bin on Windows. On Linux, navigate to OracleBI_HOME/web/bin.
3. Execute the CryptoTools utility to add the Scheduler Administrator credentials to the Presentation Services Credential Store:

   cryptotools credstore -add -infile OracleBIData_HOME/web/config/credentialstore.xml

   For more information on the CryptoTools utility, its syntax and supported sub-commands, refer to the Oracle Business Intelligence Enterprise Edition Deployment Guide.

4. Supply values for the prompted parameters, as shown in the following table.

   CryptoTools Prompt	Value or Input	Description
   Credential Alias	admin	Specify the value admin. Presentation Services uses this alias to identify the username-password credential for the Scheduler administrator.
   Username	(Username of Scheduler administrator)	Username of the Scheduler administrator. For example, SchedulerAdmin. For information on the Scheduler administrator, see the topic About the Oracle BI Scheduler Administrator.
   Password	(Password for the Scheduler administrator)	Password of the Scheduler administrator. For example, SchedulerAdmin.
   Do you want to encrypt the password?	y or n	Choosing Y encrypts the above password.
   Passphrase for encryption	(passphrase)	Provide a passphrase that is used to encrypt the password. For example, secret.
   Do you want to write the passphrase to the xml?	y or n	Choosing Y writes the passphrase that is needed to decode the password in the xml file. For enhanced security, choose N. The passphrase is not written to the xml file. Instead, you must specify the passphrase in the instanceconfig.xml file.

The following is an example of the procedure to add the Scheduler administrator credentials to the Presentation Services Credential Store.

cryptotools credstore -add -infile OracleBIData_HOME/web/config/credentialstore.xml

>Credential Alias: admin
>Username: SchedulerAdmin
>Password: SchedulerAdmin
>Do you want to encrypt the password? y/n (y):
>Passphrase for encryption: secret
>Do you want to write the passphrase to the xml? y/n (n):
>File "OracleBIData_HOME/web/config/credentialstore.xml" exists. Do you want to overwrite it? y/n (y):

The CryptoTools utility updates the credentialstore.xml file, located in the directory OracleBIData_HOME\web\config. (The directory structure is the same on Linux systems.)

After executing the CryptoTools utility with the example inputs, the credentialstore.xml file contains entries similar to the following example:

<sawcs:credential type="usernamePassword" alias="admin">
<sawcs:username>SchedulerAdmin</sawcs:username>

<sawcs:password passphrase="secret">
<xenc:EncryptedData>
<xenc:EncryptionMethod Algorithm="http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbes2">
<pkcs-5:PBES2-params Algorithm="http://www.rsasecurity.com/rsalabs/pkcs/schemas/pkcs-5#pbkdf2">
<pkcs-5:KeyDerivationFunc>

<pkcs-5:Parameters>
<pkcs-5:IterationCount>1024</pkcs-5:IterationCount>
</pkcs-5:Parameters>
</pkcs-5:KeyDerivationFunc>
<pkcs-5:EncryptionScheme Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
</pkcs-5:PBES2-params>

</xenc:EncryptionMethod>
<xenc:CipherData>
<xenc:CipherValue>jeThdk8ZklnTlyKIat8Dkw</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>

</sawcs:password>

</sawcs:credential>