Install WCM on the authoring server in WPS

System details:

• Operating system: Microsoft Windows 2003 Enterprise Edition with SP1 on x86-32
• Processor speed: 3.80GHz
• Physical memory: 4 GB of RAM
• Disk space: 3.9 GB for installation directory; 2 GB for the Temp directory
• File system: NTFS
• Virtual memory: 8 GB
• Network: Fully qualified host name and network access

Before beginning the installation:

• Check the hardware and software requirements to make sure the target system meets them.
• Disable the firewall and antivirus programs on the machine to ensure that they do not interfere with the installation. Once the installation completes, re-enable them.
• Download the product code from IBM's Passport Advantage Web site and store the code on a network drive where you can access the installation images from the machine where you are installing WebSphere Portal.

Install WebSphere Portal:

1. Open a command prompt on the target machine and changes directory to the network drive where you stored the installation images.
2. At the command prompt, enters the following command: install.bat
3. Select English as the language for the installation, click OK , and then click Next to continue.
4. Select I accept the terms in the license agreement , and click Next.
5. Select Typical , and click Next.
6. Enter C:\WebSphere\AppServer as the directory where the WebSphere Application Server will be installed. Before clicking Next , verify that:
• The directory does not already exist, because the installation program will create the directory.
• The directory name does not contain periods ( . ).
7. Verify the following WebSphere Application Server information before clicking Next .
• The cell name. In the case of a standalone server like this one, the cell name and node name are typically the same as the host name for the computer, unless the installation program needs to shorten them.
• The node within the WebSphere Application Server cell where the WebSphere Portal application server will be installed.
• The fully qualified host name or IP address of the machine being installed.
8. Enter the user ID and password for the WebSphere Application Server administrator, and click Next . You will use these credentials to log in to the WebSphere Application Server with administrator authority after installation. Take the following into consideration:
• Ensure the ID and password conform to your company's security policies
• Ensure there are no blanks in the user ID or password. You should also review the WebSphere Portal documentation regarding the use of special characters.
9. Enter C:\WebSphere\PortalServer as the directory where WebSphere Portal will be installed. Before clicking Next, verify:
• The directory does not already exist, because the installation program will create the directory.
• The directory name does not contain periods ( . ) or special characters, and he makes sure not to use a long path name, to avoid any Windows path name limitations.
10. Enter the user ID and password for the WebSphere Portal administrator, and click Next . You will use these credentials to log into WebSphere Portal with administrator authority after installation.Take the following into consideration:
• Ensure the ID and password conform to your company's security policies
• Ensure there are no blanks in the user ID or password. You should also review the WebSphere Portal
11. Misha is aware of a known issue when running WebSphere Portal as a Windows service, so he ensures that the check box is empty, and then click Next .
12. On the summary page Misha verifies the components to be installed and click Next . The installation program begins installing the selected components. Throughout the installation and configuration process, the installation program displays progress indicators for the different components.
13. When the installation finishes, the installation program displays a confirmation panel that indicates that WebSphere Portal is now running and provides the URL used to access the portal. Make a note of the URL, including the port number, and click Finish .
14. Check that WebSphere Portal is running by opening a browser to the URL displayed by the installation program.
• Here is an example of the URL, using the typical default port number:
  http://rendev.example.com:10038/wps/portal
15. Log in with the WebSphere Portal administrator user ID and password and confirm that the main page displays as expected.
16. Edit the WCMConfigService.properties file located under this directory:
    • C:\WebSphere\PortalServer\wcm\shared\app\config\wcmservices
17. Edit the following parameters with the details of the SMTP server that will be used to send automated e-mails as part of the workflow system:
• connect.connector.mailconnector.defaultsmtpserver=mail.yourmailserver.com
• connect.connector.mailconnector.defaultfromaddress=admin@yourmailserver.com
• connect.connector.mailconnector.defaultreplytoaddress=admin@yourmailserver.com
18. Save the WCMConfigService.properties file.
19. Now that the server is up and running, install the Web Content Management authoring portlet.
1. At a command prompt on the server, change the directory to the C:\WebSphere\PortalServer\config directory.
2. Enter the following command, specifying the WebSphere Portal administrator password with a command-line parameter:
   • WPSconfig.bat configure-wcm-authoring -DPortalAdminPwd= portal_admin_password
3. When the configuration task completes with a BUILD SUCCESSFUL message, close the command window.
4. Back in the browser, log out of the portal and then log back in.
20. Finally, click Web Content from main menu to access the authoring portlet.

Click here to View more...

Create Web content libraries and configure access in WPS

In this example, item type roles will be applied to the following groups:

WCMAdmins	Members of this group require access to all features of the authoring portlet.
SiteAdmins	Members of this group require access to all features of the authoring portlet except workflow.
SiteDesigners	Members of this group require access to content items, presentation templates, authoring templates and components.
ContentAuthors	Members of this group require access to content items and components.
ContentApprovers	Members of this group require access to content items only.

Library access
The simplest method of setting library access is to grant "contributor" access to all your groups. This gives all users and groups "contributor" access to the library and authoring portlet. Additional access is then granted to each group using resource permissions. You can also grant the "Anonymous Portal User" group "user" access to ensure all anonymous users can access the library if anonymous access is required for your Web site.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes
Manager	Yes	Yes
Editor	Yes	Yes
User	No	Yes	Anonymous Portal User
Contributor	Yes	Yes	WCMAdmins SiteAdmins SiteDesigners ContentAuthors ContentApprovers

Assigning roles to a library

1. Click Administration to open the administration portlet.
2. Go to Portal Content and then Manage Web Content Libraries.
3. Click on the library you would like to edit.
4. Click on the role you would like to edit.
5. Click Add and search for any users or groups you would like to assign to a role.
6. Click OK.
7. Click Resources to return to the previous view.
8. Click Done.

Resource permissions
Set the following resource permissions for each role type:

• The "WCMAdmins" group is assigned the "administrator" role for all resources.
• The "SiteAdmins" group is assigned the "manager role" to all resources except "workflow and workflow elements" as they do not require access to these resources.
• The other groups are assigned roles for each resource as outlined below.

Assigning roles to item types

1. Click Administration to open the administration portlet.
2. Go to Portal Content and then Manage Web Content Libraries.
3. Click on the library you would like to edit.
4. Click on the item type you would like to set permissions on for this library.
5. Click on the role you would like to edit.
6. Click Add and search for any users or groups you would like to assign to a role.
7. Click OK.
8. Click Resources to return to the previous view.
9. Click Done.

Authoring templates

The "SiteDesigners" group is assigned "editor" access to authoring templates as they are required to create new authoring templates.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes	SiteAdmins
Editor	Yes	Yes	SiteDesigners
User	Yes	Yes
Contributor	Yes	Yes

Components

Both the "SiteDesigners" and "ContentAuthors" groups are assigned "editor" access to components as they are required to create components.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes	SiteAdmins
Editor	Yes	Yes	SiteDesigners ContentAuthors
User	Yes	Yes
Contributor	Yes	Yes

Content

Both the "SiteDesigners" and "ContentAuthors" groups are assigned "editor" access to content as they are required to create content items. The "ContentApprovers" group is only assigned "Contributor" as they are not required to create new content items, but need approve access to content items during a workflow. You must also assign the "ContentApprovers" group "approve" access in the properties section of any workflow stages that "ContentApprovers" will use to approve content items.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes	SiteAdmins
Editor	Yes	Yes	SiteDesigners ContentAuthors
User	Yes	Yes
Contributor	Yes	Yes	ContentApprovers

Presentation Templates

The "SiteDesigners" group is assigned "editor" access to presentation templates as they are required to create new presentation templates.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes	SiteAdmins
Editor	Yes	Yes	SiteDesigners
User	Yes	Yes
Contributor	Yes	Yes

Site and site areas

Only the "WCMAdmins" and "SiteAdmins" groups require access to site and site areas as these are the only groups who build site frameworks.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes	SiteAdmins
Editor	Yes	Yes
User	Yes	Yes
Contributor	Yes	Yes

Taxonomy

Only the "WCMAdmins" and "SiteAdmins" groups require access to taxonomies as these are the only groups who build taxonomies.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes	SiteAdmins
Editor	Yes	Yes
User	Yes	Yes
Contributor	Yes	Yes

Workflow and workflow elements

Only the "WCMAdmins" group requires access to workflow and workflow elements as this is the only group that creates workflows. The groups that use workflows do not require access to the "Workflow and workflow elements" resource permissions.

Roles	Allow Propagation	Allow Inheritance	User/Group
Administrator	Yes	Yes	WCMAdmins
Manager	Yes	Yes
Editor	Yes	Yes
User	Yes	Yes
Contributor	Yes	Yes

Item-level security

The resource permissions set for each resource do not automatically give you access to individual items. They only give you access to specific tasks and views within the authoring portlet.

For example, although the "SiteDesigners" group has access to create new presentation templates, only the user who created the presentation template has access to edit the presentation template. You will need to grant the "SiteDesigners" group edit access on each presentation template for the users of that group to have edit access to all presentation templates.



Click here to View more...