Cit thin client

This is a followup to Counting K2 Client Licenses for Thin Clients, which covered the issues an Administrator must consider before deploying the K2 client (KeyAccess) to Thin Client Servers. This document covers how the client is actually installed, and what happens after. It assumes a simple three-server farm but applies to a thin client enviroment of any size or type. We’ll also assume that new computer records are created using the default ID settings – thin client sessions will be identified using the initiating client computer’s name.Deploying KeyAccess is simple: the administrator chooses a time when the thin client servers can be rebooted and runs the K2 Windows client Installer (k2client.exe) on each server in turn. After supplying the DNS name of the KeyServer host to the installer and taking all defaults, each server is rebooted so that KeyAccess is running as a service on all three Thin Client Servers.Whenever a user on a remote device initiates a thin client session, KeyAccess on the Thin Client server inserts itself into the session created on that Server. This is true both when the session is just displaying a ‘published’ app as well as when a full thin client desktop is displayed on the remote device.When KeyAccess passes the session information to KeyServer it includes the IP and MAC addresses of the thin client server where the KeyAccess process is actually running. More importantly, however, the computer name of the remote device initiating the session is reported up to the KeyServer – a “thin client computer” record is created using this device name. Which Server is hosting the session is irrelevant. Usage of any controlled or logged program is properly linked to the initiating device. This ensures accurate licensing and useful reporting.One final note: even if the KeyServer is configured to audit all new computers, when a record is created for a Thin Client session, auditing is not performed since it would be uninteresting to re-audit the thin client server host every time a distinct device connects to a thin client server and generates a new record in KeyServer’s computer table.

Last updatedtruefalsefalseroot_actualdeletetimeActual Delete TimedateWhen will this CI be deletedtruefalsetrueroot_actualdeletionperiodActual Deletion Periodinteger40What is the period after the CI will be deletedtruefalsefalseroot_candidatefordeletetimeCandidate For Deletion TimedateWhen will this CI be warned about deletingtruefalsetrueroot_classCI Typestring[100]Class name of the CItruefalsetrueroot_containerContainerstring[32]Container CI of this CItruefalsefalseroot_deletioncandidateperiodDeletion Candidate Periodinteger20What is the period after the CI will be candidate for deletetruefalsefalseroot_enableageingEnable AgingbooleanfalseIs aging enabledtruefalsefalseroot_iconpropertiesstring[100]truefalsetrueroot_iscandidatefordeletionIs Candidate For DeletionbooleanfalseIs candidate for deletiontruefalsefalseroot_lastaccesstimeLast Access TimedateWhen was this CI last accessedtruefalsefalseroot_systemSystemstring[2]truefalsetrueAdapters providing CIs of type IBM MQ ChannelAdapter NameDescriptionAdapter TypeWebsphere MQ Topology by shellDiscover Websphere MQ topology by using SSH, TELNET, NTCMD or UDADiscoveryAdapters providing CIs of type ConfigurationItemAdapter NameDescriptionAdapter TypeImport from CSV Imports data from a CSV file into CMDB using mapping of the CSV file columns to CIT attributes. Mapping is defined by the following parameters: ciType: to define the CIT name which you want to create, mappingString: to define the mapping of the CIT attributes to the CSV file columns. Mapping file is used for more complex mapping definitions. Mapping file name is specified by 'mappingFile' parameter.IntegrationImport from DB Imports data from an external database into CMDB using mapping of table columns to CIT attributes. Mapping is defined by the following parameters: ciType: to define the CIT name which you want to create, mappingString: to define the mapping of the CIT attributes to the table columns Mapping file is used for more complex mapping definitions. Mapping file name is specified by 'mappingFile' parameter. A SQL 'select' query is generated automatically and selects all columns in specified table, which defined by parameter: tableName In advanced cases you can specify custom SQL query.IntegrationImport from properties file Imports data from a Properties file into CMDB, using mapping of the CSV file columns to CIT attributes This mapping is usually defined by the setting adapter parameters: ciType: to define the CIT name which you want to create, mappingString: to define the mapping of the Properties attributes to the CSV file columns In cases you need more complex mapping abilities, such as conversion of the strings contained in Properties file to the appropriate type of CMDB object's attribute, you should use the mapping XML configuration file specified by the mappingFile parameter. IntegrationSCCM Installed Software IntegrationThis adapter queries the records from SCCM database and recognizes it as install software by UD SAIIntegrationImport from Excel WorkbookImports data from Excel Workbooks. Parses through multiple worksheet XLS files. Uses 'CIImports.xls' (default) file to import data.IntegrationAdapters providing CIs of type

Advantage Realia WorkbenchCOBOL-ITData General ICOBOLFujitsu COBOL (All Windows versions)Fujitsu .NET COBOLIBM Visual Age COBOLmbp Visual COBOLMicro Focus COBOL (All Windows versions)Micro Focus Object COBOLMicro Focus NetExpress (All versions)Liant RM COBOL (All Windows versions)Note: FormPrint can also be used in a UNIX, Linux or VMS server environment and print to remote Windows PC’s across a TCP/IP network when you incorporate Flexus’ Thin Client product. Because your COBOL would reside on the UNIX, Linux or VMS server, this means FormPrint also support UNIX, Linux and VMS servers as well, when used in conjunction with Thin Client.No Requirement to Re-write Code if You Switch Environments in the FutureCOBOL FormPrint is 100% Windows version independent. If you use Thin Client with FormPrint, you can still use the same form definitions and source code with a new server operating system. The COBOL programmer uses the same COBOL source code and COBOL FormPrint form definitions regardless of which operating system is used. This allows the COBOL programmer to support more operating systems with only one set of forms and one set of COBOL source code. Ask your COBOL Tools vendor if they support the entire list of operating systems which are supported by COBOL FormPrint.Operating Systems SupportedWindows 95, 98, ME, 2000, NT, XP, Windows 7 and Windows 8 (32 bit Windows; 32 bit COBOL compiler required)Windows 7 and Windows 8 (64 bit Windows; 64 bit COBOL compiler required)Intel based UNIX and Linux (Thin Client server license required)Proprietary UNIX (AIX, HP-UX, DG-UX, Digital UNIX, etc.) (Thin Client server license required)VAX/VMS and Open VMS (VAX COBOL or Acucobol required) (Thin Client server license required)IBM Mainframe OS/390 UNIX System Services (Thin Client server license required)IBM Mainframe Linux (Thin Client server license required)As mentioned earlier, you can even run your COBOL program on a UNIX or Linux based platform and print your documents and forms on remote Microsoft Windows PC’s with our Thin Client product. Please see the Thin Client product information for more details.Switch Between Windows and UNIX and Maintain One Set of Source Code with Thin ClientCOBOL FormPrint supports the Windows Print Manager, but can actually be used in conjunction with UNIX or Linux. The Flexus Thin Client allows the COBOL program to be run on a UNIX or Linux server environment and print forms using remote Windows PCs across a TCP/IP network.The COBOL programmer uses the same COBOL source code and COBOL FormPrint form definitions regardless of