Transcript COMMANDbatch Security and Administration PC Requirements

COMMANDbatch Security
and Administration
Mark Sinclair
[email protected]
205-879-3282 ext. 2122
Customer Training and Technology Conference
Session Objective
• This session is designed for those who manage and
administer your COMMANDbatch system. The session
will focus on user security, back-up utilities, software
reinstallation, and the software upgrade process.
COMMANDbatch Security and Administration
COMMANDbatch Users
• Access to your data should be restricted to protect the
plant configuration and limit access to sensitive
information
• COMMANDbatch Users should not be confused with
Windows Users.
• To add new users you must login to COMMANDbatch
using the ‘sa’ user.
• COMMANDbatch has a highly configurable security
setup
– Forms can be fully or partially locked out
– Components (Fields) on the Forms can also be hidden or
locked out
COMMANDbatch Security and Administration
COMMANDbatch Users
• Users form is used to add
or modify existing users.
• Super User will have
access to all forms except
for Soft Manual Station.
• Non-Super User will require
Form Authorizations to be
configured
• Group Authorizations can
be assigned to users
COMMANDbatch Security and Administration
User Password
• A Password is initially required for any new users
• The user can use the ‘User Information’ form to change
their password
COMMANDbatch Security and Administration
User Forms Editing Permission
• The Editing Permissions is used to restrict the user from
making changes to the form design
• Experienced Windows users can be configured for
Basic to allow them to change grid column widths and
position, change Form Size/Splitter position, and Field
Labels and positions.
• Most Users should be set to None so they can’t
accidently modify a form design
COMMANDbatch Security and Administration
User Plant Context Form
• The Change Plant form is used on Multi-Plant
configurations
• This will allow the user to switch control from one
plant to another.
– This configuration requires each plant to be within the
same site location
• This form is also used for language support
– The error messages will display in the selected language
COMMANDbatch Security and Administration
User Extensions – Rules Tab
• The Rules on the User Extensions
form allows restriction on the Batch
Setup for a Dispatched Ticket
• Viewing Prices can be restricted on
the Batch Setup and Orders forms
COMMANDbatch Security and Administration
User Extensions – Batching Tab
• The Batching Tab allows users to
change the behavior of
COMMANDbatch while batching
• Default Sequence should ONLY be
used on a Remote Batch user
• Load Status will determine when the
Ticket will move from the Current
View to the History View on Batch
Setup
• Batch Setup Sort Type will determine
the sorting order of the Tickets on
Batch Setup
COMMANDbatch Security and Administration
User Extensions – Colors Tab
• The Order colors allows the user to
customize the colors for the different
Order Statuses
• The Low Inventory color is the only
color setting under the Ticket that
currently functions
• The Alert Sounds allow for a sound
file to be played for these events
– LowInventoryAlert.wav
– NotificationAlert.wav
– NotificationLoadAlert.wav
–
WINXP:C:\Program Files\COMMANDbatch\Custom\Scripts
–
WIN7:C:\ProgramData\CAI\COMMANDbatch\Custom\Scripts
COMMANDbatch Security and Administration
Users - Authorizations
• The Object Authorizations for User form is used to
select which forms this User has access to and what
privileges he/she has on that particular form
COMMANDbatch Security and Administration
Users – Form Privileges
• You have 7 privilege levels you can control for
each form you allow access to.
–
–
–
–
–
–
–
Delete
Edit (Modify)
Execute (Open)
Insert (Add New)
Read (Show/Hide)
Update (Read Only)
Bulk Update (Change multiple records at one time)
COMMANDbatch Security and Administration
Users – Component Privileges
• The Component Privileges allows you to control
access to individual fields (components) within the
form
COMMANDbatch Security and Administration
Users – Component Privileges
• The Component Authorization for User form will
allow you to select fields (components) from a
particular form and control the Read (Show/hide)
and Update (Read Only) privileges.
COMMANDbatch Security and Administration
Users – Group Authorizations
• User Groups can be configured to make it easier to
assign to existing or new users without having to
configure individual user authorizations.
COMMANDbatch Security and Administration
Users – Group Authorizations
• The Object Authorization for Groups is the same as
the Object Authorizations for Individuals.
– NOTE: A zero will have to be entered to revoke the
privileges in this form.
COMMANDbatch Security and Administration
Users – Group Component Privileges
• The Component Authorization for Groups is the same as
the Component Authorizations for Individuals.
– NOTE: A one will have to be entered to grant the privileges in
this form.
COMMANDbatch Security and Administration
Exporting and Importing Users
• Users and User Groups can be exported out of
COMMANDbatch and imported into another
COMMANDbatch system
COMMANDbatch Security and Administration
Windows Users
• CAI configures two default users in Windows
– COMMAND BATCH
– USER
• The COMMAND BATCH is the normal user with no
password
• The USER is used for remote access, since windows
requires a user with a password for remote access
COMMANDbatch Security and Administration
Setting up Restricted Windows Users
• COMMANDbatch requires a user with
administrative privileges to the local machine to
perform installations or patches
• General operation will work with no additional
modifications for Admin or Power Users
• Restricted users will require some modifications to
Windows Registry keys and file folder security
settings to allow general operation
– Note: See the Install.pdf file located on your CMDbatch
system’s Documentation folder for details.
COMMANDbatch Security and Administration
Microsoft SQL Server 2008 R2TM
COMMANDbatch stores…
• All user entered information in a database file
called ‘ebatch’ (typically contains up to 90 days of
ticket information)
• Ticket info > 90 days in the ‘ebatch_archive’
database file
– (Inventory transactions, such as, Auto and Manual Usages,
Inventory Receipts, and Inventory Adjustments are not
archived by default)
• Forms information in the ‘ebatch_forms’ database
file
– Forms data consist of field labels and positions.
– Form sizes and grid settings
COMMANDbatch Security and Administration
Database Utility
• DBUtility program is a tool
used to perform database
backup and recovery
operations.
• The typical user would not
need access to this program.
COMMANDbatch Security and Administration
DBUtility – Database Actions
• Under the Settings section you can select one of the
following Database Actions in the drop-down menu:
•
•
•
•
•
•
•
•
Install New Database
Upgrade Database(s)
Restore Database(s)*
Apply Database Patches
Archive Database
Maintenance
Repair Database
Backup Database(s)*
Archive Database
COMMANDbatch Security and Administration
•
•
•
•
•
•
•
•
Purge Database
End of Year Maintenance
Repair User
Verify Database(s)
Integrity
Reset CPM Sync Values
Database Maintenance
Precision Water System
Maintenance
Start/Stop Services
DBUtility - Backup
• DBUtility can be used to manually or automatically backup
the Database files
• The backup, archive, and purge process is normally ran
through the “End of” Day process
• Backing up the databases using DBUtility will not copy the
backup files to an external drive automatically, i.e. CD,
Network Share, or USB Flash drive.
– The default local drive backups are stored on the
• WINXP: C:\Program Files\COMMANDbatch\Custom\DBBackup
• WIN7: C:\ProgramData\CAI\COMMANDbatch\Custom\DBBackup
COMMANDbatch Security and Administration
Database Backup - External Drive
• The “End of” process can be configured to Write
the Database backup files to a CD or USB Flash drive
– This process uses the ‘ebcdburn.exe’ program to compress the
latest database files and any files under the following folder:
• WINXP: C:\Program Files\COMMANDbatch\Custom
• WIN7: C\ProgramData\CAI\COMMANDbatch\Custom
– and compresses them to a CBBackupFiles.zip that is written to
the external drive.
COMMANDbatch Security and Administration
Archive Control
• Archive Controls allows you to control what is
archived and how long to keep current data in the
‘ebatch’ database.
• Auto Archive/Purge and Backups can be enabled
COMMANDbatch Security and Administration
PC Requirements
1) XP Machines can use up to V1.8.11.6. Later versions
require Windows 7-10
2) Starting with V1.8.7.3, COMMANDbatch can run on
Windows 8.1 (64-Bit) Professional or Enterprise.
3) Customers who supply their own PC’s do not need to
install SQL and .NET because they are automatically
installed with COMMANDbatch.
4) For non-English systems, Windows 7 Enterprise or Ultimate,
or Windows 8.1 Professional or Enterprise is required. For
Windows 10, only the Professional version is required.
COMMANDbatch Security and Administration
PC Requirements
Main Batching PC (external RTC)
2.0 GHz CPU or greater, IBM compatible
8 GB RAM
DVD-RW Drive
240 GB Hard Drive
120 GB free disk space
VGA Card or Integrated Graphics Controller
100 MB Network Interface Card or Integrated Network Adapter
GigaLAN PCI Express Ethernet Card (Koutech PEN120)
-- OR -Standard PCI 10/100 Ethernet Card and (1) 10/100 Ethernet Switch
Parallel Port - Additional parallel ports may be required based on
configuration of printers.
Serial Port - Additional serial ports may be required based on
configuration of system.
Mouse with Keyboard (See Keyboard Protector)
19" External Color Monitor 1024 x 768 resolution or larger
Real Time Controller (RTC) for each COMMANDbatch plant
UPS, 450VA
Main Batching PC (vRTC)
– Please contact CAI Batch Service for hardware specifications
COMMANDbatch Security and Administration
Recommended PC Protection
• PC must be protected by an Anti-Virus and AntiMalware program which will need to be purchased
and maintained by your IT department.
• Uninterruptable Power Supply (UPS)
– Should be capable of supplying power to the PC and
monitor long enough for the operator to properly
shutdown the PC
– CAI can supply an APC 450VA (250Watt) UPS
• Dust Enclosure or perform routine cleaning of the
PC and Printer(s)
COMMANDbatch Security and Administration
Network Firewalls
• Network firewalls, hardware or software, are also
effective ways to protect the PC from unauthorized
access
• COMMANDbatch will require special
considerations when using firewalls
–
–
–
–
–
–
SQL Server Database requires port 1433/TCP
CBManager requires port 3000/TCP
Remote Clients and RTC requires port 1200/TCP
RTC Error logging requires port 1202/TCP
UltraVNC Remote Control Software requires port 5900/TCP
Load Event Status (Truck Signaling) Interface is typically
configured for port 2105/UDP
– Dispatch TCP/IP Link Interface is typically configured for
port 7000/TCP
COMMANDbatch Security and Administration
COMMANDbatch Software Installation
• When CAI supplies the PC you will receive…
– Dell Windows OS installation CDs
– Dell Device Driver CD
– vRTC Recovery CD/DVD/USB, if applicable
• CAI also provides all COMMANDbatch customers
with…
– COMMANDbatch Installation CD/DVD/USB
– COMMANDbatch Tools CD/DVD/USB
• It is very important that you store these
CDs/DVDs/USBs in a safe and accessible area for
future system recovery in an event of a PC failure
COMMANDbatch Security and Administration
COMMANDbatch Software Installation
• The COMMANDbatch Installation CD/DVD/USB will
allow you to reinstall COMMANDbatch and any of
it’s support applications
– If Autorun is enabled on the CD/DVD drive the
COMMANDbatch Install Menu will appear when inserted
into the CD drive
COMMANDbatch Security and Administration
COMMANDbatch Software Installation
• A full COMMANDbatch installation is required if
upgrading to a newer major version
– i.e. 1.7.x.x to 1.8.x.x
• An upgrade patch can only be performed for the
same major version
– i.e. 1.8.2.0 patch can be performed on any previous 1.8.x.x
versions
– 1.8.2.0 patch can NOT be performed on a 1.7.x.x version
COMMANDbatch Security and Administration
COMMANDbatch Versioning
• COMMANDbatch versioning has changed this
year.
• Where the CMDbatch version was a 1.7.*.*, 1.8.*.*
now the year of the release, then the version, then
the patch number:
– 2016. version number. patch number
• 2016.1.3 is the current GA release of CMDbatch
COMMANDbatch Software Licensing
• All COMMANDbatch systems with 1.06.x and higher
require a License file to be used to brand the
system.
– The License file will be your system’s S.O. (Sales Order)
number
– Once a system is branded with that license on the first CB
installation the license file is not required on future
reinstallations or upgrades (except for upgrades to 1.8)
• A system that was branded with the incorrect
license can be rebranded using rebranding files
supplied by a CAI’s Batch Support Specialist
COMMANDbatch Security and Administration
COMMANDbatch Software Licensing
• COMMANDbatch systems with 1.8.x.x and higher
will enforce license checking
– Additional Plant Controls will require the appropriate
license (Note: Do not add any additional controls until the
correct license is added or the system will not allow for
future production)
– Order Entry and Projects will require the appropriate
license
– 2nd Client/Remote Batch Clients will require the
appropriate license
COMMANDbatch Security and Administration
COMMANDbatch Installation Types
• Main Batching PC (active) which is the typical
installation for single PC setups
• Main Batching PC (inactive) which is used as a
remote client in a multi-plant configuration but can
be converted to a Main Batching PC in event the
Main Host Batching PC fails
• Remote PC which is for Remote Order Entry, Data
Entry, Supervisory or Remote Batching
COMMANDbatch Security and Administration
Automating CB Software Installation
• Install.ini file can be configured to automate the
installation of COMMANDbatch
• This file defines…
–
–
–
–
–
if the Installer’s Welcome screen is displayed
what drive COMMANDbatch is installed on
what install type to perform
whether COMMANDassist (ARA) is installed
whether CAI’s Annoucement Service is installed
COMMANDbatch Security and Administration
COMMANDbatch Software Update Center
• The Update Center allows you to download
upgrades and control which plant sites have
access to download and what version they can
download
https:/updatecenter.commandalkon.com/cb
COMMANDbatch Security and Administration
COMMANDbatch Software Update Center
• The Web Browser form inside COMMANDbatch or
Internet Explorer can be used to access this site
COMMANDbatch Security and Administration
COMMANDbatch Software Update Center
• COMMANDbatch Web Browser can be configured
to default to the Update Centers webpage
– An ActiveX Control will need to be downloaded the 1st
time so the Update Center can determine the S.O.# of the
PC
COMMANDbatch Security and Administration
COMMANDbatch Announcement Service
• The Announcement Service is installed by default
on new CB systems
• Internet access is needed for this to operate
• The following announcements can be displayed…
– Upgrades
– Critical
– Informative
COMMANDbatch Security and Administration
CB Central
• CB Central is a new
feature of CB 2016.1.*
• This tool centralizes all
system information
and provides one
click access to log
files.
• A scan is also
provided to identify
system issues such as
missing license files
COMMANDbatch Security and Administration
CB Central
• CB Central’s right-click
menu provides simple
and quick access to:
–
–
–
–
–
–
–
–
PC Name
IP Address
CB Version
License Info
Trace Viewer
Log Files
COMMANDbatch
Support
COMMANDbatch Security and Administration
Please Complete Your Evaluation
• Be sure to circle the session you are evaluating on
the back of your card
– Plant Automation (Track Name)
– BAT-009 (session code)
– CB System Securities and Administration (session title)
• All breakout session materials can be accessed at:
marketing.commandalkon.com/cc2016/update/index.htm
• Thank You!