Deploy additional collaborative portlets
Contents
- Overview
- Before you begin
- Deploy all collaborative portlets shipped with WebSphere Portal
- Deploy a single collaborative portlet
Overview
This topic contains instructions for deploying the additional collaborative portlets that were shipped with your edition of WebSphere Portal. You can deploy the portlets individually, or you can deploy them all. The portal administrative interface also provides a way for you to install portlets to make them available to users.
If you are running with security enabled on WebSphere Application Server, specify a user ID and password for security authentication when entering the stopServer command to stop a server. For example:
stopServer WebSphere_Portal \ -user was_admin_userid \ -password was_admin_password
Before you begin
Before you can run the command to deploy portlets, verify WebSphere Portal has started...
- Determine if the WebSphere_Portal appserver is already running...
- If WebSphere Portal is not started, do one of the following to start it:
- If server1 is stopped as well, type the following two commands:
startServer server1 startServer WebSphere_Portal- If server1 is started, type the following command:
startServer WebSphere_Portal
Deploy all collaborative portlets shipped with WebSphere Portal
Follow the instructions provided to deploy the Lotus collaborative portlets.
- Make sure that WebSphere Portal has started.
- Edit...
$WP_ROOT/bin/xmlaccess.sh...and verify that the values for the JAVA and WPS_HOME variables contain the correct installation directory paths.
- Deploy the portlets...
cd $WP_ROOT/bin ./xmlaccess.sh -in ../config/work/lccportlets.xml \ -user admin_name \ -pwd admin_password \ -url server:port/portal_server_context_root/configFor example...
./xmlaccess.sh -in ../config/work/lccportlets.xml \ -user wpsadmin \ -pwd wpsadminpwd \ -url myserver:80/wps/config- Restart WebSphere Portal for the changes to take effect...
stopServer WebSphere_Portal startServer WebSphere_Portal
Deploy a single collaborative portlet
Use the following instructions to deploy a single collaborative porltet.
- Make sure that WebSphere Portal has started.
- Use a text editor to open the xmlaccess file that is appropriate for your operating system:
- UNIX/Linux: <wp_root>/bin/xmlaccess.sh
- Windows: <wp_root>\bin\xmlaccess.bat
- Verify that the values for the JAVA and WPS_HOME variables contain the correct installation directory paths. To change the values, edit and save the file.
- Deploy the specific portlet by typing the command that is appropriate for your OS...
cd $WP_ROOT/bin ./xmlaccess.sh -in ../config/work/xml_file \ -user admin_name \ -pwd admin_password \ -url server:port/portal_server_context_root/config...where xml_file is the name of the XML file name for the portlet. See the following list to map the file name with the portlet.
lcc_quickappointment_portlet.xml Quick Appointment lcc_quickemail_portlet.xml Quick e-Mail lcc_quickplace_portlet.xml Lotus QuickPlace lcc_quickplace2_portlet.xml Inline QuickPlace lcc_sametime_portlet.xml Lotus Sametime Connect lcc_webpage_portlet.xml Web Page
Examples: The following are example commands for deploying the Notes and Domino portlet:
- UNIX/Linux: ./xmlaccess.sh -in ../config/work/lcc_notes_portlet.xml -user wpsadmin -pwd wpsadminpwd -url myserver:80/wps/config
- Windows: xmlaccess -in ..\config\work\lcc_notes_portlet.xml -user wpsadmin -pwd wpsadminpwd -url myserver:80/wps/config
- Restart WebSphere Portal for the changes to take effect...
stopServer WebSphere_Portal startServer WebSphere_Portal
See also
Home | Support | Terms of use | Feedback
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.