Shulou(Shulou.com)06/02 Report--

1.6 Portal 6.1.0.3 unable to find any user or user group 1.6.1 problem description

After the Portal system is upgraded to 6.1.0.3, it is impossible to search for any users or user groups. The functional modules embodied are: WCM authorization, WCM management, PDM management, and no place where People Picker Page is used.

1.6.2 solution

This is because the upgrade program of Portal 6.1.0.3 may have inadvertently modified the property value of People Picker Portlet, resulting in the Portlet being unable to find the right user or user group, and we have to correct this problem manually. The steps to correct the problem are as follows.

Log in to the WAS Management console as a WAS Super Admin (usually wpsbind).

Click "Resource" → "Resource Environment" → "Resource Environment Providers" and locate the "WP PeopleService" entry, as shown in figure 1-26.

Figure 1-26 lack of attributes in PeopleFinder causes problems that people and organizations cannot find in many versions of Portal

Click Custom properties and edit the three property values shown in figure 1-27.

Figure 1-27 modify the PeoplePicker property in the resource provider

Make sure that these three values correspond to the property values in LDAP. For example:

Name Value

PickerPeopleSearchAttribute cn,displayName,sn,uid

PickerGroupSearchAttribute cn,displayName,sn,givenName

ConfigurePeoplePickerSearch true

Restart the Portal server to verify that it is working properly.

1.7 configuring Portal 6.1 to use the Oracle database failed 1.7.1 problem description

Failed to configure Portal 6.1.0.0 to use the Oracle database and migrate Portal data from the default database to Oracle. This problem can occur for a variety of reasons, but the three problems mentioned below are common. When a migration fails, please identify this problem first.

1.7.2 solution

The following three problems occur frequently during the engineer's configuration process, which can cause the Oracle database migration to fail.

(1) the Oracle version number is not the correct version number supported by Portal 6.1, especially the minor version number.

For example, if the Oracle version number installed by the user is 10.2.0.0, but the version number supported by Portal 6.1 is 10.2.0.1, this small patch gap will cause the migration to fail.

(2) the setting of transaction timeout by WAS is not appropriate.

The transaction timeout set by WAS is 130s by default, while many transactions of Oracle data transfer by Portal are more than 180s, which causes some threads to hang due to transaction timeout. This problem can be avoided by changing this timeout period to more than 300s before executing the transfer process.

(3) the Portal database administrator does not have permission to create views in Oracle.

In the process of creating Oracle database tablespaces, the user did not give administrator privileges to the specified Portal database administrator, resulting in data transfer failure due to insufficient permissions. This problem can be avoided by transferring the permission again after the permission is specified in Oracle.

1.8Configuring Portal 6.1Using Novell LDAP as the security mechanism for Portal 1.8.1 problem description

Configure Portal 6.1to use Novell LDAP as the user registry and security authentication mechanism for Portal. The configuration process is successful, but the users and user groups created in the Portal management console cannot be searched.

1.8.2 solution

After inspection, it is found that the user has the following problems in the configuration process.

LDAP users set too many filter conditions when they are searched by Portal. Users define eight properties of "LDAP entity types" according to their own settings document, which are used as filter conditions when Portal administrators search for users. In fact, the product requires only two filtering conditions, which are:

Standalone.ldap.et.group.objectClasses=groupOfNames

Standalone.ldap.et.personaccount.objectClasses=inetOrgPerson

The way to correct it is to delete the existing 8 attributes and add or update them to the above two attributes. After modifying these two parameters, search for users and user groups again, and the above problems are solved.

1.9 description of the problem of synchronizing 1.9.1 on a portal cluster

After performing Portlet installation, theme and skin installation, parameter configuration, etc., on the cluster, it was found that the second visit did not work. This is usually caused by the failure to perform cluster synchronization. Cluster synchronization must be performed after the above work is done. There are two ways to perform synchronization: one is forced (manual) synchronization, and the other is automatic synchronization.

1.9.2 solution 1.9.2.1 Force synchronization

Log in to the WAS management console as wpsadmin, as shown in figure 1-28.

Figure 1-28 Log in to the administrative console

Click system Administration → Node to display a list of existing nodes. Select the two machines you want to synchronize, and then click the synchronize button, as shown in figure 1-29.

Figure 1-29 Select the two machines to synchronize

The system begins to synchronize, as shown in figure 1-30.

Figure 1-30 start synchronization

After 1-2 hours, the system synchronization is completed.

1.9.2.2 automatic synchronization

On the page shown in figures 1-29, check that each node of the Portal cluster matches the settings file of the dmgr (Deployment Manager) node, and ensure the consistency of the cross-cell configuration data. The specific operation steps are as follows.

Log in to the administrative console and click system Administration → Node Agent → node_agent_name → File synchronization Service.

Select the configuration tab.

The service is enabled when the server starts.

Specifies whether the server attempts to start the file synchronization service. This setting does not cause the file synchronization operation to start. This setting is enabled by default.

Data type

Boolean

Default value

True

Specifies the synchronization interval in minutes. The default value is 1 minute.

Data type

Integer type

Unit

Minute

Default value

one

The minimum value used by the application server is 1. If the specified value is 0, the application server ignores the value and uses the default value of 1.

Set up automatic synchronization. Specifies whether files are automatically synchronized after the specified time interval. When this setting is enabled, Node Agent automatically contacts Deployment Manager during each synchronization interval to try to synchronize the node's configuration library with the main library owned by Deployment Manager.

If the automatic synchronization setting is enabled, Node Agent attempts to synchronize files when contacting Deployment Manager. Node Agent waits for the synchronization interval before attempting the next synchronization.

If you want to control the time when the file is sent to the node, deselect the automatic synchronization time check box.

Data type

Boolean

Default value

True

Start synchronization specifies whether Node Agent attempts to synchronize the node configuration with the latest configuration in the main library before starting the application server.

The default is not to synchronize files before starting the application server. Enabling settings ensures that Node Agent has the latest configuration, but increases the amount of time it takes to start the application server.

Note: this setting does not affect the startServer command. The startServer command starts the server directly without using Node Agent.

Data type

Boolean

Default value

False

Rule out. Specifies that the file or mode that should not be part of the configuration data synchronization. Files in this list are not copied to the node from the master configuration library and are not deleted from the library on the node.

The default is that no file is specified. The default value for iSeries users is * / plugin-cfg.xml, which synchronizes automatically from the Web server plug-in configuration file.

To specify a file, use the full name or a name that begins or ends with the wildcard * (asterisk). For example:

Cells/cell name/nodes/node name/file name

Exclude this specific file

* / file name

Exclude files named file name in any context

Dirname/*

Exclude dirname and sub-attributes under dirname

Press the "Enter" key at the end of each entry, and a file name appears on each line.

Because these strings represent the logical file location rather than the actual file path, no matter what platform it is, only a forward slash is needed.

Changes made to the exclusion list take effect when Node Agent is restarted.

Data type

String

Unit

File name or pattern

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.