psadmin register-portlet

Description

Registers all portlet applications packaged in an EAR file. This feature works only with EAR files generated by JCAPS tools, because the EAR files need Sun Portal proprietary artifacts inserted in them for this feature to work.

Syntax

Long Format

psadmin register-portlet --adminuser uid --passwordfile password-filename --dn dn | --global [--rolesfile roles-file] [--userinfofile user-info-file] --portal portal-ID portletearfile

Short Format

psadmin register-portlet -u uid -fpasswordfile -d [-r roles-file] [-n user-info-file] -p portal-ID portletearfile

Options

The following options are required:

[--adminuser | -u] uid

Specifies the administrator's distinguished name.

[--dn | -d] dn

Specifies the distinguished name in the LDAP node to access the Display Profile document. The -d or -g option is required.

[--passwordfile | -f] password-filename

Specifies the administrator's password in the password file.

[--portal | -p] portal-ID

Specifies the portal ID.

The following options are optional:

[--global | -g]

Specifies the global level node in LDAP to access the display profile document. The -d or -g option is required.

[--rolesfile | -r] roles-file

Specifies the file containing the Access Manager software and portlet application role mapping information.

[--userinfofile | -n] user-info-file

Specifies the file containing the user information mapping information.

The following is the operand:

portletearfile

Specifies the path to the EAR file.

The following is the usage:

psadmin register-portlet -u amadmin -f pfile -p portal1 -g /tmp/helloworld.ear

In the example provided above, all portlet applications in helloworld.ear are registered at the Global level.

psadmin register-portlet -u amadmin -f pfile -p portal1 -d o=DeveloperSample,dc=sun,dc=com --rolesfile temp/rolefile -g myejbapp.ear

In the example provided above, all portlet applications in myejbapp.ear are registered at the DeveloperSample node. A role mapping file is also specified.