To make your portlets available in a portal, you must register the provider that owns those portlets with the portal. After you register a provider, the provider and its portlets become available in the Portlet Repository and the Add Portlets screen. They are also listed in the Navigator.
To register a provider, you must have at least Publish privileges on All Providers.
If
you are registering a database provider that uses the Federated
Portal Adapter, choose Web as the implementation style instead
of Database, because although the provider is written in PL/SQL, all
communication to it is as a Web provider. For more information, see
the Oracle9iAS Portal
Configuration Guide on Portal
Center.
In the Providers portlet, click Register a Portlet Provider.
Note: By default, the Providers portlet is on the Build tab of the Builder page.
In the Name field, enter the name of the provider.
Note: The name you enter here must be the same as the name of the provider on the server on which it resides.
In the Display Name field, enter a more descriptive name for the provider. This display name is be the name that appears in the Portlet Repository.
In the Timeout field, enter the number of seconds the portal should attempt to connect to this provider before timing out.
In the Timeout Message field, enter the message to display within the body of the portlet when the portal cannot establish contact with the provider within the number of seconds specified in the Timeout field.
Note: The message may not contain either mobile (mobileXML) or desktop (HTML) markup.
In the Implementation Style list, choose:
Database if the provider is written as a PL/SQL package. Oracle9iAS Portal communicates to the database provider by making local procedure calls.
Web if the provider is written as a Web application. Oracle9iAS Portal communicates to the Web provider using the HTTP protocol.
Click Next.
To continue registering your provider, select the appropriate procedure below:
In the URL field, enter the provider's URL.
Select Web provider in same cookie domain as the portal, if the cookies created by the provider are in the same domain as the portal.
(Optional) In the Service Id field, enter the service id of the provider if multiple providers are accessed via the specified URL.
Select how the user names and passwords used by the provider's application relate to the user names and passwords used by the portal:
Select the first radio button if the provider's application uses the same user names and passwords as the portal's Single Sign-On Server.
Select the second radio button if the provider's application uses different user names and passwords from the portal's Single Sign-On Server.
If you select this option, you must also enter the application id of the external application used for user authentication in the External Application ID field.
(Optional) In the Subscription Key field, enter the key to uniquely identify Oracle9iAS Portal as the requester.
(Optional) In the Shared Key field, enter the key for encrypting calls to the provider.
In the User/Session Information section:
Select Public if the provider does not require any user or session specific information.
Select User if the provider requires user specific information.
If you select this option, in the Login Frequency list, choose how often to call the provider's initSession method. Choose:
Always if you want call the provider's initSession method every time each user requests one of the provider's portlets.
Once Per User Session if you want to call the provider's initSession method only the first time each user requests one of the provider's portlets.
Never if you do not want to call the provider's initSession method when users request one of the provider's portlets.
(Optional) Select Require portal user specific session information if the provider also requires session specific information.
(Optional) If your portal uses proxy servers, you can choose to use them for contacting your provider.
In the Middle Tier list, choose the proxy server to use for contacting the provider from the middle tier for rendering the provider's portlets.
In the Portal Repository list, choose the proxy server for contacting the provider from the portal database for getting information about the provider and its portlets.
Note: You can also choose to not use a proxy server for either of these connections.
Tip: To specify a new proxy server, see Adding a proxy server.
Click Next.
In the Grantee field, enter the name of the user or group that you want to allow to access this provider.
Tip: If you are not sure of
the name of the user or group, click 
(for users) or 
(for groups), and select from the list provided.
In the list, choose a privilege level.
Click Add.
Repeat steps 10 through 12 as necessary.
Click Finish.
In the Owning Schema field, enter the name of the schema where the PL/SQL package that implements the provider is stored.
Tip:
If you are not sure of the name, click 
,
and select from the list provided.
In the Package Name field, enter the name of the PL/SQL package that implements the provider.
In the Login Frequency list, choose how often to call the provider's do-login API. Choose:
Always if you want call the provider's do-login API every time each user requests one of the provider's portlets.
Once Per User Session if you want to call the provider's do-login API only the first time each user requests one of the provider's portlets.
Never if you do not want to call the provider's do-login API when users request one of the provider's portlets.
Click Next.
In the Grantee field, enter the name of the user or group that you want to allow to access this provider.
Tip: If you are not sure of
the name of the user or group, click
(for users) or
(for groups), and select from the list provided.
In the list, choose a privilege level.
Click Add.
Repeat steps 5 through 7 as necessary.
Click Finish.
If the provider that you want to register belongs to a provider group that is already registered with the portal, simply drill down into that provider group in the Navigator, and click the Register link next to the provider.
To edit the registration information, click Edit next to the provider in the Navigator.
Because OID can include multiple containers that can use the same group names, the distinguished name (DN) is displayed next to any group that does not belong to the local Oracle9iAS Portal instance.