![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This section covers the following topics:
Integrating AquaLogic Enterprise Security with WebLogic Portal server and portal application results in an enhanced set of security services for use in protecting WebLogic Portal (see Figure 9-1). AquaLogic Enterprise Security participates in the authoring and management of policy for WebLogic Portal resources. Once AquaLogic Enterprise Security is integrated with WebLogic Portal, you use AquaLogic Enterprise Security Administration Server to manage resources related to portal desktops, books, pages, and portlets.
Therefore, the intent is that you use AquaLogic Enterprise Security for authorization of the resources associated with a portal application as well as standard WebLogic Server J2EE resources. The benefit of using AquaLogic Enterprise Security to manage visitor entitlements is that it offers fine-grained, dynamic role-based authorization. Additionally, AquaLogic Enterprise Security allows you to have common security policies for a heterogeneous environment. For example, you may have a single security infrastructure that supports WebLogic Portal, WebLogic Server, and custom applications.
The AquaLogic Enterprise Security security service does not replace all of the management functionality provided by the Portal Administration Tools. For example, as shown in Figure 9-1, AquaLogic Enterprise Security is not used to manage administrative users and resources associated with Portal Delegated Administration and Portal Content Management; use the Portal Administration Tools for those management tasks.
AquaLogic Enterprise Security enables you to write, deploy, and manage fine-grained policy for controlling access to WebLogic Portal application resources. You can use AquaLogic Enterprise Security to protect portal desktops, books, pages, portlets, and application look and feels.
For more information, see the following topics:
AquaLogic Enterprise Security and WebLogic Portal can be used with WebLogic Server 9.2 or WebLogic Server 8.1 Service Pack 4 or Service Pack 5. While several different security providers can be used with WebLogic Portal, the following security providers include enhanced WebLogic portal support:
Note: | Use of the Database Authentication provider with WebLogic Portal is not mandatory. You may use other authentication providers as well. |
The following use-case scenario is supported when you integrate AquaLogic Enterprise Security with WebLogic Portal:
Note: | To implement this use case scenario, you must define the security configuration as specified in Creating the Portal Application Security Configuration. |
When integrated with AquaLogic Enterprise Security, WebLogic Portal has the following constraints and limitations:
Use of AquaLogic Enterprise Security with a Portal application implies that an administrator will not use the Portal Administration Tools to create "Visitor Entitlements" on portal desktops, books, pages, and portlets. Managing visitor entitlements from the Portal Administration Tools is not a supported use case.
Use of Deployment descriptors to deploy policy is not supported in AquaLogic Enterprise Security.
AquaLogic Enterprise Security does not to support the migration of visitor entitlements policy for existing portal applications. There are no facilities for migrating any information from the WebLogic Server embedded LDAP store.
You cannot use AquaLogic Enterprise Security to manage the resources associated with Portal Delegated Administration and Portal Content Management. AquaLogic Enterprise Security does not support Portal Unified User Profiles.
Before you begin, you must ensure that the following pre-requisites are satisfied:
This section describes how to integrate AquaLogic Enterprise Security with WebLogic Portal 9.2. The procedure for integrating ALES with WebLogic Portal 8.1 is different; for information about that, see Integrating with WebLogic Portal 8.1: Main Steps. Once integrated, you can use the AquaLogic Enterprise Security Administration Console to write and deploy a set of authorization and role mapping policies to protect WebLogic Portal application resources.
To integrate AquaLogic Enterprise Security with WebLogic Portal 9.2, perform the following tasks:
This section describes how to create a new security configuration named myrealm
.
myrealm
. portalInstance
and the Configuration ID to myrealm
.To configure security providers for the WebLogic Server 9.x Security Service Module, you use the WebLogic Server Administration Console, not the ALES Administration Console. In order to create and configure ALES security provider instances using the WebLogic Server Administration Console, you must first install an extension to the console. See Modifying the startWebLogic File.
For information about how to configure security providers for ALES and WebLogic Portal 9.2, see Configuring Security Providers for the WebLogic Server 9.x SSM.
Before you can start a WebLogic Portal server that uses BEA AquaLogic Enterprise Security, you must modify the startWeblogic
file that is located in the WebLogic Portal domain that you are using for you WebLogic Portal server.
The startWeblogic
file for the WebLogic Portal sample domain named portalDomain
is located at: BEA_HOME\weblogic92\samples\domains\portal
To edit the startWeblogic
file, perform the steps:
Note: | This procedure assumes a Windows installation of WebLogic Portal in the directory c:\bea with a WebLogic Server Security Service Module instance named portalInstance . |
startWeblogic.cmd
to startWeblogic.cmd.original
.set-wls-env.bat
. For example, add it below the line: set SAVE_JAVA_OPTIONS=
call "c:\bea\ales22-ssm\wls9-ssm\instance\portalInstance\bin\set-wls-env.bat"
classpath
variables to the classpath
. For example, add the following text before the line: echo CLASSPATH=%CLASSPATH%
set CLASSPATH=%CLASSPATH%;%WLES_POST_CLASSPATH%
%WLES_JAVA_OPTIONS%
to the server start command after %JAVA_OPTIONS%
. Listing 9-2 shows, in bold text, where to make this change.if "%WLS_REDIRECT_LOG%"=="" (
echo Starting WLS with line:
echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% %WLES_JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS%
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% %WLES_JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS%
) else (
echo Redirecting output from WLS window to %WLS_REDIRECT_LOG%
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% %WLES_JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS% > "%WLS_REDIRECT_LOG%" 2>&1
)
This section describes how to integrate AquaLogic Enterprise Security with WebLogic Portal 8.1. Once integrated, you can use the AquaLogic Enterprise Security Administration Console to write and deploy a set of authorization and role mapping policies to protect WebLogic Portal application resources.
Note: | While the instructions provided in this section use a WebLogic Portal server and the sample portal application that ships with the WebLogic Platform software distribution, you can use this procedure to integrate AquaLogic Enterprise Security with your WebLogic Portal server and portal application. |
To integrate AquaLogic Enterprise Security with WebLogic Portal, perform the following tasks:
This section describes how to create a new security configuration named myrealm
. A security configuration defines the set of security providers to use for adjudication, authentication, auditing, authorization, role mapping, and credential mapping services. The security configuration named myrealm
matches the default security configuration for the WebLogic Portal sample portal application.
Note: | To implement the use-case scenario described in Supported Use-case Scenario, you are required to define the security configuration as described in this section. This security configuration is a requirement; it is not optional. |
Refer to Table 9-1 and use the AquaLogic Enterprise Security Administration Server to configure the security providers listed there. Set the Configuration ID to myrealm
. For instructions on creating a security configuration, see the administration console's help system.
Set the Control Flag to
SUFFICIENT, and click Create. For the Details tab settings, except for the Identity Scope, the parameters are populated automatically. Set the Identity Scope to myusers , and click Apply.
|
|||||
|
|||||
The security configuration must be bound to a Service Control Manager.
To bind the myrealm
security configuration, see the Console Help
The myrealm
security configuration must be distributed.
To distribute the myrealm
security configuration, see
the Console Help.
Before starting a WebLogic Server Security Service Module, you must first create an instance of the WebLogic Server Security Service Module using the Create New Instance Wizard.
To create an instance of a WebLogic Server Security Service Module, see Creating an Instance of a Security Service Module in Installing Security Service Modules.
You must have the Administration Server running prior to enrolling the Security Service Module.
Note: | While you can use the demonstration digital certificate in a development environment, you should never use it in a production environment. |
To enroll a security service module, see Enrolling the Instance of the Security Service Module in Installing Security Service Modules.
Before you can start a WebLogic Portal server that uses BEA AquaLogic Enterprise Security, you must modify the startWeblogic
file that is located in the WebLogic Portal domain that you are using for you WebLogic Portal server.
The startWeblogic
file for the WebLogic Portal domain named portalDomain
is located at: BEA_HOME\user_projects\domains\portalDomain
To edit the startWeblogic
file, perform the steps:
Note: | This procedure assumes a Windows installation of WebLogic Portal in the directory c:\bea with an WebLogic Server Security Service Module instance named portalInstance . |
startWeblogic.cmd
to startWeblogic.cmd.original
.set-wls-env.bat
. For example, add it below the line: set SAVE_JAVA_OPTIONS=
call "c:\bea\ales22-ssm\wls-ssm\instance\portalInstance\bin\set-wls-env.bat"
classpath
variables to the classpath
. For example, add the following text before the line: echo CLASSPATH=%CLASSPATH%
set CLASSPATH=%WLES_PRE_CLASSPATH%;%CLASSPATH%;%WLES_POST_CLASSPATH%
%WLES_JAVA_OPTIONS%
to the server start command after %JAVA_OPTIONS%
. Listing 9-2 shows, in bold text, where to make this change.if "%WLS_REDIRECT_LOG%"=="" (
echo Starting WLS with line:
echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% %WLES_JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS%
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% %WLES_JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS%
) else (
echo Redirecting output from WLS window to %WLS_REDIRECT_LOG%
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% %WLES_JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS% > "%WLS_REDIRECT_LOG%" 2>&1
)
Create a text file named security.properties
and place it in the portal domain directory. You use this file to define the AquaLogic Enterprise Security realm and the default realm. Listing 9-3 shows the content of this file for the realm myrealm
.
# AquaLogic Enterprise Security Configuration File
#
# This file contains AquaLogic Enterprise Security configuration
# properties. By default, the AquaLogic Enterprise Security runtime
# looks for a property file called 'security.properties' in the
# working directory.
wles.realm=myrealm
wles.default.realm=myrealm
To integrate AquaLogic Enterprise Security with WebLogic Portal, you must replace the p13n_ejb.jar
file in the top-level portal application directory with the version of that file that is provided in the AquaLogic Enterprise Security software distribution. The AquaLogic Enterprise Security version of p13n_ejb.jar
is located in BEA_HOME/
ales22-ssm/wls-ssm/lib
directory.
Note: | BEA AquaLogic Enterprise Security 2.2 includes two versions of p13n_ejb.jar , the WebLogic Server 8.1 SP4 version: p13n_ejb_81SP4.jar , and the SP5 version: p13n_ejb_81SP5.jar . Be sure to use the correct version. |
Note: | Because these instructions assume that you are using the sample portal application that ships with WebLogic Portal, this procedure instructs you to replace the p13n_ejb.jar in the sample portal application. To use a different portal application, replace p13n_ejb.jar in that application as well. |
To replace p13n_ejb.jar
, perform the following steps:
p13n_ejb.jar
. For example, rename it to p13n_ejb.jar.original
. The portal application version of this file is located in BEA_HOME/weblogic81/samples/portal/portalApp.
p13n_ejb_81SP4.jar
or p13n_ejb_81SP5.jar
from BEA_HOME/ales22-ssm/wls-ssm/lib/
to BEA_HOME/weblogic81/samples/portal/portalApp
and rename
it to p13n_ejb.jar
.
To integrate AquaLogic Enterprise Security with WebLogic Portal, you must replace the p13n_system.jar
file in the BEA_HOME/weblogic81/p13n/lib
directory with the version of that file that is provided in the AquaLogic Enterprise Security software distribution. The AquaLogic Enterprise Security version of this file is located in BEA_HOME/ales22-ssm/wls-ssm/lib
directory.
Note: | BEA AquaLogic Enterprise Security 2.2 includes two versions of p13n_system.jar , the WebLogic Server 8.1 SP4 version: p13n_system_81SP4.jar , and the SP5 version: p13n_system_81SP5.jar . Be sure to use the correct version. |
Note: | Once you replace p13n_system.jar in the /lib directory of the WebLogic Platform installation, all portal domains configured for that installation must be AquaLogic Enterprise Security enabled. |
To replace p13n_system.jar
, perform the following steps:
p13n_system.jar
. For example, rename it to p13n_system.jar.original
. The portal version of this file is located in BEA_HOME/weblogic81/p13n/lib.
p13n_system_81SP4.jar
or p13n_system_81SP5.jar
from BEA_HOME/ales22-ssm/wls-ssm/lib/
to BEA_HOME/weblogic81/p13n/lib
and rename it to p13n_system.jar
.
WebLogic Server uses the DefaultAuthorizerInit.ldift
file to establish access controls for J2EE resources. By default, WebLogic Server allows access to all J2EE resources to users in the Everyone
role. To protect these resources, WebLogic Server provides the Administration Console and other tools to define security policies.
When using AquaLogic Enterprise Security, there is a need to supersede the WebLogic Server J2EE access controls. The DefaultAuthorizerInit.ldift
file, provided in the AquaLogic Enterprise Security 2.2 for the WebLogic Server Security Service Module, is used for this purpose.
To enable the AquaLogic Enterprise Security DefaultAuthorizerInit.ldift
file to supersede WebLogic Server access controls for J2EE resources in the sample portal application, perform the following steps:
Note: | Because these instructions assume that you are using the sample portal domain that ships with WebLogic Portal, this procedure instructs you to delete the ldap directory in the portalDomain/portalServer directory. Repeat the above steps for all AquaLogic Enterprise Security enabled portal domains. |
Developing a set of policies typically begins by determining which resources you need to protect and your access control requirements. You then create the identity directory, resources, groups, users, and roles that you will use to write policies to protect those resources. Next you write a set of authorization and role mapping policies to define access control on those resources. Finally, you deploy the set of polices to the WebLogic Server Security Service Module that you use to control access to your portal application resources.
AquaLogic Enterprise Security provides two means for writing portal application policy, the Administration Console and the Policy Import Tool. In this section you are directed to use the Administration Console to write policy. For more information on how to use the Administration Console to write policy, see the Policy Managers Guide and the Console Help.
In addition, the ALES Administration Server installation includes a set of sample polices for BEA WebLogic Portal, located at BEA_HOME/ales22-admin/examples/policy/portal_sample_policy
. You can import these sample policies and use them as a starting point for developing a full set of policies for your applications. For information about how to import the sample policies, see the README files in each of the sample directories and see also
Importing Policy Data in the Policy Managers Guide.
This section covers the following topics:
This section describes how to use the Administration Console to create an identity directory, groups, and users for a portal application.
Note: | This procedure uses myusers as the name of the Identity directory; however, you can use a different name. |
To create the Identity directory and users:
myusers
and click OK. The myusers
directory appears in the list of Identity directories.
If you are using the WebLogic 9.x SSM, create a user with the Admin role to access the WebLogic Server Administration Console. The default WebLogic Server Admin user and password is weblogic
/weblogic
.
This section describes how to use the Administration Console to define the portal application resources that you will protect using AquaLogic Enterprise Security.
To configure resources, perform the following tasks:
Note: | myrealm is used is this procedure as the realm name because the WebLogic Portal 8.1 sample portal application exists in the myrealm realm. You can choose any realm name for your portal application; however, if you are integrating WebLogic Portal 9.2 using the WebLogic Server 9.x SSM, the Configuration ID must match the name of the WebLogic Server security realm. |
To create a realm resources, perform the following steps:
myrealm
, select Binding
from the Type drop-down list box, and click Ok. The myrealm
resource appears under the Policy node.myrealm
resource and click Configure. The Configure Resource dialog box appears.Figure 9-2 shows the shared resources that you must create.
To create the shared
resources, perform the following steps:
myrealm
resource and click New. The Create Resource dialog box appears.shared
, and click Ok. The shared
resource appears under myrealm
.shared
resource and click New. The Create Resource dialog box appears.adm
and click Ok. The adm
resource appears under the shared
resource.jdbc
, jndi
, and svr
resources as shown in Figure 9-2, repeat steps 5 and 6 for each resource.Figure 9-3 shows the console resources that you must create.
To create the console
resources, perform the following steps:
myrealm
resource and click New. The Create Resource dialog box appears.consoleapp
, and click Ok. The consoleapp
resource appears under myrealm
.
For WebLogic Portal 8.1, in the Name text box, enter console
, and click Ok. The console
resource appears under myrealm
.
url
, console
, login
, and bea_logo.gif
resources as shown in Figure 9-3, repeat steps 1 and 2 for each resource.console
or consoleapp
resource directly under myrealm
and click Configure. The Configure Resource dialog box appears.Note: | This procedure uses portalApp as the name of the portal application resource because it is the name of the WebLogic Portal sample portal application. However, you should use the name of your portal application when creating the portal application resource. |
Figure 9-4 shows the portalApp
resources that you must create. In addition, if you are integrating WebLogic Portal 9.2 using the WebLogic Server 9.x SSM, you must create these virtual resources under myrealm
:
To create the portalApp
resources, perform the following steps:
myrealm
resource and click New. The Create Resource dialog box appears.portalApp
, and click Ok. The portalApp
resource appears under myrealm
.portalApp
resource and click New. The Create Resource dialog box appears.ejb
and click Ok. The ejb
resource appears under the portalApp
resource.ejb
resource and click Configure. The Configure Resource dialog box appears.url
resource, repeat steps 5 and 6.portalApp
resource and click New. The Create Resource dialog box appears.wlp
and click Ok. The wlp
resource appears under the portalApp
resource. Do not configure the wlp
resource to allow virtual resources.url
resource and click New. The Create Resource dialog box appears.portalappadmin
and click Ok. The portalappadmin
resource appears under the url
.portalApp
resource in Figure 9-4. Do not configure any of the remaining resources to allow virtual resources.This section describes how to use the Administration Console to create role mapping policy that will be used to control access to portal application resources.
Table 9-3 lists and describes the role mapping policy that you have to create for the WebLogic Portal domain.
Creates the role mapping policy necessary for the Everyone role to be used in the
myrealm Identity directory.
|
To create the role mapping policy, refer to Table 9-3 and perform the following steps:
Caution: | If you do not create the Everyone role mapping policy correctly, none of the authorization policies defined in Table 9-4 and Table 9-5 that use the Everyone role will work properly. |
Everyone
in the Available Roles list box, and click Add.myrealm
, and click Add.allusers
in the list box, click Add, and click Ok.This section describes how to use the Administration Console to create authorization policies to protect portal application resources.
Table 9-4 lists and describes the authorization policies that you have to create for the WebLogic Portal domain to protect the sample portal application resources. In addition, Table 9-5 lists the authorization policies required for WebLogic Portal 9.2.
Perform the following steps create the authorization policies listed in Table 9-4 (and, for WebLogic Portal 9.2, Table 9-5).
any
privilege from the Select Privileges from Group list box, and click Add. svr
resource from the Child Resource box and click Add. Note: | If you want to assign multiple resources to a single privilege and role, you may define all of the resources in one authorization policy. |
Admin
role from the Roles List box, click Add, and click Ok. Visitor entitlements is a mechanism used by WebLogic Portal for determining who may access the resources in a portal application and what they may do with those resources. AquaLogic Enterprise Security provides a means of defining robust role-based policy for portal resources. The resources that can be entitled within a portal application include:
Table 9-6 shows the capabilities of each of these resources:
The capabilities listed in Table 9-6 are defined as follows:
The following topics provide information on how to use AquaLogic Enterprise Security to configure portal resources:
A desktop is a view of the portal that the visitor accesses. There can be one or more desktops per portal, so the portal is effectively a container for the desktops. A Desktop is referenced as a resource in AquaLogic Enterprise Security in the following manner:
//app/policy/
myrealm
/
portalapp
/wlp/
sampleportal
/com_bea_p13n/Desktop/
samplePortal
If you define an authorization policy at the samplePortal
level, you can control access at the samplePortal
desktop level.
Table 9-7 shows an authorization policy that grants the view
privilege to the samplePortal
desktop for visitors in the SampleVisitor role.
A book is a collection of pages. A book is referenced as a resource in AquaLogic Enterprise Security in the following manner:
//app/policy/myrealm/portalapp/wlp/sampleportal/com_bea_p13n/Book/
book_1
where book_1
is the label definition of the book.
If you define an authorization policy at the book_1
level, you can control access at the book_1
book level.
Table 9-8 shows an authorization policy that grants the view
privilege to the book_1 book for visitors in the SampleVisitor role.
A page is the primary holder of individual portal elements such as portlets. A page is referenced as a resource in AquaLogic Enterprise Security in the following manner:
//app/policy/myrealm/portalapp/wlp/sampleportal/com_bea_p13n/Page/page_2
where page_2
is the label definition of the page.
If you define an authorization policy at the page_2
level, you can control access at the page_2 page level.
Table 9-9 shows an authorization policy that grants the view
privilege to the page_2 page for visitors in the SampleVisitor role.
Portlets are the visible components that act as the interface to applications and content. A portlet is referenced as a resource in AquaLogic Enterprise Security in the following manner:
//app/policy/myrealm/portalapp/wlp/sampleportal/com_bea_p13n/Portlet/
portlet_login1
where portlet_login
is the label definition of the portlet.
If you define an authorization policy at the portlet_login1
level, you can control access at the portlet_login1
Portlet level.
Table 9-10 shows an authorization policy that grants the view
privilege to the portlet_login1
Portlet for visitors in the SampleVisitor role.
|
A Look and Feel is a selectable combination of skins and skeletons that determine the physical appearance of a portal desktop. A Look and Feel is referenced as a resource in AquaLogic Enterprise Security in the following manner:
//app/policy/myrealm/portalapp/wlp/sampleportal/com_bea_p13n/LookAndFeel/
textLookAndFeel
where textLookAndFeel
is the label definition of the Look and Feel.
If you define an authorization policy at the textLookAndFeel
level, you can control access at the textLookAndFeel
level.
Table 9-11 shows an authorization policy that grants the view
privilege to the textLookAndFeel
Look and Feel visitors in the SampleVisitor role.
|
Portlets have a unique instance ID that allows for granular authorization policy definition outside the standard hierarchy of the Desktop->Book->Page->Portlet. To use this in AquaLogic Enterprise Security, add a condition statement in the portlet rule that adds the portlet instance ID. For example:
grant( [//priv/maximized,//priv/minimized,//priv/view], //app/policy/myrealm/portalapp/wlp/sampleportal/com_bea_p13n/Portlet
/portlet_login1
, //role/Operator) if instanceid = "portlet_login1
";
Table 9-12 shows an authorization policy that grants the view
privilege to the portlet_login1
Portlet for visitors in the Operator role.
|
if instanceid = " |
When developing policies for use with a Security Service Module, you can use the discovery mode feature of the AquaLogic Enterprise Security Administration Server to help define your policy components. Instructions for using discovery mode are provided in the Resource Discovery section in the Policy Managers Guide.
Distribute policy and security configuration to the WebLogic Server Security Service Module.
For information on how to distribute policy and security configuration, see the Console Help. Be sure to verify the results of your distribution.
To start a WebLogic Portal server, perform the following steps:
To use the WebLogic Authentication provider to manage administrative users for portal administration, perform the following steps:
Before you can use AquaLogic Enterprise Security to control access to a portal desktop, you must use WebLogic Portal Administration Tools to create a portal desktop.
To create a portal desktops, perform the following steps:
For instructions on using Portal Administration Tools to create portal desktops, see Create a Desktop in the WebLogic Administration Portal Online Help.
To create a portal desktop for the sample portal application using the Portal Administration Tools, perform the following steps:
http://<hostname>:7001/testportalappAdmin
. The Sign In page appears.portaladmin
, Password: portaladmin
, and click Sign In. The Portal Resources navigation tree appears.myportal
, enter a partial URL for this Portal, for example: myportal
, and click Save. The Available Portals list appears.myportal
link from the list. The Editing Portal: myportal
page appears.mydesktop
and a Partial URL, for example: mydesktop
. testportalweb/test.portal
and click Create New Desktop. Desktops contained in Portal myportal
list appear.mydesktop
from the list. The Editing Desktop: mydesktop
page appears.mydesktop
is displayed in a new browser window. Verify that the desktop contains the sample portal application.To access a portal application running on a portal server, open a browser and point it to the desktop URL. For example, if you set up the desktop for the sample portal application as described in Using Portal Administration Tools to Create a Portal Desktop, you can access the sample portal application using the following URL:
http://<
host_name
>:7001/sampleportal/appmanager/myportal/mydesktop
where <host_name
> is the machine on which portal application is running.
![]() ![]() ![]() |