Difference between revisions of "Workforce Intelligence Runtime Deployment Strategies"

From PegaWiki
Jump to navigation Jump to search
Tag: Visual edit
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{New request
+
{{Design pattern|Title=Workforce Intelligence Runtime Deployment Strategies|Description=Different options and strategies for deploying the Workforce Intelligence runtime software|Version=8.5|Applications=Pega Workforce Intelligence|Capability Area=Workforce Intelligence|Owner=Mathew, ann}}
  
|Request to Publish=Yes
+
Here are some strategies that will help your organization efficiently roll out Pega Robotic Runtime for Workforce Intelligence. Below are some client-based scenarios that offer greater flexibility and control over the entire runtime deployment process. These processes are created using Pega Robotic Runtime version 19.1.
 
 
|Curator Assigned=
 
|Description=This article describes the different options and strategies available to deploy the Workforce Intelligence runtime software.
 
|Applications=Workforce Intelligence
 
|Capability Area=Implementation
 
|Version=
 
 
 
}}
 
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓  '''<big>Please Read Below</big>'''  ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
 
 
 
Enter your content below. Use the basic wiki template that is provided to organize your content.  After making your edits, add a summary comment that briefly describes your work, and then click "SAVE".  To edit your content later, select the page from your "Watchlist" summary.  If you can not find your article, search the design pattern title.
 
 
 
When your content is ready for publishing, next to the '''"Request to Publish"''' field above, type '''"Yes"'''. A Curator then reviews and publishes the content, which might take up to 48 hours.
 
 
 
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ '''<big>The above text will be removed prior to being published</big>''' ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
 
 
 
Here are some strategies that will help your organization roll out the Pega robotic runtime for Workforce Intelligence efficiently. Mentioned below are some client-based scenarios that offer greater flexibility and control over the entire runtime deployment process. These processes are created using Pega Robotic Runtime version 19.1.
 
  
 
== Runtime Startup Strategies for Work from Home Data Collectors ==
 
== Runtime Startup Strategies for Work from Home Data Collectors ==
'''Use Case #1''' – Large number of agents now work from home which makes them highly dependent on their organization’s VPN server. In certain cases the agents may not be connected to the VPN.
+
'''Use Case #1''' – A large number of agents now work from home, which makes them highly dependent on their organization’s VPN server. In certain cases the agents may not be connected to the VPN.
  
 
'''Solution:'''  
 
'''Solution:'''  
 
* Non-VPN
 
* Non-VPN
 
# With the Workforce Intelligence 8.5 release, clients can now enable WFI Runtime Endpoint Authorization. With this feature the runtime endpoints will be authenticated securely using a client ID and client secret combination to authorize each data collector.  
 
# With the Workforce Intelligence 8.5 release, clients can now enable WFI Runtime Endpoint Authorization. With this feature the runtime endpoints will be authenticated securely using a client ID and client secret combination to authorize each data collector.  
# Single Sign On – Application users will be authenticated using clients SSO technology. In a non-VPN environment, the application users are required to enter SSO credentials. Please refer to this [https://community.pega.com/knowledgebase/articles/pega-workforce-intelligence/enabling-single-sign-workforce-intelligence-portal community article] for more information on how to enable this SSO feature.
+
# Single Sign On – Application users will be authenticated using clients' SSO technology. In a non-VPN environment, the application users are required to enter SSO credentials. Please refer to this [https://community.pega.com/knowledgebase/articles/pega-workforce-intelligence/enabling-single-sign-workforce-intelligence-portal community article] for more information on how to enable this SSO feature.
 
* VPN
 
* VPN
# Starting Runtime with a Secure Connection – By using Cisco VPN or a specific network profile on Windows, Pega robot runtime could be configured to start after a successful VPN connection. Please refer to this community article for more information.
+
# Starting Runtime with a Secure Connection – By using Cisco VPN or a specific network profile on Windows, Pega Robot Runtime could be configured to start after a successful VPN connection. Please refer to this [https://community.pega.com/knowledgebase/articles/starting-runtime-secure-connection community article] for more information.
 
# Single Sign On – Application users will be authenticated using clients SSO technology. Please refer to this [https://community.pega.com/knowledgebase/articles/pega-workforce-intelligence/enabling-single-sign-workforce-intelligence-portal community article] for more information on how to enable this SSO feature.
 
# Single Sign On – Application users will be authenticated using clients SSO technology. Please refer to this [https://community.pega.com/knowledgebase/articles/pega-workforce-intelligence/enabling-single-sign-workforce-intelligence-portal community article] for more information on how to enable this SSO feature.
  
Line 36: Line 19:
 
'''Solution:'''  
 
'''Solution:'''  
  
Add the proxy server address to route Workforce Intelligence data. To add the proxy server address, changes need to be made on the '''CommonConfig.xml''' and '''OpenSpan.Runtime.exe.config''' runtime configuration files. Consult with Workforce Intelligence Support team before adding the proxy server address. Please refer to this community article for more information.
+
Add the proxy server address to route Workforce Intelligence data. To add the proxy server address, changes need to be made on the <code>CommonConfig.xml</code> and <code>OpenSpan.Runtime.exe.config</code> runtime configuration files. Consult with the Workforce Intelligence Support team before adding the proxy server address. Please refer to this [https://community.pega.com/knowledgebase/articles/pega-workforce-intelligence/setting-proxy-server-workforce-intelligence community article] for more information.
  
 
== Mitigating the Firewall Obstacle ==
 
== Mitigating the Firewall Obstacle ==
Line 48: Line 31:
  
 
== Troubleshooting Within Workforce Intelligence ==
 
== Troubleshooting Within Workforce Intelligence ==
If all the above options have been validated and the root cause is still unknown, please refer to this community article for further troubleshooting tips.
+
If all the above options have been validated and the root cause is still unknown, please refer to this community [https://community.pega.com/knowledgebase/articles/pega-workforce-intelligence/checking-runtime-connectivity article] for further troubleshooting tips.

Latest revision as of 15:51, 13 August 2021

Workforce Intelligence Runtime Deployment Strategies

Description Different options and strategies for deploying the Workforce Intelligence runtime software
Version as of 8.5
Application Pega Workforce Intelligence
Capability/Industry Area Workforce Intelligence



Here are some strategies that will help your organization efficiently roll out Pega Robotic Runtime for Workforce Intelligence. Below are some client-based scenarios that offer greater flexibility and control over the entire runtime deployment process. These processes are created using Pega Robotic Runtime version 19.1.

Runtime Startup Strategies for Work from Home Data Collectors[edit]

Use Case #1 – A large number of agents now work from home, which makes them highly dependent on their organization’s VPN server. In certain cases the agents may not be connected to the VPN.

Solution:

  • Non-VPN
  1. With the Workforce Intelligence 8.5 release, clients can now enable WFI Runtime Endpoint Authorization. With this feature the runtime endpoints will be authenticated securely using a client ID and client secret combination to authorize each data collector.
  2. Single Sign On – Application users will be authenticated using clients' SSO technology. In a non-VPN environment, the application users are required to enter SSO credentials. Please refer to this community article for more information on how to enable this SSO feature.
  • VPN
  1. Starting Runtime with a Secure Connection – By using Cisco VPN or a specific network profile on Windows, Pega Robot Runtime could be configured to start after a successful VPN connection. Please refer to this community article for more information.
  2. Single Sign On – Application users will be authenticated using clients SSO technology. Please refer to this community article for more information on how to enable this SSO feature.

Using a Proxy Server to Route Workforce Intelligence Data[edit]

Use Case #2 – Data collectors’ data is being cached locally on their machine because Workforce Intelligence traffic is not routed through the proxy server.

Solution:

Add the proxy server address to route Workforce Intelligence data. To add the proxy server address, changes need to be made on the CommonConfig.xml and OpenSpan.Runtime.exe.config runtime configuration files. Consult with the Workforce Intelligence Support team before adding the proxy server address. Please refer to this community article for more information.

Mitigating the Firewall Obstacle[edit]

Use Case #3 – The organization’s firewall denies Workforce Intelligence data to be sent to the WFI portal.

Solution:

Ensure your security team permits the below 2 URLs within the Firewall.

  1. https://{clientName}.wfi.pega.com/
  2. https://{clientName}-ingest.wfi.pega.com/ingest/events

Troubleshooting Within Workforce Intelligence[edit]

If all the above options have been validated and the root cause is still unknown, please refer to this community article for further troubleshooting tips.