ACS Administration Guide
ACS Administration Guide
Agenda ™
1
1/24/19
Deployment
Product Availability ™
2
1/24/19
Documentation ™
Deployment ™
3
1/24/19
Deployment ™
• Client Bundle
– Contains the Java executable Jar, properties file, platform specific start
executables and javascript start samples, product documentation, and licensing
notices
– All that is required to be deployed is the Java executable Jar
– The rest is optional
• No JRE distributed
– IBM i Access Client Solutions does not deploy a specific JRE
– Relies on a Java 8 or JRE to be accessible on the client OS
• When thinking about deployment, ask yourself where you want to put:
4
1/24/19
Deployment: Options ™
Deployment: Options ™
5
1/24/19
Deployment: Options ™
Deployment: Options ™
6
1/24/19
Deployment: Options ™
Deployment: Options ™
7
1/24/19
Deployment: Options ™
Deployment ™
8
1/24/19
Deployment ™
Deployment ™
9
1/24/19
Deployment/Install Scripts ™
Deployment/Install Scripts ™
• Provided install_acs script on Windows will copy the IBM i Access Client Solutions
deployment to C:\Users\<WindowsUser>\IBM\ClientSolutions
• Provided install_acs_*_allusers script will copy the IBM i Access Client Solutions
deployment to C:\Users\Public\IBM\ClientSolutions
• Deployment will ask the user which functions they want to use, if it should create
shortcuts on the Desktop for the Main User Interface and 5250 Session Manager. It
will also create file associations for the .hod, .bchx, .dttx & .dtfx if they haven’t already
been created
• The bitness of the of the install script should match the bitness of Java installed on the
workstation. It is recommended that bitness also match the client OS bitness
10
1/24/19
Deployment/Install Scripts ™
• Deployment Prompts
• IBM i Access Client Solutions v1r1m4 Update 3 (October 2015) provided an update to
these deployment scripts for Windows to allow an Administrator to control some of the
deployment behavior and how the client behaves for the user
• More Details
– https://www.ibm.com/developerworks/ibmi/library/i-ibmi-access-client-solutions-
customization-trs/
– http://www-01.ibm.com/support/docview.wss?uid=nas8N1020967
© 2018 IBM Corporation
11
1/24/19
12
1/24/19
13
1/24/19
• No => Copy the IBM i ACS deployment to the client workstation directory
appropriate for the install type, current user or all user
– To update the product, update the central location and re-run install script
• Yes => Run the product from the location the install script is being ran from
– May be a Network or Local location
– To update the product just update the deployment location via file copy
• Can also be used to copy the IBM i ACS Image to a chosen location on each
workstation and then run the install script from there
– File Associations and Desktop icons will point to this location
31
© 2018 IBM Corporation
14
1/24/19
Following this will be the same set of questions about what functions to allow
15
1/24/19
16
1/24/19
– An IBM i ACS deployment image that has been customized via /AdminConfig on
Windows can be used to deploy on Mac and Linux and the functions that are allowed
or not will be followed on those platforms as well
• Provided install_acs Javascript on Mac will copy the IBM i Access Client Solutions
deployment to the Mac OS Applications folder.
– IBM i ACS on Mac requires Java JDK
17
1/24/19
• Provided install_acs Javascript on Linux will copy the IBM i Access Client Solutions
deployment to the locations of
– /usr/share/applications/
– /opt/ibm/iAccessClientSolutions/
• The bitness of the of the install script should match the bitness of Java installed on the
workstation. It is recommended that bitness also match the client OS bitness.
18
1/24/19
https://www.ibm.com/developerworks/ibmi/library/i-ibmi-access-client-solutions-
customization-trs/index.html
Manual Settings
19
1/24/19
Limiting Function ™
• There are two approaches to limiting the functions that the user has
access to when running IBM i Access Client Solutions
Excluding Components ™
• What the IBM i ACS install_acs* scripts use to determine functions available to the user
• Deployed via AcsConfig.properties file next to or within acsbundle.jar
– Property must be set:
• com.ibm.iaccess.ExcludeComps
– Set this property to a comma-separated list of function keywords
20
1/24/19
Runtime Restrictions ™
Runtime Restrictions ™
• Can be set via the IBM i Access Client Solutions application when ran
with Administrator or Root level authority.
• Command Line option to restrict, unrestrict, list, export/import
21
1/24/19
acslaunch_win-32.exe /plugin=fileassoc
22
1/24/19
23
1/24/19
Application Administration
Application Administration ™
• Articles by Dawn May in her “i Can” Blog for IBM Systems Magazine
– Application Administration with Navigator for i
• http://www.ibmsystemsmag.com/Blogs/i-Can/February-2017/Application-Administration-with-Navigator-for-i/
24
1/24/19
Application Administration ™
Application Administration ™
25
1/24/19
Application Administration ™
Agenda ™
26
1/24/19
AcsConfig.properties ™
27
1/24/19
AcsBaseDirectory ™
28
1/24/19
Verifying Location ™
Network share
com.ibm.iaccess.AcsBaseDirectory=
com.ibm.iaccess.AcsBaseDirectory={PRODUCTDIR}/config_directory/{USER}
Thumb drive!
com.ibm.iaccess.AcsBaseDirectory={PRODUCTDIR}/config_directory
29
1/24/19
Export/Import ™
• IBM i Access Client Solutions has a mechanism for saving (exporting) and restoring
(importing) a user’s settings and preferences
• When a configuration is exported, all information is stored in an export file
• Stored data includes emulator session profiles
30
1/24/19
Export/Import ™
Auto Import ™
• So what is “autoimport”?
– Allows an export file to be automatically imported when the product starts up
– Useful for an administrator to automatically roll out settings
31
1/24/19
Auto Import ™
• com.ibm.iaccess.autoimport
– Can contain special config keywords
• com.ibm.iaccess.autoimport.version
– Typically set to a numeric value
– Dictates whether the file (specified by com.ibm.iaccess.autoimport) is imported. The
import happens if this value differs from the last file imported via the “autoimport”
feature.
– A value of ‘*’ can be used for the version and the import will be performed on every
launch. Could lead to consistently slower launch times.
Questions
32
1/24/19
Backup Information
Migration
33
1/24/19
Migration ™
• IBM i Access Client Solutions provide several tools to assist with migrating from the
IBM i Access for Windows client environment to IBM i Access Client Solutions
– Data Transfer
• Saved Data Transfer migration
– System Connections
5250 Migration ™
34
1/24/19
5250 Migration ™
5250 Migration ™
35
1/24/19
5250 Migration ™
5250 Migration ™
• Create File Association for IBM i Access for Windows saved .ws or .bch file to be opened
with IBM i Access Client Solutions
36
1/24/19
5250 Migration ™
• Create File Association for IBM i Access for Windows saved .ws or .bch file to be opened with IBM i Access Client
Solutions
• Can be set during IBM i ACS deployment script on Windows
37
1/24/19
• Migrates saved .dtt and .dtf files to IBM i Access Client Solutions .dttx and .dtfx files
38
1/24/19
• Results of Migration
– Green check indicates success
– Red x indicates failure and there are more details
• IBM i Access Client Solutions Copy Connections can be used to move System
Configurations
39
1/24/19
40
1/24/19
Create
Edit
41
1/24/19
42
1/24/19
• Create a connection for "common2.idevcloud.com that uses Windows logon and ssl
• Edit a connection for "common2.idevcloud.com that uses Windows logon and ssl
(the key here is /r)
43
1/24/19
Create/Edit
• IBM i Access Client Solutions Copy Connections can be used to move System Configurations
44
1/24/19
• ACS has "Use shared credentials." This maps to the "Use Windows user name and
password" option in Windows
Edit
45
1/24/19
1. cwbcossl.exe utility
2. Use IBM i ACS Base Package
46
1/24/19
• cwbcossl utility
47
1/24/19
Default password:
ca400
© 2018 IBM Corporation
48
1/24/19
49
1/24/19
50
1/24/19
4) "Tools->Key Management"
51
1/24/19
Default password:
ca400
© 2018 IBM Corporation
52
1/24/19
– IBM i Access for Windows Incoming Remote Command service was such a REXEC
daemon
– Windows Server OS also provided an REXEC daemon
– REXEC spec has significant issues, key being that it does not provide for SSL
communications so credentials and command are passed in clear text
– Microsoft last provided their REXEC daemon in the
Windows Server 2003 SDK, and documents that it is deprecated and not
guaranteed to work in newer Windows OS environments
– IBM does not include it’s Incoming Remote Command with
IBM i Access Client Solutions Windows Application Package
© 2018 IBM Corporation
53
1/24/19
• IBM i Access For Windows r7.1 is still supported on Windows Server 2012 R2 and
Windows 8.1 and earlier Windows OS versions
• Install and use the Microsoft Windows Server 2003 SDK provided REXEC daemon
Connection Configuration
54
1/24/19
System Configurations ™
• Use the System Configurations panel to store connection information on the IBM i
Systems that will be used
System Configurations ™
55
1/24/19
System Configurations ™
56
1/24/19
Performance
• IP Address Lookup Frequency
• Never – Specify IP Address
• IP Address
• Use the IP Address vs the System
name
57
1/24/19
Console Configuration
Console ™
58
1/24/19
5250 Console ™
• Service Functions
– Providing options for service
commands instead of providing
the up and down arrows and enter
• Supported with
LAN and HMC console types
59
1/24/19
• Advanced
– Optional configuration
pointing to specific System
and Partition
60
1/24/19
61
1/24/19
Questions
https://facebook.com/IBMPowerSystems
https://twitter.com/IBMPowerSystems
https://www.linkedin.com/company/ibm-power-systems
http://www.youtube.com/c/ibmpowersystems
https://www.ibm.com/blogs/systems/topics/servers/power-
systems/
© 2018 IBM Corporation
62
1/24/19
More to Follow: ™
128
© 2018 IBM Corporation
63