The portal authentication filters are a set of plugin points. You can use them to intercept or extend the portal login, logout, session timeout, and request processing by custom code, for example to redirect users to a specific URL.

Make a note of the features that were available in the previous versions of IBM® WebSphere® Portal but are no longer available in this version or in future versions.

To start the Portal Scripting Interface from a console window, use the procedure described here.

After you complete working with the Portal Scripting Interface, you log out and exit the interactive scripting console.

The following exercise shows you some steps how to work with portal resources, such as pages and portlets, search for resources and information about them, and add a portlet to a page.

Before you can work with portal scripting commands, you need to log in to the portal server instance where you want to work with the Portal Scripting Interface.

The Portal Scripting Interface provides more commands and variants of commands than shown in the previous topics. To learn more about these commands and their syntax and function, and beans and parameters, refer to the integrated help of the Portal Scripting Interface.

For security reasons, the portal search seedlist by default redirects to HTTPs. Therefore you need to configure your myserver web server for HTTPs.

You can associate friendly URLs with portal pages and labels. You and your users can use these friendly URLs to access specific portal pages or labels by using a human readable path, which is easy to remember.

View information on how to manually transfer data to the DB2® database you have installed and set up. Follow these steps to transfer WebSphere® Portal Express®, and Java™ Content Repository databases to DB2. As an alternative to the manual database transfer procedure that this topic describes, ...

View information on how to manually transfer data to the DB2® database you have installed and set up. Follow these steps to transfer WebSphere® Portal Express®, and Java™ Content Repository databases to DB2. As an alternative to the manual database transfer procedure that this topic describes, ...

By setting the portal and portlet configuration parameters, you can monitor the session load and configure the parameters to increase performance.

After migrating IBM® WebSphere® Portal Express®, additional tasks might be needed depending on how you customized the source portal environment and which components you used.

If you configured WebSphere® Portal Express® to use virtual portal, there are some additional steps needed to complete the migration.

By default, only administrators have access to work with Web content libraries. To allow other users to work with web content libraries, such as virtual portal administrators, you need to assign them access to the JCR content root node.

With WebDAV for IBM® WebSphere® Portal Express®, you can use standard operating system tools to create, modify, and delete web content rather than the standard authoring portlet.

Before you can work with portal scripting commands, you need to log in to the portal server instance where you want to work with the Portal Scripting Interface.

After you complete working with the Portal Scripting Interface, you log out and exit the interactive scripting console.

The Portal Scripting Interface provides more commands and variants of commands than shown in the previous topics. To learn more about these commands and their syntax and function, and beans and parameters, refer to the integrated help of the Portal Scripting Interface.

The following exercise shows you some steps how to work with portal resources, such as pages and portlets, search for resources and information about them, and add a portlet to a page.

To start the Portal Scripting Interface from a console window, use the procedure described here.

You can associate friendly URLs with portal pages and labels. You and your users can use these friendly URLs to access specific portal pages or labels by using a human readable path, which is easy to remember.

For security reasons, the portal search seedlist by default redirects to HTTPs. Therefore you need to configure your myserver web server for HTTPs.

By setting the portal and portlet configuration parameters, you can monitor the session load and configure the parameters to increase performance.

The developer mode allows you to improve start up performance and to configure IBM® WebSphere® Portal Enable for zOS® for development. This file explains how to configure and unconfigure the development mode option. Developer mode is for a development environment only and should not be used in a ...