Jack Henry & Associates, Inc. Xperience Technologies ...

© 2018 Jack Henry & Associates, Inc.®1 © 2018 Jack Henry & Associates, Inc.®

Xperience Technologies Rollout –

A Deeper Look at Xperience Workstations

Jack Henry & Associates, Inc.®

© 2018 Jack Henry & Associates, Inc.®2

Legal Disclaimer: Dates contained in this presentation are

provided as estimates only and can be changed at any time

at the sole discretion of Jack Henry & Associates, Inc. This

information may not be incorporated into any contract and

should not be relied upon in making purchasing decisions.HANK YO FOR THE

OPPORTUNITY TO

SHARE JHA’S STORY


Agenda

• Overview

• Server Configuration for Deployment

• Workstation Setup

• User Setup

• Troubleshooting/Resources

© 2018 Jack Henry & Associates, Inc.®4 © 2018 Jack Henry & Associates, Inc.®

Overview


Overview

• Components

– Workstation, Integration Server, iSeries

– Communication Diagram

• Framework vs. Product

• Packages


Core Xp Client

Integration Farm

iSeries Integration Providersex: Synergy

Communication

1. User launches Xperience™ Client

2. Handshake with Integration Servers

– User authentication for Xp

– Synchronization of packages

– Retrieval of themes, favorites links

3. User launches Core Xperience™

– Core authenticates using Network Authentication

– Core data is retrieved directly from the core

4. Integration servers are used to connect to data providers

1

2

34

Core


Framework vs. Products• Framework

provides navigation, themes, favorites, and is the portal to the products

• The products reside in the Framework as packages and appear in the Products listing


Packages

Interface updates utilize

Packages

– Compressed File

– 40-80MB in size

1. Deployed to a central

server

2. Downloaded to clients

Xperience Server (XS)Xperience Help System (XHS)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

WAN

Branch A

Branch B

1

22

2


Xperience Package – Frequency of Updates

• Core Xperience creates a Generally Available (GA) release every quarter

• As you work with support you may identify issues or enhancements

• Interim releases allow for quick access to updated functionality

© 2018 Jack Henry & Associates, Inc.®10© 2018 Jack Henry & Associates, Inc.®

Server Configuration


Server Configuration for Deployment

• Instance Options

– Authentication

– Closed Environment

• Pre-deployment

• Xp Deployment Services


Configuration Options

• Authentication Method – Options are User Name or Windows. If

Windows is selected, Xperience attempts to use the credentials of the currently logged on Windows® user.

– If this authentication fails, Xperience will fail over to User Name. With the User Name option, the logon prompt always displays asking for the logon name, password, and domain.

• Closed Network – A Yes or No value indicating if outside

access is limited for this instance.


Xperience™ Package Deployment

• Pre-deployment

reduces strain

– Default mode requires

Xperience™ to be

open

– Xperience™ Client

Agent (XCA) updates

overnight

• Package download

can be throttled


(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

WAN

Branch A

Branch B


Deployment Settings

• Install Path

• “Throttle” Deployment


Monitor Deployments

Console allows monitoring

of deployment status of

packages to workstations


Xperience™ Deployment Services


Xperience Edge Server (XES) Xperience Edge Server (XES)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

(XCA)

(XFC)

Xperience Client Agent (XCA)

Xperience Framework Client (XFC)

WAN

Branch A

Branch B

• Xperience™

Deployment Services

offload packages to

branch locations


Workstation Setup


Workstation Setup

• Framework Requirements

– .Net Version

• Framework Deployment

• User permissions to folders

• Anti-virus exclusions

• Communication to iSeries,

Xp Servers, CRL

• Xperience Client Agent

• Xperience Installations Requirementsidentifies minimum resources required for Xperience workstations.

• Xperience Installation Guide using either the Automated Xperience Initializer or “ClickOnce”.

• XperienceClientAgentUserGuide will assist you in deployment of Xperience across your entire organization. The Xperience Client Agent (XCA) is an optional Windows service that can pre-deploy packages.

https://forclients.jackhenry.com/products-and-services/Core-Solution/SilverLake-System/Documents/XperienceInstallationRequirements_101317.pdf#search=Xperience%20Installation%20Requirements

https://forclients.jackhenry.com/products-and-services/Core-Solution/XperienceFramework/Lists/Documentation/XperienceFrameworkInstallationGuide_2017.3_102417.pdf

https://forclients.jackhenry.com/products-and-services/Core-Solution/XperienceFramework/Lists/Documentation/XperienceClientAgentUserGuide_2017.3_102417.pdf


Xperience Framework Client Requirements

• Version of .Net on the

client is very important

• For Client Portal

– Requirements Documents

– Installation Guides

– Self-Assessment


How can the Xperience Framework be Deployed?

• Click Once

– Browser link that will download the Framework Initializer to the user workstation and install locally

– Browser must be launched as Administrator

• Group Policy or Command Line

– The Framework Initializer can be deployed with a set of command line options to automate installation

• Additional information on FCP

https://forclients.jackhenry.com/products-and-services/Core-Solution/XperienceFramework/Lists/Documentation/XperienceFrameworkInstallationGuide_2017.4_031418.pdf


Xperience File Structure• Xperience installation folder is controlled in the

Xperience Management Module (XMM)

• The default is to – C:\program files(x86)\JHA\Xperience

• A separate file structure is created for each instance of Xperience that a user accesses

– The example to the left shows the workstation has 3 instances

– Each instance can contain a separate set of products and versions

– Allows for connection to other environments and parallel testing

• Common Logs are available at this level

• Primary contains the downloaded packages

• Working contains the packages in use

• The user running Xperience must have full control access rights to the Xperience install folder


Additional Permissions

• User running Xperience needs at least modify rights to the following folders:– %SystemDrive%\JHA

– %ProgramFiles%\JHA (or %ProgramFiles(x86)%\JHA)

– %ProgramData%\JHA

– %windir%\Temp

– %temp%– %ProgramData%

– %ProgramData%\Jack Henry & Associates, Inc

– C:\programdata\microsoft\crypto for Windows 10 machines

• Permissions– XP Install folder (already mentioned)

– Merge Document folders (network location, defined by FI)

– JAX\device.txt location (network location, defined by JAX/FI)


Anti-Virus Exclusions

• It is recommended to exclude the following folders from the Anti-Virus scans on the workstations:– %SystemDrive%\JHA


– %ProgramData%\JHA

– %ProgramFiles%\jXchangeMC – If running the JMC on the workstation

• Also exclude Xperience.exe from all scans on the workstations

• On the jXchange servers exclude the following folders:– %systemDrive%\JX

– %ProgramFiles%\JX (or %ProgramFiles (x86)%\JX


– %ProgramFiles%\jXchangeMC – This is the folder for the JMC


Core Xp Client

Integration Farm

iSeries Integration Providersex: Synergy

Communication The Xperience client needs to be able to communicate to the:

1. Xperience Server farm– (Port 443)

2. Core Server – iSeries (Ports 44 + Bank#

and 47 + Bank#)

– Core Director (Port 443)

3. Certificate Authority (Optional)

• Verifies against the active Certificate Revocation List (CRL)

• If communication is closed to external sites, set the Xperience environment to Closed in the XMM

1

2

Core

Microsoft,

Symantec,

…3


Xperience Client Agent (XCA)

• The Xperience Client Agent (XCA) is a separate installation from the Xperience Framework

• The XCA runs as a system service in the background even when the user is not logged into the workstation

• The XCA is responsible for the following:– Pre-deployment of Xperience packages when Xperience is closed

– Registration and monitoring of Xperience Hyperlinks jhaXp• Some products can send emails with a hyperlink to a particular page in Xperience

• XCA creates the registry entry and monitors for that Uniform Resource Identifier (URI)

– Registration of Xperience WebBrowser compatibility• By default Microsoft sets the browser compatibility level at IE 7

• The XCA installer sets the compatibility level to the max installed on the workstation

– XCA Tray Monitor provides user updates on XCA processing and notifications


User Setup


User Setup

• Active Directory Account– User needs to be a user on the same domain as Xperience

– Group policies should be applied for folder permissions and screen timeouts

• iSeries Profile (SL & 2020)– User should be defined with MENU or Global Security

– For Network Authentication, the user does not need to have a password

– Administrative users added to SLUIMEN or XPMENU

• EIM Association (SL & 2020)– Add user to EIM registry using IBM tool for In-House or SBUTILITY for Outlink

• IMS Claim– Add user Alias Claim to JXChange IMS (manual until R18)

• Device.txt (SL & 2020)– Add user/workstation to device.txt (Device Printer Table via JAX Admin)


iSeries Profile (SL & 2020)


Enterprise Identity Mapping (SL & 2020)

• EIM is an IBM solution, already present on the iSeries

• It leverages Kerberos, which is already present in Windows Active Directory

• The thought process is simple and practical…

Source RegistryWindows Active Directory

green1

Target RegistryIBM iSeries

bankergreen

EIM Identifier

Mr Green


IMS Claim (SL & 2020)

• Xperience Setup in Identity Management System (FCP)

• Identity Management System (IMS) is similar to EIM in that it associates the Windows Domain user to the AS400 user for authentication

• When institution is converted to EIM/SSO, the claims will need to be added manually until R18

https://forclients.jackhenry.com/products-and-services/Core-Solution/XperienceFramework/Lists/Documentation/CIF2020/XperienceSetupInIdentityManagementSystem_010418.pdf


Device.txt (SL & 2020)

• Leveraged by both JAX/Browser and Xperience to map individual Computers to specific iSeries Devices on the Power I

• Ensures that whenever the Browser Client or an Xperience tab is launched on a PC that the Session will always get the same iSeries Device(s)

• The proper method for managing the Device.txt file is to use the JAX Admin –Device Printer Table

• When you need an entry in the JAX Admin Device Printer Table– If you are an Outlink customer all workstations that will be accessing JHA Core Banking

software will need to have an entry

– If you have Teller stations and you are not on Xperience Teller, each Teller station will need an entry

– You are an InHouse customer and do not have your Power I set to use Virtual Devices

• When you do not need an entry in the JAX Admin Device Printer Table– You are an InHouse customer that has the Power I configured to use Virtual Devices

– Teller stations do not need an entry if you are currently on Xperience Teller


Troubleshooting


Troubleshooting

• Other Applications

• Landing Zone PC

• Common Errors

• Performance

• Support User


Other Applications

• Other applications

can have an impact

on Xperience

• Resources including

memory and CPU

can be used by

other programs

impacting Xperience

performance


High Level Troubleshooting

• Landing Zone– Used by support teams to replicate, research, and resolve issues without

tying up end user workstations

• Common Error Messages

Error Message Potential Solution/Research

“No institutions” Could be a locked ID, core bank access, etc

“Unable to connect. Verify EIM” User needs to be set up in EIM

“Communication fault occurred.. invalid device name” Ensure user/pc is in the device.txt file. This also applies to

XPE access

“Unable to save product manifest” or “cannot create file

structure”

User does not have sufficient access to the install folder


Performance

• Verify permissions and communications

• Check Task Manager and other running applications– Windows pages to disk when

memory is above 80%

• Limit # of records returned on searches (SL & 2020)

• Pre-load service dictionaries (SL & 2020)– Will impact launch times


Support User

Designation as Support User grants access to advanced system tools. These

tools provide your institution with additional options to troubleshoot, log errors, and

map your own screens.


Wrap-up


Coming Soon to the For Client Portal

This Photo by Unknown Author is

licensed under CC BY

• User Setup Guides

• Workstation Setup Guides

• Troubleshooting and Common Errors

http://ipkitten.blogspot.com/2013/10/monday-miscellany.html

https://creativecommons.org/licenses/by/2.0/


Potential Future Topics

• SilverLake & 20/20– Institution Maintenance

– System Maintenance

– User Maintenance

• Core Director– Xperience Architecture

• Personalization

Survey will be sent following presentation

This Photo by Unknown Author is licensed under CC

BY-NC-SA

http://www.eoi.es/blogs/mintecon/2015/04/28/feedback-liderazgo-efectivo/

https://creativecommons.org/licenses/by-nc-sa/3.0/


This Photo by Unknown Author is licensed under CC BY-SA

http://mmjgwrites.wordpress.com/

https://creativecommons.org/licenses/by-sa/3.0/

Date post:	26-Jan-2022
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times