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.

If you are creating or extending an application and want to manage content mappings with that application, you can use portal remote APIs to retrieve a list of content mappings and then create, update, or delete mappings. Based on the Representational State Transfer (REST) architecture, these ...

Configure IBM® WebSphere® Portal Express® to use a standalone LDAP user registry to store all user account information for authorization.

Outofthebox the web content viewer is based on the JSR 286 API. However, if you have exported the web content viewer from another server or if you installed the older IBM API web content viewer, you can use the convertwcmrenderingportlet task to convert the IBM API web content viewer ...

Configure IBM® WebSphere® Portal Express® to use a standalone LDAP user registry over SSL to store all user account information for secure authorization.

If you are using VMware ESX, you can create a virtual environment that will allow you to create virtual machine instance. When a new virtual machine instance is created, you need to update IBM® WebSphere® Portal Express® with the machine specific information, such as the host and node names of the ...

Configure IBM® WebSphere® Portal Express® to use a standalone LDAP user registry over SSL to store all user account information for secure authorization.

Add an LDAP user registry to the default federated repository to store user account information for authorization. You can add multiple LDAP user registries to the default federated repository although you can only add one LDAP server at a time. If IBM® Lotus® Domino® will be one of your user ...

Add an LDAP user registry over SSL to the default federated repository to store user account information for secure authorization. You can add multiple LDAP user registries to the default federated repository although you can only add one LDAP server at a time.

Configure IBM® WebSphere® Portal Express® to use a standalone LDAP user registry to store all user account information for authorization.

Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, to use software products successfully.

If you have made changes to your company and no longer require the use of a repository within your default federated repository, you can delete the repository from your configuration.