An excerpt from Portal Wiki Site about Site Management:
Site Management features provided by WebSphere Portal v6.1 make managing multiple
portal deployments easier. Portal administrators can use Site Management and the
Resource Manager portlet to develop and test a portal page on a test server, then copy the
page to a target server for review and later promotion to a live page. Once you publish the
page to a target server where only a selected group of users can preview and do additional
test before promoting the page to all users and groups with the appropriate access rights.
After the page is modified , republished and re-promoted, the previous promoted page
becomes a version page. The demote function makes the page no longer visible in the
target server if a rollback is needed.
The following example illustrates how to use Site Management to perform a portal
Enabling remote access to your servers
The portal site management publish feature requires at least two portal systems: a source
system, where you create new pages that you need to publish, and a target system, where
you make the new pages visible to portal users. You can also use one server with two or
more virtual portals for your source and target systems. The Resource Manager portlet
can display the contents of the systems. By default, the portal server is pre-configured to
allow remote access.
If you have a portal cluster, you need to run the enable-http-basic-auth-taisitemgmt
task before you start managing your site. A WebSphere Application Server
Trust Association Interceptor (TAI) is used to authorize access to the servers.
Note: Individual virtual portals on a single portal server do not require the enablehttp-
basic-auth-tai-sitemgmt task to be run more than once.
In this River Bend project, the development server is a standalone portal server, both
staging and production environments are vertical portal clusters with two portal instances
installed on the same physical Windows 2003 server. In order to manage the sites, the
task enable-http-basic-auth-tai-sitemgmt needs to be run on the staging
and production servers for each portal instance, details of running this task are described

Yazının tamamını okuyun (

Yorum (comment) (2)