3.5.1 Signing On to Your Content Provider Database

To sign on to your content provider database:

1. Open your browser.

2. Enter the URL for the content provider database.

   The URL uses the format http://<localhost>/<pshome>/signon.html.

   • Replace <localhost> with the hostname of the web server machine where the content provider database web server files are installed.

     Note:

     If the web server for the content provider database is using an Authentication Token Domain, then the localhost value must include the network domain name in the URL. If the web server for the content provider database is using an HTTP port other than the default port of 80, then the localhost value must contain the port number in the URL.

     For example, if the URL address is http://myserver/pshome/signon.html, then use the following URL address:

     http://myserver.mydomain.com/pshome/signon.htm

     If the URL address is http://myserver:8080/pshome/signon.html, then use the following URL address:

     http://myserver.mydomain.com:8080/pshome/signon.html

   • Replace <pshome> with the site name of the PeopleSoft content provider database web server files. The default value is ps for PeopleSoft PeopleTools 8.5x databases.

3. Enter the superuser user ID and user password values on the sign-on screen. For example, VP1/VP1.

   For PeopleSoft 8.5x databases, the database home page that displays the Menu pagelet appears.

Trusting the PeopleSoft Portal Solutions database default local node involves the following set of subtasks:

For PeopleSoft Single Sign-On to work, each content provider database must list the PeopleSoft Portal Solutions database default local node as trusted.

Note:

If your content provider database contains content that is to be used by multiple PeopleSoft Portal Solutions databases, the following subtasks can be repeated for each additional PeopleSoft Portal Solutions database default local node.

For example, if you have installed an EMPLOYEE portal and a SUPPLIER portal in two separate PeopleSoft Portal Solutions database instances, you may want to access a single PeopleSoft Financials and Supply Chain Management database from both of the PeopleSoft Portal Solutions database instances.

If you renamed the default local node in the PeopleSoft Portal Solutions database, you must also rename the default local node in the content provider database.

See Renaming the Default Local Node in a Content Provider, in this installation guide.

Message nodes that are actively being used (contain queued messages) cannot be renamed until the message queues are cleared.

Note:

You can only rename database message nodes; you cannot rename content provider message nodes.