Outbound connection profile
The outbound connection profile contains the elements of the configuration model. The following profiles can exist.
- System profile
- Settings used by the system internally. A portal configuration contains exactly one system profile.
- Global profile
- Maintained by the portal administrator. The policy mappings, proxy rules, and cookie rules are available to all applications using the outbound connection service. A portal configuration contains zero or one global profile.
- Application-scoped profiles
- Valid within the scope of a specific web module. Scope is determined by the context root of the web module deployment descriptor. For example, if the deployment descriptor of the web module isad.war contains the context root setting /wps/PA_Banner_Ad, the application-scope profile must contain only /wps/PA_Banner_Ad as a scope reference.
An outbound connection profile item contains the application scope reference setting:
- application scope reference
- Null for the system profile and for the global profile. For application-scoped profiles, the scope reference identifies the application to which this profile belongs. The scope reference contains the context root setting of the application.
We can locate this information by either of the following ways:
- If the referenced application is a portlet application, log in to the portal using the portal administrator user ID and go to...
Administration | Portlet management | Web modules | Manage Web Modules portlet | web module | Web Module Properties
The web module properties view lists the context root. For example, this context root can be /wps/PA_Banner_Ad.
- Determine the context root of an application using the WAS console. Go to...
Applications | enterprise application | View Deployment Descriptor
The value context-root tag is the scope reference value.
Parent Configuration structure