sybase afaria 2006 wp (1)

Afaria Session Manager


5/17/05 2

TABLE OF CONTENTS

ABSTRACT................................................................................................................................3

INTRODUCTION ......................................................................................................................4

USAGE SCENARIO 1 – AUTOMATING DATA RETRIEVAL .........................................................5

USAGE SCENARIO 2 – AUTOMATING DATA DELIVERY ..........................................................8

USAGE SCENARIO 3 – PRE AND POST SOFTWARE DISTRIBUTION PROCESSES..................10

USAGE SCENARIO 4 – ENHANCING APPLICATION SELF-HEALING.....................................12

USAGE SCENARIO 5 – APPLYING BUSINESS LOGIC FOR SESSION CONTROL.....................14

TAKING ADVANTAGE OF AFARIA’S COMMUNICATION EFFICIENCIES.................................16

SUMMARY..............................................................................................................................17

APPENDIX A. – LIST OF SESSION MANAGER EVENTS .........................................................18

APPENDIX B. – LIST OF SESSION MANAGER PRE-DEFINED VARIABLES .............................20

ABOUT IANYWHERE ..............................................................................................................22


5/17/05 3

Abstract History has shown that the rapid proliferation of laptops caught some companies by surprise. Now handheld devices have invaded the enterprise. Information technology (IT) managers are looking for tools they can use today for controlling and maintaining their mobile computing assets. Companies are now in the process of acquiring and deploying frontline devices, such as Windows laptops, Palm handhelds, WinCE and Pocket PC devices, Windows Mobile-based Smartphones and Symbian smart phones. Meeting the need to manage these devices, their applications and the data that moves through them is critical to the success of the enterprise. IT managers must deal with rapidly expanding issues such as how they will:

• Retrieve business data from their mobile devices • Deliver content to their mobile devices • Define, efficiently automate, and execute the business processes - the flow of business data to and from

their devices • Upgrade and maintain the applications installed on their mobile devices once the devices have left the

building and are in use in the field • Proactively manage applications on their mobile devices • Optimize the connections for the communications environment

Afaria is frontline management software that allows companies to solve these challenges. With Afaria, companies can centrally manage and secure devices used by workers at the front lines of business, such as sales people and service technicians. Afaria goes beyond traditional systems management to help companies secure devices, automate processes and manage software, content and data whenever workers have a connection. With Afaria information is secure, IT is in control, and workers have the data, content and applications they need, regardless of the available bandwidth. This document is designed to assist IT managers, systems administrators, system engineers and others interested in frontline management solutions. It describes, via detailed usage scenarios, how Afaria’s Session Manager provides solutions to the challenges associated with managing devices at the front lines of business. .


5/17/05 4

Introduction Business has moved outside the walls of the enterprise. Every department of an organization includes potential mobile workers – sales and service personnel, remote branch office workers, telecommuting employees, traveling executives, field engineers, and other road warriors. Every organization requires a well-defined flow of information within their mobile enterprise, because the “line-of-business” processes involved represent the very basis for that organization’s economic well-being. Successful automation of these business processes can yield many benefits including cost savings, improved productivity, better decision-making, and access to information that can be converted into strategic advantage. The push toward mobile computing necessitates a session-oriented mobile device management approach that queues management tasks for intermittently connected clients. Session Manager, a key component of Afaria provides this type of approach. It is an easy-to-use, graphical user interface based, scripting tool that allows you to automate business processes and increase communication efficiency, without having to learn a programming language. The purpose of this document is to provide examples of how Session Manager can enable and extend these business processes to disconnected mobile devices. Afaria is a client/server software solution, organized and described by a transmitter/channel paradigm. Mobile clients such as laptops, handheld devices, interactive pagers, and smart phones with Afaria client software subscribe to channels or groups of channels defined on the transmitter (server). There are several types of channels that can be defined within Afaria, including Software Manager channels, Inventory Manager channels, Document Manager channels, Configuration Manager channels, Backup Manager channels and Session Manager channels. Session Manager channels are comprised of worklists and sendlists – organized, reusable groups of events, corresponding to specific tasks that can be scripted to occur when the Afaria client connects to the transmitter. The range of possible tasks that can be achieved with these events is broad in scope. The complete list of worklist events can be found in Appendix A. Session Manager can be used to automate processes in a variety of business scenarios. These scenarios include business tasks such as:

• Automating Data Retrieval from Mobile Devices • Automating Data Delivery to Mobile Devices • Automating Pre and Post Software Distribution Processes • Enhancing Application Self-Healing • Applying Business Logic to Automated Processes

For more information on how to use the product, refer to the Getting to Know Afaria Guide and the Afaria product documentation.


5/17/05 5

Usage Scenario 1 – Automating Data Retrieval An insurance company has 400 sales representatives in the field equipped with laptop computers. The sales representatives use a Windows based order entry application for recording their sales orders. Throughout the day, they enter order information into the application and connect through an ISP to the corporate HQ to transmit the orders. At the corporate HQ, the files created by the order application are queued for processing and held in directories associated with each sales representatives. In order to track the handling of the data, these files are stamped with the date and time the file transfer occurs. Once the data is received, a processing service is notified to begin processing of the order data. The definition of a business process – the flow of data – needs to be accurate, complete, reliable and rapid. Session Manager facilitates the automation of well-defined business processes such as data retrieval that define where data is located, and how it is to be transported. A high level view of the data retrieval business process described in this scenario looks like this: The need to move data between the mobile devices in the field and the corporate enterprise is mandatory. Session Manager provides the ability to create file transfer worklist events to accomplish this. An Afaria file transfer event is used to describe the direction in which the data moves. The ‘Get File From Client’ event is a ‘pull’ of data from the client device to the server, such as in a polling or data retrieval scenario. To accomplish this common business task, the Afaria client initiates an IP based connection to the Afaria transmitter at the corporate HQ. Once this connection is established and optionally authenticated, a predefined ‘channel’ containing worklists is executed, conducting the work necessary to move the order data from the mobile device to the corporate database for processing. After the data has been successfully retrieved, a notification is sent to a data processing program to act on the received data.

Output files are moved to the corporate HQ and queued for processing

Data processing program is notified and order files are processed

An Order Data Output File is created

End

Reps Enter Order Data on Mobile Clients


5/17/05 6

The administrator has built this ‘Get’ file transfer event by providing the information shown in this Session Manager screen shot below. On the right is the complete list of events available:

Note the information the administrator provided in this example. As the file Source and Target paths indicate, the *.fil data file is moved from the C:\program files\salesapp\data folder on the mobile device to the corporate server, \\AlphaOne by Afaria and deposited into the directory created with Afaria’s predefined <ClientMachineName> variable. This example also introduces the use of variable data in Afaria’s Session Manager. In addition to using a pre-defined variable to rename a directory, the data file is renamed in the transfer process using the predefined <date> and <time> variables. This facilitates easier tracking by placing a date/time stamp on the file received for processing.


5/17/05 7

Note that there are many options available for customizing Afaria worklist events. In this example, the administrator has enabled the following event options:

• Safe Transfer - Prevents the creating of a destination file until the file has been successfully transferred. This option instructs the Server to use a hidden temporary file until the file transfer completes. Once complete, the Server renames the temporary file to the destination filename.

• Delete After (-) – Deletes the file from target file(s) from the source directory after a

successful file transfer has been verified. • Make Target Path – Creates the specified target file path if it doesn’t already exist. • File Differencing – With this option enabled, Afaria compares the version of the file at the

Client with the version at the Server and sends only the byte-level differences. When this option is not selected, Afaria transfers the entire file. The option reduces connection time when transferring updated versions of existing files.

Session Manager’s file transfer capability is easy to deploy and manage and is a typical use of this component of Afaria. The use of variables for construction of directory and file names illustrates the broad power and flexibility of this scripting tool.


5/17/05 8

Usage Scenario 2 – Automating Data Delivery A manufacturing firm has 2,000 sales representatives in the field equipped with Kyocera Smart Phones running the Palm OS. They rely on current pricing and inventory data that is updated frequently. Throughout the day, sales representatives input orders and connect to the Afaria transmitter at the corporate HQ to transmit their data. During this connection the version of the product price database residing on the client device is checked and if necessary, an updated price database is delivered to the Palm OS device. A high level view of the data delivery business process described in this scenario looks like this: No Yes As in the previous example, the need to move data between the corporate enterprise and mobile devices in the field is mandatory. Afaria’s Session Manager provides a solution to this challenge. In this scenario, the Afaria worklist event, ‘Send File to Client’ event is used. This event provides a ‘push’ of data from the corporate enterprise to the mobile client devices in the field, such as in a content delivery scenario. Within the Afaria communication session, the worklist containing this ‘Send’ event is executed. The event compares the version of the database file on the client device with the source file on the corporate server, updating the client version only when necessary.

Updated price database is sent to mobile client End

Reps connect and transmit order data

Data output files are moved to the corporate HQ and queued for processing

Price db current?

End


5/17/05 9

The administrator has built this ‘Send’ file transfer event by providing the information shown in this Session Manager screen shot:

In this example, the administrator has defined the pricelist.pdb located in the pub folder of the \\AlphaOne server on the corporate LAN as the source and root of the client device (Palm OS has no file structure) as the target. Note that there are many options available for customizing Afaria worklist events. In this example, in addition to enabling the ‘Safe Transfer’ the administrator has enabled the ‘Check Updates Only’ option. This event option transfers a file only if the time, size, version, or date differs between the source and the target. This option can shorten the connection time by ensuring that a file transfer then only takes place when necessary. Whether ‘Getting’ files from or ‘Sending’ file to mobile clients, Session Manager offers the option of using specific communication optimizations such as Safe Transfer and Check Updates Only. The use of these optimizations reduce the amount of time necessary for the connection, reduces costs, and enhance the end user experience.


5/17/05 10

Usage Scenario 3 – Pre and Post Software Distribution Processes A national retail chain has 5,000 unattended workstations running Windows NT and 2000. The applications on these personal computers are upgraded typically four times a year. Because the applications are designed to run in an unattended environment, they are configured to run as services. To upgrade the application requires stopping the application service, performing the upgrade and often rebooting the PC. A high level view of the application update business process described in this scenario looks like this: Yes No To accomplish this, the administrator has used Session Manager to build worklists with the following events:

‘NET STOP’ event in ‘Stop Service’ worklist ‘Shutdown’ event in ‘Shutdown’ worklist The ‘Stop Service’ worklist contains an ‘Execute Program’ event that issues a NET STOP on the application, shutting down the application service. The ‘Shutdown’ worklist contains an ‘Execute Program’ event that calls a shutdown and restart utility. These worklists are then assigned to separate Session Manager channels named ‘Stop Service to Upgrade App’ and ‘Reboot After Upgrade’.

Channel executes NET STOP, stopping application service

Application is upgraded by Afaria Software Manager Channel

End

Afaria client on unattended pc connects to transmitter on a scheduled basis

Upgrade

app?

End

Channel executes rebooting PC and restarting application


5/17/05 11

In this example, Session Manager is used in conjunction with another Afaria component, Software Manager. Tying these channels together, within the Afaria Software Manager channel, the administrator has specified the following Session Manager channels to be executed before and after the Software Manager channel executes:

When this Software Manager Channel executes, it calls the ‘Stop Service’ Session Manager channel to stop the application service, delivers and installs the upgraded application, and then calls the ‘Reboot After Upgrade’ channel to reboot the unattended PC, completing the installation. This example illustrates the ease of use and the scope of power made available to the administrator by Afaria’s Session Manager.


5/17/05 12

Usage Scenario 4 – Enhancing Application Self-Healing A pharmaceutical company has deployed 8,000 Pocket PC devices with a mission critical application to its mobile sales force. In order to keep the application up and running, an application ‘health check’ is performed automatically with each connection to the Afaria transmitter. Any missing, modified, or damaged files are automatically replaced and critical registry keys are verified to ensure the application will perform as designed. A high level view of the application file comparison ‘health check’ business process described in this scenario looks like this: Yes Yes Yes No No No

End

Afaria client on Pocket PC device connects to transmitter

Exe size match?

Send correct version of application executable to client

Date / Time match?

Send correct version of application executable to client

Registry key corrrect?

Send correct registry key to client


5/17/05 13

In this scenario, the mission critical application deployed is comprised of a binary executable named orders.exe and single registry entry indicating the application version. When the Afaria client connects to the transmitter, the assigned channel executes and a worklist containing multiple events described in this Session Manager screenshot is executed:

The scripting required for this example is more complex than the previous scenario examples. There are 11 events in the ‘Check Order App’ worklist. It starts with a ‘Send’ event that checks the version of the executable on the client against a reference version of the same file on the server. If the executable size and time/date stamps of the file on the client and the reference file match, no action is taken; otherwise the correct version of the executable is delivered to the client. Next the worklist reads the registry value of the HKLM\Software\OrderApp\Version key. If there is no value for this key, the registry key is then created and the appropriate value is set. To end the worklist, ‘End If’ statements close out the logical branches. Note the events appearing in blue. These are session control events which utilize conditional logic with ‘Conditional False’, ‘If’, and ‘Else’ statements. These events are followed by an ‘End If’ statement that closes out the logical branches created when the worklist executes. The ability to leverage advanced programming techniques such as conditional logic branching is a unique strength of Afaria’s Session Manager - providing a level of control normally reserved for a programmer to the system administrator. Using variables such as <OrderAppVersion>, makes code reusable, enhancing its applicability and usefulness and therefore it’s value. Session Manager’s broad set of predefined variables and the ability to set variables from INI files, registry keys, and ASCII string and read variables further enhances its usefulness and value.


5/17/05 14

Usage Scenario 5 – Applying Business Logic for Session Control A professional services firm has deployed 12,000 Windows devices to its field service organization. Each service rep connects to the corporate Afaria transmitters several times a day to receive open work orders and transmit completed site visit reports. During the connection from the mobile device, the connection speed is determined and work is executed based on predefined business logic. A sample of the business process described in this scenario can be depicted like this: ‘Connection Speed Detection Decision Process’ Yes No Yes In this scenario, the work executed is dependant on the connection speed obtained during the connection. By leveraging a dynamic environmental condition such connection speed, this session manager channel is given intelligence to determine the work to be accomplished. When the Afaria client connects to the transmitter, the connection speed is recorded and categorized as a high, medium or slow speed connection. The appropriate worklist is then assigned and executed.

End

Run medium and high priority, medium process time worklists only

Run high priority, short process time worklists only

Slow speed connection determined

Run all defined worklists, regardless of process time required

Hi-speed connect?

Medium speed

connect?

Afaria client on Pocket PC device connects to transmitter


5/17/05 15

This Session Manager screenshot depicts the construction of the worklist:

The intelligence built into this process can be seen in the details, at the event level. The ‘Check Speed’ worklist performs several functions. The first event, ‘Check Speed’ notes the speed of the session connection. This information is written to the <ConnectionSpeed> variable. The value of this variable can be tested and specific actions taken. In this example the connection speed is categorized into one of three ranges, less than or equal to 33,600 kbps, between 14,000 and 33,600 kbps and less than 14,400 kbps. Each category is associated with a worklist containing high, medium or low priority work. This ensures that the work executed during the connection is appropriate to the connection speed obtained.


5/17/05 16

Taking Advantage of Afaria’s Communication Efficiencies As the corporate IT manager begins to plan for supporting mobile devices, he realizes that managing for the mobile environment is very different than managing for the LAN environment. Gone is the assumption of continuous high-speed LAN connection between client and server. It has been replaced with high latency, intermittent and often fragile landline and wireless connections, mandating the need for a mobile focused management strategy. One of Afaria’s strengths is its ability to keep a mobile user in touch and up-to-date with critical enterprise information without transferring an undue burden of responsibility. Companies don’t want to involve the mobile worker in the process of updating critical information, maintaining applications and tracking hardware and software assets. A more workable approach is to seamlessly update mobile devices on a session-by-session basis. Afaria is designed to monitor a user’s mobile ‘heartbeat’, and then perform necessary system and data management tasks whenever a mobile device connects to the network. Afaria incorporates a number of communication optimization features that can be enabled or disabled, based on the task(s) that are being performed. Just as with other Afaria channel types, Session Manager provides the following communication options:

• File differencing – which sends file updates based on byte level changes, updating those files that have been altered since the last update.

• Speed detection – checks the speed limitations of a connection before downloading large files

that could require extended connection times, and then determine the most intelligent use of a bandwidth window. As in Scenario #5, you can then use Session Manager’s conditional logic capabilities to assign management tasks based on the connection speed.

• Checkpoint restart –automatically picks up failed data transfers at the exact point of

interruption, rather than going back to the beginning, which would be a waste of time and effort when dealing with large files.

• Compression – reduces the size of large files therefore eliminating redundant computing

cycles on the server when the same file or files are sent to many users. These compressed files are also cached by Afaria to boost access speeds.

• Segmented file transfer – lets IT administrators send out large files or application software

updates in segments – almost like packet exchanges in communications. The chunks of data can then be organized to send the smallest or largest first, or even transferred at times when the network is less busy.

Afaria was built specifically to address the unique challenges of the mobile environment. Session Manager leverages Afaria’s optimizations for the mobile environment to deliver more efficient, faster, less error prone, and more cost effective communications with mobile devices. This results in decreased costs and increased uptime delivering higher productivity and an improved end user experience.


5/17/05 17

Summary The largest portion of the total cost of ownership of mobile devices is not the initial costs of the devices, but the costs associated with support, administration and operations. According to Giga Information Group, enterprises with mobile devices are faced with support cost 11/2 to 3 times higher than costs associated with tethered devices. Regardless of the connection method – dial-up RAS connections, wired Ethernet, Internet connections, radio or wireless LAN – these organizations need a management solution that considers the differences while working as a single solution. Afaria provides the unique session management capability required as a component of this solution. Through the examples provided, this paper emphasizes Afaria’s Session Manager capabilities, including:

• Rapid development – A powerful command set accessed through a point and click interface for rapid development of highly customized business solutions.

• Ease of use – A highly literate, non-compiled scripting language. • Powerful flexibility – Includes a comprehensive range of predefined events, a broad list of system

variables, the ability to define custom variables and the ability to use advanced programming structure. • Fault tolerance – Any defined business process can be mapped into an automated Afaria session.

Contingencies that could delay or prevent the flow of critical business data can be planned for and proactively dealt with.

• Efficient execution – Leverages Afaria’s highly optimized core communication protocols for clean, fast, reliable execution of automated business processes.


5/17/05 18

Appendix A. – List of Session Manager Events

Events Names Description File & Disk Operation Append File Combines one or more files Check Disk Retrieves storage characteristics of a disk. Check File Checks file time stamp and size. Check Volume Retrieves a value that represents the volume of disk space specified on

the client device. Copy File Duplicates files on the same computer. Delete File Removes files from the computer. Directory Listing Places a list of directories and files in a text file on the Server. File Status Determines if a file exists. Find File Sets a variable name to the full path for the specified file. Get File from Client Retrieves Client files and places them on the Server. Make Directory Creates a new directory. Remove Directory Deletes an empty directory. Rename File Changes a file’s name. Wait for File to Exist Pauses until the file appears, but continues if the time is exceeded. Set File Attribute Sets or clears the attributes for a single file specification, or for a

wildcard. Variable Events Create Registry Key Create a key in the registry. Delete Registry Key Delete a key in the registry. Delete Registry Value Delete a registry value. Delete Variable (INI) file

Delete a variable in a INI structured file.

Get Registry Value Get a registry key value. Increment Variable Changes a variable by a positive or negative amount. Read Variable (INI) File Reads INI files, INF files, or a file of variables. Search Registry Finds and places full registry key path into a variable. Set Registry Value Sets a value in the registry to a specified string. Set Variable Defines a variable for the selected object. Test Variable Compares variables to a known value. Update Variable (INI) File

Updates INI files, INF files, or a file of variables.

Session Control Comment Includes a non-executable remark. Disconnect Terminates the IP connection for the current session. Else Begins an alternate case of events. End If Ends an If block of events. End Repeat Ends a Repeat block of events. End Session Stops a session and ends communication. End Work Object Stops the current object and starts the next object. If Executes an event block based on a condition.


5/17/05 19

Quota Defines the beginning of the quota block and quota criteria, minutes and/or bytes.

End Quota Ends a Quota block of events. Repeat Repeats a set of events based on a condition.

Events Names Description Other Events Check Memory Retrieves a value that represents the memory of the client device. Check Speed Checks the speed of the session connection. Execute Program Execute an application. File Save Dialog Displays the Save Files dialog, which lets the Client user choose the

destination directory. Insert Channel Executes an existing Session Manager channel in an event file. Insert Worklist Executes an existing set of events in an event file. Message On the Server, places a message in the Messages or Sessions view in the

Log Viewer. At the Client, displays an informational message window. Notify Program Sends a command to an application. Raise Event Specifies that a particular event be visible in the Alerts Console. Notify Program Sends a command to an application.


5/17/05 20

Appendix B. – List of Session Manager Pre-defined Variables

Variable Names Description <!Drive<VarName>> Extracts file name from session variable or user variable. <!File<VarName>> Extracts file name from session variable or user variable. <!Path<VarName>> Extracts path from session variable or user variable. <%UserDefined> Extracts the value of the specified user-defined variable. <AuthenticatedUser> Indicates whether or not Authentication is turned on. <ChannelName> The channel’s name. <ChannelStatus> Indicates the completion status of the channel when if differs from

the session status. <ChannelViewer> Indicates whether the Channel Viewer Client initiated the session. <CheckDiskSize> The disk space available value set by the Check Disk event. <CheckMemorySize> Returns a value that represents the available amount of memory on

the handheld Client. <ClientChannelDir> The directory of the Client computer where channel files are

located. <ClientCommonFilesDir> The Windows Common Files directory on the Client computer. <ClientDeviceType> The machine name of the handheld device. <ClientDomainName> The name of the domain to which the user is logged on. If the user

isn’t logged on to a domain, this variable will contain the user’s machine name.

<ClientInstallDir> The name of the install directory on the Client. <ClientIPAddress> The client’s IP Address. <ClientMachineName> The machine name of the Clients computer. <ClientMemorySize> Returns a value that represents the total amount of memory on the

handheld Client <ClientOS> The operating system on the Client computer. <ClientOSVersion> The version of the operating system on the Client computer. <ClientProgramFilesDir> The Program Files directory on the Client computer. <ClientRASUserName> If the handheld Client connects to the transmitter via a modem,

returns the user’s User Name. <ClientSyncUserName> If a Palm user is synching the device with a Companion PC, returns

the user’s User Name. <ClientTempFilesDir> The Temporary Files directory on the Client computer. <ClientUserName> The Windows login name. <ClientVersion> The version of the Afaria system on the Client computer. <ClientWindowsDir> The Windows directory on the Client computer. <ClientWindowsSystemDir> The Windows system directory on the Client computer. <ConnectionId> The unique numeric ID for the connection.

Variable Names Description <ConnectionSpeed> Used with the Check Speed event, determines the speed of a session


5/17/05 21

connection in KPS <ConnectionType> Determines whether the session connection is via LAN or dial-up

(RAS). <d> Day of the month (01 to 31) <date> The numeric month, day, and year in the form specified by the

Server’s Windows Regional Settings Control Panel. <dw> Day of the week (1 to 7). <dy> Day of the year (001 to 365). <FileStatCount> Number of files as indicated by the File Status event. <FileStatSize> File size value set by File Status event. <FileStatVersion> The file version value determined by running the File Status event. <hh> Current 24-hour value on Server (00 to 23). <InteractiveUserName> The Windows logon name. <m> Numeric month (01 to 12). <mm> Current minutes value at Server (00 to 59). <ms> Milliseconds (000 to 999). Reset every second. <SendFilesAttempted> The number of files the Server attempts to send. Counters are set to

“0” at the beginning of each channel and never reset. <SendFilesFailed> The number of times the Server is unable to send a file. Counters

are set to “0” at the beginning of each channel and never reset. <SendFilesSuccessful> The number of times the Server is successful in sending a file.

Counters are set to “0” at the beginning of each channel and never reset.

<ServerChannelDir> The directory on the Server where channel files are located. <ServerCommonFilesDir> The Windows Common files directory on the Server computer. <ServerInstallDir> The name of the install directory on the Server computer. <ServerIPAddress> The Server’s IP address. <ServerMachineName> The machine name of the Server computer. <ServerOS> The Server’s operating system. <ServerOSVersion> The version of the Server’s operating system. <ServerProgramFilesDir> The Program Files directory on the Server computer. <ServerTempFilesDir> The Temporary Files directory on the Server computer. <ServerVersion> The Server’s CONNECT:Manage version. <ServerWindowsDir> The Windows directory on the Server computer. <ServerWindowsSystemDir> The Windows System directory on the Server computer. <SessionDuration> The number of minutes elapsed during this session. <SessionStartTime> The time (in hhmmss format) when this session started. <ss> Current seconds value at Server (00 to 59). Variable Names Description <time> Inserts the Server’s current 24-hour time in the form hhmmss. <TransmitterID> The unique identifier for the transmitter. <TransmitterName> The transmitter’s name as specified in Channel Administrator <y> Numeric year (00 – 99). <y1> Numeric one-digit year (0 to 9). <y4> Numeric four-digit year (0000 to 9999).


5/17/05 22

About iAnywhere iAnywhere enables success at the frontlines of business, and holds worldwide market leadership positions in mobile and embedded databases, mobile management and security, and mobile middleware. iAnywhere's unique "Always Available" computing model provides online and offline access to the information and applications users need, when and where they need it most. Millions of subscribers, 15,000 customers and 1,000 partners rely on the company's award-winning technologies, including SQL Anywhere®, Afaria®, and the AvantGo® mobile Internet service. iAnywhere is a subsidiary of Sybase, Inc. (NYSE: SY). Visit www.ianywhere.com for more information.

www.iAnywhere.com

North America T 1-800-801-2069 1-519-883-6898

Europe, Middle East, Africa

+44 1628 597 100

iAnywhere Solutions, Inc. Worldwide Headquarters

One Sybase Drive Dublin, CA 94568-7902

U.S.A. [email protected]

Asia Pacific

+852 2506 8700

Japan +81 3 5210 6380

Copyright © 2005 iAnywhere Solutions, Inc. All rights reserved. iAnywhere, SQL Anywhere Studio, AvantGo XcelleNet, Afaria, and RemoteWare are trademarks of Sybase, Inc. or its subsidiaries. All other trademarks are properties of their respective owners. ® indicates registration in the United States of America. IANY041305

sybase afaria 2006 wp (1)

Documents

mobile devices

frontline devices

companies secure devices

devices upgrade

handheld devices

usage scenario

pocket pc devices

afaria information