Cisco Unified MeetingPlace Release 8.0 -- Installing and Configuring Jabber with Cisco Unified MeetingPlace Release 8.0

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(5 Upgrading or Reinstalling the Jabber with Cisco Unified MeetingPlace Integration)
m (1 revision)
 

Latest revision as of 17:12, 2 July 2010

Main page: Cisco Unified MeetingPlace, Release 8.0

Up one level: Integrations



With Jabber for Cisco Unified MeetingPlace, users can initiate Cisco Unified MeetingPlace meetings from a Jabber Messenger client. The user who initiates the meeting selects meeting invitees from a list of contacts and invites them to the meeting. Each invitee receives a message (and a pop-up window) inviting them to join the meeting. By clicking on a hyperlink in the invitation message, the invitees can enter the Cisco Unified MeetingPlace meeting and have Cisco Unified MeetingPlace dial out to their phones.


Contents

1 How to Prepare to Install Jabber with Cisco Unified MeetingPlace


Reviewing System Requirements

Before installing the Jabber with Cisco Unified MeetingPlace integration, read the System Requirements for Cisco Unified MeetingPlace Release 8.0 at: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.0_--_System_Requirements_for_Cisco_Unified_MeetingPlace_Release_8.0.


Note: Cisco Unified MeetingPlace Release 8.0 supports Jabber Extensible Communications Platform (XCP) Release 5.1 only.

Gathering Installation Values

Use the following table to record the information you need to prepare for your installation.

Description Your Value

Cluster name

Note: Clusters enable your Jabber XCP server to use dynamic routing. All of the Jabber routers that you want to interact should be in the same cluster.

 

Realm name, which is a unique string used to identify the router and all of its components (i.e., the entire system). The realm name is used to distinguish between the components belonging to different Jabber XCP installations in the event that you run multiple Jabber XCP servers.

 

Hostname of your Jabber XCP server.

 

IP address of the Jabber XCP server.

Note: This must be a static IP address.

 

Port on which the Jabber router will listen for connections from all components (also referred to as the Master Accept Port).

 

Password to be used for router and component authentication.

Note: All components will use the same authentication password.

 

Staging directory, which holds files that are waiting to be scanned or that are being scanned. It also holds files that have failed the scan.

 

Final directory, which holds files that are ready for users to download.

 



The jabber License

Ensure that you have the Cisco Unified MeetingPlace jabber license. See the Planning Guide for Cisco Unified MeetingPlace Release 8.0 : Cisco Unified MeetingPlace, Release 8.0 -- Planning Your Deployment.

Setting the JABBER_HOME Environment Variable

Before you install Jabber with Cisco Unified MeetingPlace, set the JABBER_HOME environment variable for the root account on the Jabber XCP server to point to the directory in which Jabber is installed.


Procedure
  1. Sign in to the Jabber XCP server as root.
  2. Enter bash at the command line.
  3. Enter JABBER_HOME=<Path to the directory in which Jabber is installed>, where <Path to the directory in which Jabber is installed> is the path to the directory in which Jabber is installed. For example, enter JABBER_HOME=/opt/jabber.
  4. Enter export JABBER_HOME.
  5. Enter echo $JABBER_HOME. to confirm the setting.
The system displays the path to the directory in which Jabber is installed.

2 How to Install the Jabber with Cisco Unified MeetingPlace Integration

Unlike other Cisco Unified MeetingPlace integrations, the Jabber integration is installed on a standalone server and not on a Cisco Unified MeetingPlace Web Server. Perform the following steps in the order listed to install the Jabber with Cisco Unified MeetingPlace integration:


Installing the Jabber XCP Server on the Standalone Server

Before You Begin
  • Install Cisco Unified MeetingPlace. See the Installation and Upgrade Guide for Cisco Unified MeetingPlace Release 8.0.
  • Find a standalone server on which to install all the Jabber integrations. This server must have Enterprise Cisco Linux (ECS) or Red Hat Linux Release 3.0 or Release 4.0 installed on it.
  • Perform all the tasks in the 1 How to Prepare to Install Jabber with Cisco Unified MeetingPlace.


Note: In this procedure, to accept the default value at any time, press Enter.


Procedure
  1. Sign in to the standalone server as the root user.
  2. Enter ./xcp-core-installer-<Jabber version number>-linux.bin at the command line, to install all of the core Jabber XCP server components to the default location, which is /opt/jabber.
  3. Enter a cluster name for this server.
  4. Enter the realm name for this server.
  5. Enter the FQDN or hostname of your Jabber XCP server. If you enter a hostname, it must be resolvable to the IP address of the server where the Connection Manager process runs.
  6. Enter the IP address of the Jabber XCP server. This must be a static IP address.
  7. Enter a port number for the Jabber XCP component connections.
  8. Enter a password to be used for router and component authentication. All components will use the same authentication password.
  9. Enter the port number that the Jabber XCP Controller will use to listen for web browser requests.
  10. Enter root when prompted to enter the login name for the Jabber XCP Controller Administrator.
  11. Enter cisco123 when prompted to enter the password for the Jabber XCP Controller Administrator.
  12. Confirm the password.
  13. Enter n at the Configure Oracle prompt.
  14. Enter n at the Configure DB2 prompt.
  15. Enter the staging (upload) directory path for file transfers.
  16. Enter y to allow others to have read privileges for files in the staging directory.
  17. Enter the final directory path for file transfers.
  18. Enter y to allow others to have read privileges for files in the final directory.

Starting the Jabber XCP Server Controller

Procedure
  1. Enter cd /opt/jabber/bin/ to navigate to the bin subdirectory of the Jabber XCP installation directory.
  2. Enter ./runcontroller start to start the Jabber XCP Controller.
  3. Enter https://<xcp_server_IP>:<port>/admin to connect to the Jabber XCP Controller. For example, enter https://jabber.lab.pst:7300/admin.
  4. Select Accept this certificate temporarily for this session.
  5. Select OK.
    The system displays a message because you are connecting via SSL and the certificate is being signed by Jabber, Inc., which is not a certificate authority.
  6. Enter the username and the password for the Jabber XCP Controller Administrator at the login prompt.
  7. Select OK.
  8. Select start the system now on the Jabber XCP Controller System page.


Related Topics

Starting and Stopping the Jabber XCP Server

The runjabber script (which is located in the bin subdirectory of the Jabber XCP installation directory) starts and stops the Jabber XCP server. It also allows you to see the status of the server and to view or change the logging level.


Note: When you start the Jabber XCP server, all events are logged to syslog by default.


Procedure
  1. Enter cd /opt/jabber/bin to navigate to the bin subdirectory of the Jabber XCP installation directory.
  2. Enter ./runjabber start to run the runjabber script to start the Jabber XCP server.
  3. Enter ./runjabber stop to stop the Jabber XCP server.


Installing the Cisco Unified MeetingPlace for Jabber Integration

Procedure
  1. Enter chmod 775 install_jabber_<version_number>.bin to install the Jabber with Cisco Unified MeetingPlace integration.
  2. Start the Jabber XCP server.
    The system displays the Jabber XCP Controller System page.
  3. Select Cisco Broker from the Add a new list box in the Components section.
  4. Select Go.
  5. Check Cisco Unified MeetingPlace Command on the Cisco Broker Configuration page.
  6. Enter the hostname or IP address of the Cisco Unified MeetingPlace Web Server.
  7. Enter "MeetingPlace" for the MeetingPlace Server Type field.
  8. Select Submit.
    The system displays the System page. In the Components section, the cisco component should be red.
  9. Select Restart the system.
  10. Select Start to activate the cisco component.


Related Topics

3 Configuring the Jabber with Cisco Unified MeetingPlace Integration

This section describes how to configure Jabber with Cisco Unified MeetingPlace on a Jabber XCP server so that users can initiate Cisco Unified MeetingPlace meetings from a Jabber Messenger client. You have the option to configure Secure Sockets Layer (SSL) to implement security between Cisco Unified MeetingPlace and the Jabber XCP server. Use SSL to provide secure transmission of data across the network through the use of public or private key encryption.


Configuring Jabber

You must configure Jabber so that users can initiate Cisco Unified MeetingPlace meetings.


Before You Begin
Procedure
  1. Locate the Components section.
  2. Locate the Add a New list.
  3. Select Cisco External Command Interface.
  4. Select Go.
    The system displays the Cisco External Command Interface Configuration window.
  5. Scroll to the Cisco Unified MeetingPlace Command Configuration section.
  6. Enter the hostname or IP address of the Cisco Unified MeetingPlace Web Server.
  7. Choose MeetingPlace from the MeetingPlace Server Type list.
  8. Select Submit.
  9. Locate the Cisco External Command Interface component that you added.
  10. Locate the Actions column.
  11. Select Start.

(Optional) How to Configure SSL


Entering the Cisco Unified MeetingPlace Web Server Certificate Files in the Jabber Server Keystore

Before You Begin
  • Sign in to the Jabber XCP server as root.
  • Configure SSL on the Cisco Unified MeetingPlace Web Server. See the Configuration Guide for Cisco Unified MeetingPlace Release 8.0 or the online help in the administrator interface for information about configuring SSL.
  • Copy the certificate file from the Cisco Unified MeetingPlace Web Server to the Jabber XCP server. The certificate file is for Hostname [Home Page] and ends in .cer.
  • Obtain the hostname or IP address of the Cisco Unified MeetingPlace Web Server.
  • Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.


Procedure
  1. Open a command line interface.
  2. Enter keytool -import -alias "CiscoMeetingPlaceHomePage" -file <Certificate File for Hostname [Home Page]> -keystore <Keystore Location>, where <Certificate File for Hostname [Home Page]>' is the name of the certificate file for the Hostname [HomePage] and <Keystore Location> is the value for the -keystore parameter.
    Note: The -keystore parameter specifies a file that holds the keystore. If you do not specify a full path, the keystore is created in the directory in which you run the keytool command.
  3. Enter a password for the keystore.


Configuring SSL for Cisco Unified MeetingPlace on the Jabber Server

Before You Begin
  • Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.


Procedure
  1. Locate the Cisco External Command Interface component.
  2. Select Edit.
    The system displays the Cisco External Command Interface Configuration page.
  3. Choose Intermediate from the Configuration View list box.
  4. Locate the Cisco Unified MeetingPlace Command area.
  5. Select SSL Configuration in the External Command Integration Configuration area.
  6. Enter the information from Step 1 of the Entering the Cisco Unified MeetingPlace Web Server Certificate Files in the Jabber Server Keystore in Full Path to SSL Key File.
  7. Enter the information from Step 3 of the Entering the Cisco Unified MeetingPlace Web Server Certificate Files in the Jabber Server Keystore in Password for SSL Key File.
  8. Select Submit.
  9. Go to the Jabber XCP Controller home page.
  10. Locate the Components area.
  11. Locate the Cisco External Command Interface component that you just added.
  12. Select Start.

4 How to Troubleshoot Jabber with Cisco Unified MeetingPlace


Component Does Not Start After Adding Cisco External Command Interface Component

Problem: The Cisco External Command Interface component does not start after adding it to the Jabber XCP Controller.

Solution: This problem can occur if an incorrect version of Java is installed on the Jabber XCP server, or if an incorrect path is specified for the Java executable or the meetingplace.jar file in the Cisco External Command Interface configuration.


For information about the version of Java required for Jabber, see the System Requirements for Cisco Unified MeetingPlace : Cisco Unified MeetingPlace Release 8.0 -- System Requirements for Cisco Unified MeetingPlace Release 8.0.


Before You Begin
  • Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.


Procedure
  1. Locate the Cisco External Command Interface component.
  2. Select Edit.
    The system displays the Cisco External Command Interface Configuration window.
  3. Choose Intermediate from the Configuration View list box.
  4. Ensure that the value for Command in the Router Connection Information area is correct.
  5. Ensure that the value for the Java path is correct. The value appears after "exec" in the command.
  6. Ensure that the value for the meetingplace.jar file is correct. The value appears after "-jar" in the path.
  7. (Optional) Copy the text from this field.
  8. (Optional) Paste the text into a console to attempt to run the component.
  9. Select Submit.


Clients Response is Slow When Attempting to Join a Meeting

Problem: Jabber Messenger clients experience slow response time when attempting to join a meeting, or when inviting users to a meeting.

Solution: If the response time between the Jabber Messenger client and Jabber is too long, users might think their Jabber client has hung while it is waiting for a response from the Jabber XCP server. The default time period is 300 seconds (five minutes). You can adjust this time period by completing the following procedure.


Before You Begin
  • Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.


Procedure
  1. Locate the Cisco External Command Interface component.
  2. Select Edit.
    The system displays the Cisco External Command Interface Configuration window.
  3. Choose Intermediate from the Configuration View list box.
  4. Enter a new value in seconds for the Command time-out (secs) field in the External Command Integration Configuration area.
  5. Select Submit.


Collecting Log Files

You can collect console information from the Jabber Messenger client and logs from the Jabber XCP server to help diagnose problems. If you report a problem to Cisco TAC, you might need to send the logs to them.


In the Jabber Messenger client, the Console tab lists the XML messages that pass between the client and the Jabber XCP server. To access the message list from the Jabber Messenger menu, click View > Console to enable the console.


On the Jabber XCP server, you can enable diagnostic logs from the Jabber XCP Controller web interface.


Before You Begin
  • Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.


Procedure
  1. Locate the Cisco External Command Interface component.
  2. Select Edit in the Actions column.
    The system displays the Cisco External Command Interface Configuration window.
  3. Choose Intermediate from the Configuration View list box.
  4. Locate the External Command Configuration area.
  5. Locate the Cisco Unified MeetingPlace Command area.
  6. Choose Verbose from the MeetingPlace Level Filter list box.
  7. Make a note of the value of the file name parameter under Java component logging. This is the location where log will be written.
  8. Select Submit.

5 Upgrading or Reinstalling the Jabber with Cisco Unified MeetingPlace Integration

To upgrade or reinstall the Jabber with Cisco Unified MeetingPlace integration, perform these tasks.

Step Action See

1

Stop the cisco component.

Stopping the cisco Component

2

Add the jabber license for Jabber with Cisco Unified MeetingPlace to the Cisco Unified MeetingPlace Application Server.

The jabber License

3

Set the JABBER_HOME environment variable.

Setting the JABBER_HOME Environment Variable

4

Install Jabber with Cisco Unified MeetingPlace.

2 How to Install the Jabber with Cisco Unified MeetingPlace Integration

6 How to Uninstall the Jabber with Cisco Unified MeetingPlace Integration


Stopping the cisco Component

Procedure
  1. Start the Jabber XCP Server Controller.
    The system displays the Jabber XCP Controller System page.
  2. Locate the cisco component in the Components section.
  3. Select Stop in the Actions column.


Related Topics


Removing the cisco Component

Procedure
  1. Stop the cisco component.
  2. Select Remove in the Remove column.


Related Topics


Gathering Values for Uninstalling Jabber with Cisco Unified MeetingPlace

Gather the following values, which are used in the Deleting the Jabber with Cisco Unified MeetingPlace Integration Files.

Parameter Your Value

Installer source file directory


The directory that contains the installer source files.


Example: /opt/jabber

 

JAR file directory


The ./lib/cisco subdirectory of the directory that contains the installer source files.


Example: /opt/jabber/lib/cisco

 

Cisco JIG configuration directory


The ./schemas/jig/config/cisco subdirectory of the directory that contains the installer source files.


Example: /opt/jabber/schemas/jig/config/cisco

 

Cisco XSD configuration directory


The ./schemas/xsd/config/cisco subdirectory of the directory that contains the installer source files.


Example: /opt/jabber/schemas/xsd/config/cisco

 



Deleting the Jabber with Cisco Unified MeetingPlace Integration Files

Before You Begin


Procedure
  1. Sign in to the Jabber XCP server as root.
  2. Enter rm -rf <JAR file directory>.
  3. Enter rm -rf <Cisco JIG configuration directory>.
  4. Enter rm -rf <Cisco XSD configuration directory>.


Removing the cisco Component Reference from the Jabber.Jig File

Procedure
  1. Sign in to the Jabber XCP server as root.
  2. Locate the jabber.jig file (for example, /opt/jabber/schemas/jig/config/jabber/jabber.jig).
  3. Use a text editor to open the jabber.jig file.
  4. Find and remove the following line of text: <xi:include xi:href="${JABBER_HOME}/schemas/jig/config/cisco/cisco.jig" level="base"/>
  5. Save and close the jabber.jig file.

Rating: 0.0/5 (0 votes cast)

Personal tools