Plants By WebSphere Ajax Sample Application Installation, Setup and Configuration WebSphere Application Server v8.0

Transcription

1 Plants By WebSphere Ajax Sample Application Installation, Setup and Configuration WebSphere Application Server v8.0 Tibor Beres Software Engineer WebSphere Application Server SIP Testing IBM Software Group, Application and Integration Middleware Software May 2011 Copyright International Business Machines Corporation All rights reserved. Summary: This paper describes necessary steps for the installation, setup, and configuration of a WAS v8.0 environment with Plants By WebSphere Ajax Sample Application installed. It also demonstrates the Communications Enabled Communications (CEA) widgets built into the Plants By WebSphere Ajax Sample Application. 1

2 Plants By WebSphere Sample Application Installation, Setup and Configuration WebSphere Application Server v8.0 Prerequisites: WebSphere Application Server v8.0 (WAS80) driver installed on Linux systems. Sample applications for Communications Enabled Applications by IBM Rational Application Developer for WebSphere Software v8.0 (RAD 8.0) or later Sample PBX application or access to an external IP-PBX server. X-Lite and Express Talk soft-phone software installed on a Windows environment. This document presumes you have already installed the WAS v80 driver and you have created an ND environment with the following configuration: 1 Deployment Manager (DMGR) 3 managed nodes (for the external IP-PBX server you can also create a standalone WAS 80 server, outside of the ND environment. In this exercise we will create a PBX server as part of the ND cell). It also presumes you have already installed RAD 8.0 and you have X-Lite and Express Talk soft-phones installed on a separate Windows environment. As first step, set administrative console preference to automatically synchronize managed nodes after making changes, so you won t have to manually synchronize all nodes after each executed step. Navigate to System administration > Console Preferences Check the box next to Synchronize changes with Nodes. Click Apply. 2

3 Decision Point: you can create an application server (AS) on a managed node and apply tuning to it, then convert the application server into an application server cluster OR you can create an empty application server cluster and add application servers to the cluster as needed OR you can create an application server server, apply some tuning to it, create an application server cluster using this server as a template and add additional members to the cluster as needed Points to take into consideration when making this decision: Creating an application server first and applying most/all of the necessary tuning, then converting this application server into a cluster can save you time, as all the tuning parameters are saved on the cluster level, and will be inherited by all application servers added to the cluster later on. On the other hand, if your hardware differs from node to node, you might end up in a situation where you have saved incompatible tuning on the cluster level, making it 3

4 impossible to expand the cluster due to managed nodes running on inferior/incompatible hardware/software. In this example we will demonstrate the third approach. We will create one application server (the server to be used as IP-PBX) and we will apply all the tuning needed for running Communications Enabled Applications widgets. Once tuning is complete we, will create an application server cluster using the tuned application server as a template. Then we will add additional servers to the cluster, as needed. In final step we will create a SIP proxy server to front the application server cluster. Step 1: Create application server to be used as IP-PBX on a managed node Navigate to the following panel: Servers > Server Types > WebSphere application servers. Click New Select your managed node and provide a server name (for example PBX) on the Select a node panel. Choose the default WebSphere server template on Step2: Select a server template panel 4

5 Click Next. Follow default steps and create a new application server on managed node. Save your changes directly to the master configuration. Step 2: Tune application server for performance Minimum tuning for running applications taking advantage of the Communications Enabled Applications offered functionalities involves setting JVM properties and increasing the HTTP timeout on the web container. Specifying the interfaces to be used for HTTP and SIP transports can also be useful when the system has more than one NIC. You can also consider increasing the heap size and creating a dedicated thread pool to be used by the SIP container. Set JVM properties: Navigate to the following panel: Application Servers > [servername] > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties Click New Enter com.ibm.websphere.webservices.http.connectiontimeout for Name. Enter 2400 for Value. 5

6 Click OK Click Java Virtual Machine in the navigational breadcrumbs, as seen below, to access the JVM settings. You could also access the same panel by navigating to: Application Servers > [servername] > Java and Process Management > Process Definition > Java Virtual Machine 6

7 Set Initial heap size to 1024 MB Set Maximum heap size to 1024 MB. Click OK. Save your changes to the master configuration. Increase HTTP timeout on the HTTP transport chain. Navigate to Servers > Server Types > WebSphere application servers > [servername] > Web Container Setting > Web container transport chains > WCInboundDefault > HTTP inbound channel (HTTP 2) Change the following timeout values: Read timeout set to 2400 seconds Write timeout set to 2400 seconds Persistent timeout set to 2400 seconds 7

8 Click OK Save your changes to the master configuration. Define HTTP and SIP interfaces: Navigate to Servers > Server Types > WebSphere application servers > [servername] > Communications > Ports Click on SIP_DEFAULTHOST Change the host to the IP address of the host or to the hostname. If using hostname it is recommended using the fully qualified host name, such as svtr1c1b08a.rtp.raleigh.ibm.com. In this document we will be using IP addresses throughout. 8

9 Click OK Also set WC_defaulthost to IP (or hostname). Click OK Save your changes to the master configuration. Add <IP address>:<port> combinations to the list of virtual hosts: Navigate to Environment > Virtual hosts > default host > Host Aliases Add the <IP address>:<port> (or <hostname>:<port>) combination for SIP_DEFAULTHOST to the list of virtual hosts. o Click New o Enter the IP address for Host Name o Enter the corresponding port for Port 9

10 Click OK Add the <IP address>:<port> (or <hostname>:<port>) combination for WC_defaulthost to the list. o Click New o Enter the IP address for Host Name o Enter the corresponding port for Port o Click OK. Save your changes to the master configuration. Create thread pool to be used by SIP container. Navigate to Servers > Server Types > WebSphere application servers > [servername] > Thread pools Click New Enter SIPContainerPool for Name Enter 100 for Minimum Size Enter 100 for Maximum Size Leave the other fields with default settings. 10

11 Click OK Navigate to Servers > Server Types > WebSphere application servers > [servername] > SIP Container Settings Click on SIP container Select SIPContainerPool from the list of available pools in the Thread pool drop down list 11

12 Click OK Save your changes to the master configuration. At this point additional tuning can be added, if desired, such as node agent monitoring policy, trace and log settings, additional JVM parameters, etc. Please remember that all these settings will also be saved on cluster level since we will be using this server as a template when creating the application server cluster. Step 3: Create application server cluster Create a new application server cluster by using the existing PBX application server as a template: Navigate to Servers > Clusters > WebSphere application server clusters 12

13 Click New Provide Cluster name Leave the check box for Configuring HTTP session memory-to-memory replication blank for now. You can configure replication settings later on application server level if desired (steps for configuring replication are not included in this documentation). Fill in the Member name. Select the node you want the server installed on. Select Create the member by using an existing application server as a template and select the PBX application server. 13

14 Click Next At this point you can add additional members to the cluster or you can click Next. Click Finish on the Summary page. Save your changes. Step 4: Add additional application servers to the application server cluster. Navigate to Servers> Clusters > WebSphere application server clusters Click on the cluster-name. Click on Cluster members under Additional Properties 14

15 Click New Define the server name and select the node you want the new application server to run on. Leave the Generate unique HTTP ports checkbox selected (default setting). Click Add Member. Add 2 more servers by repeating the previous step, for a total of 4 application servers in the cluster, 2 application servers per node. 15

16 Click Next, then click Finish on the Summary page. Save your changes to the master configuration. Add SIP and HTTP transport chain:<port> combinations to the list of virtual hosts. Navigate to Servers > Server Types > WebSphere application servers > [servername] > Communications > Ports Make a note of the SIP_DEFAULTHOST and WC_adminhost <IP address>:<port> (or <IP address>:<port>) values. Notice that since the tuned application server was used as a template when creating the application server cluster, the SIP_DEFAULTHOST and WC_defaulthost ports were bound to 16

17 hostname, instead of the default *. You can leave them as hostname or replace them with IP addresses. In this exercise we will bound everything to IP address for simplicity. o Click on SIP_DEFAULTHOST 17

18 o Replace the host name under Host with the IP address you want the SIP chain to listen on o Click on WC_defaulthost o Replace the host name under Host with the IP address you want the inbound HTTP chain to listen on o Click OK. Navigate to Environment > Virtual hosts > default host > Host Aliases Add the <IP address>:<port> (or <hostname>:<port>) combinations for SIP_DEFAULTHOST and WC_defaulthost to the list as described above in Step 2. Repeat above steps for all the application servers in the cluster and add the <IP address>:<port> (or <hostname>:<port>) combinations for SIP_DEFAULTHOST and WC_defaulthost to the list of virtual hosts. Save your changes to the master configuration. Step 5: Enable Communication Enabled Applications (CEA) on the application server cluster Navigate to Servers> Clusters > WebSphere application server clusters Click on the cluster-name. Click on Communications Enabled Applications (CEA) under Communications. 18

19 Click the check box next to Enable communications services Select Use SIP CTI (ECMA TR/87) gateway for telephony access if not selected and provide the IP address (or hostname) of the IP-PBX. Specify the SIP port of the PBX for Port. In this scenario we will be using the PBX server created in Step 1, therefore we have to enter the values for the SIP transport chain as set in Step2 ( for Host name or IP address and 5062 for Port). Select UDP for Protocol 19

20 Click OK. Save your changes to the master configuration. Step 6: Create SIP Proxy server Application servers must be fronted by a proxy server. Navigate to Servers > Server Types > WebSphere proxy servers Click New Select target node and provide proxy server name. Click Next. Take default settings on the Specify server specific properties panel. 20

21 Click Next. Default for server template. Click Next. Click Finish on the Confirm new server page. Save your changes. Step 7: Configure SIP proxy server to front the application server cluster: Navigate to Servers > Server Types > WebSphere proxy servers > [ProxyName] >SIP Proxy Server Settings > Sip proxy settings Select the application server cluster as Default cluster from the drop down menu Click OK. Save changes to the master configuration. 21

22 Step 8: Tune proxy server On a minimum you should increase HTTP proxy timeout to 2400 seconds and specify the SIP and HTTP interfaces to be used by the proxy. Increase HTTP timeout on proxy: Navigate to Servers > Server Types > WebSphere proxy servers > [ProxyName] > HTTP Proxy Server Settings > Proxy server transports Click on HTTP_PROXY_CHAIN Click on HTTP_inbound_channel_(HTTP_3) Set Read timeout to 2400 Set Write timeout to 2400 Set Persistent timeout to 2440 Click OK Save your changes to the master configuration. Specify the interface used for HTTP and SIP transports: Navigate to Servers > Server Types > WebSphere proxy servers > [ProxyName] > Ports Click on PROXY_SIP_ADDRESS Change the host to the IP address of the host (or to hostname) 22

23 Click OK. Click on PROXY_HTTP_ADDRESS Change the host to the IP address of the host (or to hostname) Click OK Save your changes to the master configuration. Add the proxy server SIP and HTTP <interface>:<port> values to the environment s virtual hosts: Navigate to Environment > Virtual hosts > default_host > Host Aliases o click New o enter the corresponding values for SIP o click OK o click New o enter the corresponding values for HTTP o click OK Save changes to the master configuration. Step 9: Install sample PBX application on the PBX server: Navigate to Applications > Application Types > WebSphere enterprise applications Click Install Browse to the sample commsvc.pbx.ear application Click Next Choose Fast Path Prompt only when additional information is required. Click Next. Take default installation options. Click Next. 23

24 Ensure that the PBX server is specified as the target server on Map modules to servers panel. If not, select the CSTASipPbx module, select the PBX server listed under Clusters and servers and click Apply Click Next Click Finish on the Summary page Ensure Application commsvc.pbx installed successfully is printed on the feedback screen. Save your changes to the master configuration. At this point the PBX server is fully configured to accept register messages from phones. Start the PBX server. Ensure that the server starts up error free and that the commsvc.pbx application started up successfully (the SystemOut.log prints out Application started: commsvc.pbx). Step 10: Work with the Plants by WebSphere Ajax Sample Application: 1) Import the Plants by WebSphere Ajax sample application into RAD Open RAD 8.0 Select File > Import. Then select Java EE > EAR file. Click Next. On the Import page select Browse and locate the PlantsByWebSphere.ear sample application for WAS 8.0 Make sure the Target runtime is set to WebSphere Application Server v

25 Select Finish. 2) Edit / note widget related html content The Click To Call widget code is on the contactus.html web page. Expand WebContent under PlantsByWebSphere_WEB Locate contactus.html under WebContent and double click it. The page will load in the viewer. Click Source to view the source code. Locate and edit the phone number that the customer will call when he activates Click To Call - it is the value associated with widgetnumber. By default it is - widgetnumber= sip:csr@localhost. CSR is the name of the soft-phone representing the customer service representative and localhost is the host name or IP address of the PBX. If running an IP_PBX application then localhost is the hostname or IP address of the IP-PBX host. Please note that you can change the customer service representative phone name if you want. In our example setup the IP-PBX is listening on , as set up in the Step 2: Tune application server for performance section of this document. 25

26 Save your changes to contactus.html. The Call Notification widget code is included on the callnotification.html page. Expand WebContent under PlantsByWebSphere_WEB Double click callnotification.html and view the source code. Add the phone number corresponding to the customer service representative to the call notification widget using the following syntax: widgetnumber= (please see screenshot below). CSR is the name of the soft-phone representing the customer service representative and localhost is the host name or IP address of the PBX. If running an IP_PBX application then localhost is the hostname or IP address of the IP-PBX host. Please note that you can change the customer service representative phone name if you want. In our example setup the IP- PBX is listening on , as set up in the Step 2: Tune application server for performance section of this document. Save your changes to callnotification.html 3) Export the application: Select File > Export Select Java EE > EAR file, then Next. 26

27 Make sure PlantsByWebSphere is the EAR project value and select Browse. Select a location where you want to save the new application. Make sure the Target runtime is filled out for WebSphere Application Server V8.0 Beta. Click Finish. 4) Deploy the application on the target node: In order to generate deployment bindings between the Enterprise Java Beans and the application server, we will run the ejbdeply deployment tool provided with WebSphere Application Server. Move the exported application on the target machine into a working directory in this example we used the /tmp directory. Open a command window and navigate to <WAS_HOME>/bin Invoke the ejdeploy tool. The general syntax is EJBDeploy inputear workingdirectory outputear [options]. Run the following command:./ejbdeploy.sh PlantsByWebSphere.ear <working directory> PlantsByWebSphere_deployed.ear dbvendor DERBY_V10 Sample output from running the command can be seen below: [root@svt-r1c1b08a ~]# cd /opt/was80/bin [root@svt-r1c1b08a bin]#./ejbdeploy.sh /tmp/plantsbywebsphere.ear /tmp /tmp/plantsbywebsphere_deployed.ear -dbvendor DERBY_V10 27

28 Starting workbench. EJB Deploy configuration directory: /opt/was80/profiles/dmgr/ejbdeploy/configuration/ framework search path: /opt/was80/deploytool/itp/plugins build: RAD801-I _1439 Creating the project.. Writing output file Shutting down workbench. EJBDeploy complete. 0 Errors, 2 Warnings, 0 Informational Messages [root@svt-r1c1b08a bin]# 5) Configure the connection to the Derby database to be used by the application Create a connector to the Derby database (Derby v10 is shipped with WebSphere Application Server v8). Navigate to Resources > JDBC > JDBC Providers. Select the application server cluster for scope. Click New For Database type select Derby For Provider type select Derby Network Server Using Derby Client 40 (you must use a Network Server in a clustered environment). For Implementation type select XA data source 28

29 For Name type: Derby Network Server for Plants By WebSphere Click Next. Click Finish on the Summary page. Save your changes directly to the master configuration. Create a data source associated with the with the new JDBC provider. Navigate to Resources > JDBC > Data sources Select the scope omega2-cluster. 29

30 Click New to create a new data source. Enter PLANTSDB for Data source name Enter jdbc/plantsbywebsphereajaxdatasource for JNDI name. Click Next. Select an existing JDB provider select the Derby Network Server for Plants By WebSphere created in the previous step. 30

31 Click Next. For the Database name enter: ${APP_INSTALL_ROOT}/${CELL}/PlantsByWebSphereAjax.ear/Database/PL ANTSDB. Mark the check box Use this data source in container managed persistence (CMP) if not marked. Click Next until you reach the summary page. Click Finish. Save your changes to the master configuration. 31

32 As security is enabled by default on Derby, login information has to be defined in order to access the newly created Data Source. First you ll have to define the authentication parameters. Navigate to Resources > JDBC > Data sources Click on the PLANTSDB Data source you created in the previous step. Click the JAAS J2C authentication data hyperlink under Related Items Click New Specify an Alias to identify the profiles for example Derby Connection Default User id is APP Default Passwords is Password Click OK Save your changes to the master configuration. 32

33 Enable your data source connection to use the JAAS J2C authentication data Navigate to Resources > JDBC > Data sources Click on the PLANTSD Data source In the bottom section of the page, under Security settings o select dmgr/derby Connection for Authentication alias for XA recovery. o Select dmgr/derby Connection for Component-managed authentication alias Click OK Save your changes to the master configuration. 6) Install the deployed application Navigate to the following panel: Applications > New Application > New Enterprise Application Click Remote file system. Browse to the newly created PlantsByWebSphere_deployed.ear file. Click the check-box next to PlantsByWebSphere_deployed.ear, click OK 33

34 Click Next. Select Fast Path Prompt only when additional information is required. Click Next. Leave default installation options. Click Next. Ensure the application server cluster is listed as target server on Map modules to servers panel. If not o select both modules of the application o select the application server cluster under Clusters and servers o click Apply 34

35 Click Next. Click Finish on the Summary page. Ensure that the message Application PlantsByWebSphereAjax installed successfully is printed on the feed-back screen. Save changes directly to the master configuration 35

36 Step 11 : Configure Soft-phones to register as Customer Service Representative (CSR) and as Customer Configure the X-Lite soft phone to register as CSR. Click the down arrow to open up the X-Lite soft-phone menu. Click SIP Account Settings Click Add 36

37 On the Properties of Account1 screen: o Enter CSR for Display Name o Enter the user name hardcoded in the Call Notification widget in Plants By WebSphere for User name. In this test example we have left the default value of CSR. o Enter the hostname or IP address of the PBX for Domain. In this test example the IP-PBX is listening on host o Enter the <hostname>:<port> combination into the proxy field under Domain Proxy if the PBX is listening on a different port than the default In this test example the PBX is listening on port 5052 o Leave the default value for Dialing plan 37

38 Click OK Click Close on SIP Accounts screen. The X-Lite soft-phone will try to register as CSR in the IP-PBX server. You can verify if the connection was successful by enabling com.ibm.ws.cti.*=all runtime tracing on the PBX server or by running packet capture software on the PBX server and filtering for SIP. You should see the REGISTER messages sent by the X-Lite phone as well as the 200 OK sent back by the IP-PBX. Configure Express Talk soft-phone to register as Customer Click Options Click the Lines tab o Enter Customer for Full Friendly Display Name o Enter the PBX hostname or IP address for Server (SIP Proxy or Virtual PBX). In this test setup the IP-PBX is listening on o Enter Customer for SIP Number (or User Name) o IF the IP-PBX is listening on a different port than default 5060 click Advanced Line Settings Select Use a different outbound server and enter the hostname:port or IP address: port combination of the PBX. In this test setup the IP-PBX is listening on :

39 Click OK o Click OK on the Options screen The Express Talk soft-phone will restart and will try to register in the IP-PBX as customer, If registration was successful it will display a confirming message: Registered as sip:customer@

40 Step 12 : Start up the test environment Start the Derby Network Server first. Open a command line window on both of the managed nodes and navigate to <WAS_HOME>/derby/bin/networkServer Start the Derby Network Server by issuing the startnetworkserver.sh command Ensure you can connect to the defined Data Source: Navigate to Resources > JDBC > Data sources Select PLANTSDB by clicking the check box next to it Click Test connection 40

41 Start up the proxy server. Start up the application server cluster. Ensure there are no error messages in the server logs and that all processes started up successfully. Step 13 : Test the CEA widgets integrated into the Plants by WebSphere Ajax application Access the user interface of PlantsByWebSpere by going to this URL: server hostname OR IP address>:<http port>/plantsbywebsphereajax/ (in this example 41

42 In order to test the Two Way Form widget, you will have to create an account and log in. Click LOGIN. On the Login or Register screen click register for your own account here. Fill in all required fields. o Enter jsmith@us.ibm.com for address o Enter Password for Password o Enter John for First Name o Enter Smith for Last Name o Enter 1 IBM Drive for Address Line 1 o Enter Durham for City o Enter NC for State o Enter for Zip Code o Enter for day time phone number Click Register. The page will reload and the LOGIN will change to display LOG OUT JOHN Start a new browser and open another connection to PlantsByWebSphere. Please use a different browser and not a new tab or a new window of the previously used browser. For 42

43 example, you can use one instance of Internet Explorer and one instance of Firefox for the two sessions. Create another login for CSR or Operator. Once logged in, this session will become the customer service operator s (CSR) session. Once logged in one both browsers, access the call notification widget by clicking on Call Notification or by appending callnotification.htlm to the URL (for example in the CSR browser. The Call Notification widget will display in your browser: Click the Telephone icon to activate the Call Notification widget. The icon will change to a blue square and the text Available will be displayed under the icons. Access the Click To Call widget on the customer browser by clicking on Contact Us or by appending contactus.html to URL. Enter the phone number of the soft-phone registered as Customer in the IP-PBX into the Click To Call widget and click Call Me. 43

44 The Operator phone will ring first. Pick up the phone. The Customer phone will ring next. Answer the phone and the call between Operator and Customer will be established. Both soft-phones will display that the call was established, as seen in the screenshots below: o Operator phone: o Customer phone: 44

45 The Call Notification widget will display that the call has connected and the End Call and CoBrowse icons will be activated in the widget: The Click To Call widget will also display a Connected message, and the End Call and Cobrowse buttons will be activated. 45

46 Test the Co-Browsing functionality by clicking on the corresponding widgets in both of the browser windows. Both browsers will load the Plants By WebSphere index page and both windows will display the Peer Window is Open message. One of the windows will have all of the co-browse toolkit (Send Page, Follow Me, Grant Control and Highlight) active and will display Controlling Navigation see screenshot below. Click Highlight and highlight the header section of the page. The highlighting will display in the peer window. Switch to the peer window, click Highlight and highlight another area of the page. The corresponding highlight will display in the peer window see screenshot below. 46

47 Click on Grant Control to transfer the control from one browser window to the other. Click Follow Me inside of the controlling window. Click Flowers. Both browsers will load the Flowers page. Click Vegetables. Both browsers will load the Vegetables page. Highlight one of the items in the active window. Highlight the price in the peer window to demonstrate that highlighting works after control was transferred. Click Grant Control to transfer control back. Click Send Page in the controlling session. Both browsers will re-load the index page. Test the Two Way Form: Ensure that the customer s browser is the one controlling the session. Click Follow me. Click Check Out in both browsers, so that the Two Way Form appears on both browser windows. You can ignore the Access restrictions prevented peer from following the last actions and the Unable to follow one or more actions of peer Waiting for peer to send current page errors, as long as both browsers display the checkout form. Fill in the required fields in the customer s browser. As you fill in the values, the corresponding fields are being populated in the CSR session, accompanied by special icons ( ), enabling information validation from the CSR. 47

48 Once you filled out all values, accept or deny the customer entered values from the CSR browser. The CSR can accept the values by clicking on the green check mark. A green check mark will appear on the customer side, signaling that the entered value was accepted. The CSR can reject the entered information by clicking on the red x. The red x will signal the customer that the information was not accepted. The customer will then can provide new information for validation. Accept all values provided by the customer. Switch back to the customer browser and click Submit Order. The CSR browser will not update due to a limitation built into the PlantsByWebSphere sample application. The customer browser will load the Review Your Order page. Click the Submit Order button to complete the transaction. 48

49 Terminate co-browsing by closing the windows. Terminate the call by clicking End Call in one of the browser windows. Log out from both browser sessions. Test co-browsing outside of a call: Access the PlantsByWebSphere application home page running on another server on the same node. Log in with the same user IDs (CSR and Customer). Click Cobrowse. The Co-browsing widget will load. Click on the Create button to create an invitation link for a collaboration session. Copy the created URL and paste it in the other browser window. A collaboration session will be established establish where you can perform the same operations you performed earlier when co-browsing inside of a call. You can highlight, follow the peer partners browsing and transfer control. Perform the same steps of adding an item to the shopping cart, accessing the check-out page and finishing the transaction. Terminate the co-browsing by closing the windows and clicking the End Collaboration Session button. 49

50 Access the Plants by WebSphere application running on an application server on the other node. Create new logins. Ensure you can establish a co-browsing session inside of a call. Ensure you can establish co-browsing outside of a call. Ensure highlighting, granting control and the follow me functions work when cobrowsing. Known restrictions in Plants By WebSphere sample application: When co-browsing, the peer window cannot follow the login procedure. The browsers will display the following error messages: The controlling browser will display the Access restrictions prevented peer from following the last action error message. The peer browser will display Unable to follow one or more actions of peer Waiting for peer to send current page error message 50

51 In order to test the Two Way Form, one has to log in prior to starting co-browsing and has to click on the Check Out button in both browsers while logged in, as described above in this document. 51

52 When co-browsing, the peer window cannot follow items added to the shopping cart. If attempted, the Unable to follow one or more actions and the Access restrictions error messages will display, as described previously. The items in the shopping cart do not transfer to the peer session, as illustrated in the screenshot below. The Click To Call, Call Monitoring and Co-browse widgets are disabled inside of a cobrowsing session. The Feature cannot be used within a Web collaboration session error message will display if trying to access these widget within a co-browsing session. You can exit this error state by clicking the Home link in the upper right corner of the controller browser window. 52