TOPICSBasic SAP Control Center Administration > 12% Describe the SAP Sybase Control Center (SCC) and perform basic administration tasks such as: Monitor Users and Licenses, review or Change Communication and DCN Ports, manage various Synchronization Settings, maintain and manage Cache Groups, review logs and manage option, configure Apple Push Notifications, configure BlackBerry Enterprise Server Communications, create, enable and remove Domains, manage EIS Connections.MBO Deployment and Backend Connectivity > 12% Describe MBO/LBO concepts - Attributes, Operations, Roles, Relationships; define general and SAP Connectivity: SOAP Web Services, RESTful Services, database and SAP BAPI MBOs via JCO MBOs, SAP BAPI MBOs via Web Services MBO, DOE, SAP NetWeaver Gateway. Perform additional JDBC installations and configurations and create deployment packages.Advanced SAP Control Center Admin > 12%Deploy MBO packages and Mobile Workflow applications to production servers, configure deployed MBO packages and Mobile Workflow applications. Import/Export Applications, and manage applications and users.Security Administration 8% - 12% Create Users, Groups and Roles (e.g. supAdmin). Configure Server Security: Secure Server Infrastructure, Secure Platform Administration, and Encrypt Application Payloads. Secure all ports and server infrastructure. Apply application authentication and map physical and logical roles.Sybase Unwired Platform Monitoring and Tuning 8% - 12% Configure monitoring and then perform monitoring tasks for the following: Security logs, synchronization, system queue status, data change notifications, device notifications (replication), package statistics, device users, cache activity. Apply performance tuning and configuration checks/adjustments for the following: Thread Count, Synchronization Cache Size, Java Heap Size, Log Levels/Settings, Number of queues, Connection Pool Size, general platform sizing. Create Synchronization and Cache Groups and Cache Policies: e.g. Cache Group/Cache Policy vs. Synchronization Group/Change Detection Interval.Sybase Unwired Platform Maintenance and Troubleshooting 8% - 12% Perform common maintenance tasks for the following: caches, connections, databases, devices and Users, error history, logs, packages, scheduled cleanup, and investigate CDB, device connection, SCC access, relay server-related errors. Perform backup and recovery for core platform components.

Implementation Planning, Installation and Design < 8% Determine and validate key target landscape infrastructure requirements: Relay server (RSOE and Relay Server platform), Server and Client License Requirements, Underlying User Store: i.e. LDAP. Describe how to scale the SAP Sybase Unwired Platform environment and define Domain strategies.Data Change Notification and Push < 8% Describe and create the two types of Data Change Notifications, implement DCNs with and without payload, and impliment Push Notifications.Product Introduction and Architecture < 8% Describe the SAP Sybase Unwired Platform architecture (Runtime vs. SDK) and the core components; identify installation prerequisites, and perform the installation of key components, and apply post-installation procedures.

MODULE ISybase Unwired Platform and Administration ArchitectureThe Sybase Unwired Platform is...Sybase Unwired Platform (SUP) is a mobility-enablement platform that allows you to create end-to-end mobile applications. It provides a server environment for hosting mobile business objects. SUP consists of a cache, also referred to as Cache Database (CDB), for storing mobile application data. SUP can handle data synchronization between clients and back-end data systems. It provides an integrated development environment (IDE) to create rich native applications or quick hybrid web container applications. SUP supports client APIs to create native mobile applications for BlackBerry, iOS, Windows Mobile, and Android devices.What is an EIS?Enterprise Information System (EIS) is a back-end system that serves as the source of data for Sybase Unwired Platform. Sybase Unwired Platform allows connectivity to many types of EISs, such as: Relational databases using Java Database Connectivity (JDBC); Simple Object Access Protocol or SOAP-based Web Services; REpresentational State Transfer or REST-based Web Services; SAP BAPIs and RFCs.Administrator TypesSUP has two types of administrators, namely, Unwired Platform Administrator and Domain Administrator. The Unwired Platform Administrator has cluster-wide administration rights, so he or she has full control of SUP. The Unwired Platform Administrator is the super user of the platform. The Unwired Platform Administrator can perform domain management, Server configuration, Device Registration, Monitoring, and Package Deployment and Management. The administrator is the domain owner and has all the domain administrator rights. The Domain Administrator has the rights to perform Domain manager tasks. The Domain Administrator can perform package deployment and management, server connections, security configuration, and role mapping. The Domain Administrator can only access the domains that the platform administrator grants.Administrator Tasks

The key tasks of an administrator are

..Mobile application deployment; ..Mobile application configuration and management; ..Mobile application user and device registration; ..Server configuration, maintenance, monitoring, and tuning.

To perform these tasks, you need to understand certain requirements such as

..System design required for the environment ..Security plan including level of security to be implemented ..Synchronization model to be used ..Back-end systems that applications must be integrated with ..Types of devices that need to be supported.Sybase Unwired Platform Architecture: First ViewThe Unwired WorkSpace is a Development IDE that allows you to create Mobile Business Objects (MBOs).MBOs contain Attributes and Operations. Attributes define what data is shown on the device, and Operations define how the data can be manipulated. By using the Unwired WorkSpace, you can create Native and Workflow applications and deploy them on Unwired Server.The Management Console is another component of the SUP architecture. The Sybase Control Console (SCC) is where an administrator can perform administrative tasks. For example, deployment of Workflows, creating a domain, security implementation, monitoring, and registration of user and devices.Sybase Control Center (SCC)The Sybase Control Center (SCC) is the key component of SUP where the administrator performs the tasks to manage the platform.

Generally, administrators use the SCC to

Configure the environment such as users, security, etc.; Manage application components; Monitor the health of the server.

The SCC is a browser-based utility where you can deploy and administer SUP. To access the SCC, you need to enter the valid URL. After navigating to SCC, you need to provide the user credentials. The user credentials are case-sensitiveTwo Primary Components of a Mobile ApplicationMobile Business Objects (MBOs) and the User Interface are the two main components of a mobile application.After the MBOs are created and deployed, developers create the User Interface. The User Interface is the front end that contains the screens, controls, and menus. The Workflow User Interface is created using the Mobile Workflow Forms Editor in Sybase Unwired WorkSpace. The Native User Interface is created in IDEs like Xcode, Eclipse, or Visual Studio.Types of Sybase Unwired Platform ApplicationsBy using Sybase Unwired Platform, you can build two types of mobile applications. They are Workflow applications and Native applications. The Workflow application is a simple request-response type application. For example, the employee requests vacation, and the manager approves or denies the application. Sybase Unwired Platform Workflow applications are not the same as SAP Workflow applications. The Native application allows access to more complex features on the device platform. It requires more coding, knowledge, and time. The developer can have more control of application development.Mobile Workflow Development ModelIn the Mobile Workflow Development Model, the first step is to create and deploy MBOs and Workflow on the Production Unwired Server. Next, you need to assign a workflow to the registered user. These two steps are common administrative tasks.Native Application Development ModelIn the Native Application Development Model, administrators deploy the MBOs on the Production Unwired server. Next, the developer generates the code to create the native application.Caching Mobile DataWhen using the mobile application developed using Sybase Unwired Platform, the devices do not communicate directly with the EIS. Therefore, the mobile device data is cached. Caching is controlled by the Data Tier. The Data Tier manages the cache database, also referred to as CDB or the Consolidated Database.Data Synchronization ApproachesOne of the challenges in building mobile applications is to keep the data in sync between the backend data source and the device. SUP supports two types of data synchronization, namely replication-based synchronization (RBS) and message-based synchronization (MBS).Replication-based Synchronization (RBS)Replication-based Synchronization (RBS) synchronizes data between a devices database and the servers cache database (CDB). RBS can be used for occasionally-connected devices that need access to data when offline. When offline, you can view, add, modify, and delete data from the source. RBS is optimal when you need to store large amount of data on the device. RBS requires the device to initiate the synchronization. The changes are sent to the data source in bulk. RBS is used by Windows, Windows Mobile, and BlackBerry platforms.Message-based Synchronization (MBS)MBS initiates a session to perform the synchronization for a bulk transform of changes. Whereas, Message Based Synchronization sends individual messages between SUP and the mobile device. If the device is offline, the messages are stored in a queue in the Data Tier and Advantage DB. When the device connects to SUP, the cached data is transferred to SUP. iOS Native applications and Workflow applications use MBS.Supported Device TypesYou can build mobile applications by using Sybase Unwired Platform for various devices such as Android which is limited to Mobile Workflow applications; BlackBerry; iOS devices; Windows XP, Windows Vista, and Windows Mobile (laptops and tablets), which are limited to RBS Native applications.

Device and Replication SupportRBS supports only these application types: BlackBerry Native applications Windows Mobile Native applications Windows Native applications MBS supports these application types: iOS Native applications All Mobile Workflow applicationsSybase Unwired Platform EditionsThe Sybase Unwired Platform Runtime contains Unwired Platform Server components; Sybase Control Center (SCC); Components that support Online Data Proxy for SAP NetWeaver Gateway.Sybase Mobile SDK is an installable component that provides an interface to develop mobile applications. SDK is used by developers to build the applications. Sybase Mobile SDK contains three components, namely Sybase Unwired WorkSpace; Native Object API and additional OData SDK; Hybrid Web Container.

SAP NW Gateway OData SupportThe Online Data Proxy contains the Unwired Platform Server components that support mobile applications consuming Open Data (OData) Protocol.Supported Operating SystemsThe Unwired Platform Runtime supports the Enterprise Server (Production) Edition that runs on 64-bit Windows 2003 Server or Windows 2008 Server. Sybase Mobile SDK supports Windows XP Professional with SP2 and SP3 Windows Vista Business, Enterprise, and Ultimate Edition; Windows 7 Professional, Enterprise, and Ultimate Edition versions for 32-bit and 64-bit.Platform Environment OptionsSybase Unwired Platform supports different environment types, such as Development Test; Single server installation; Clustered installation; Multitenant environments.Platform EditionsThe Unwired Platform Runtime has two editions.

The Enterprise Development Server components can be deployed to one or more server hosts. It supports clustering in a multinode environment. The Enterprise Development Server supports multitenant environments by allowing domains to be created in the server. Typically, the Enterprise Development Server is used in the test environment. The Enterprise Server is similar to Enterprise Development Server. The only difference is, the Enterprise server is used for a production environment. In addition, you need to purchase the number of client software licenses based on the need. Sybase Unwired Platform ArchitectureSybase Unwired Platform ComponentsSybase Unwired Platform contains five core distinct components. They are Relay Server; Unwired Server; Data Tier; Unwired WorkSpace and Mobile Application Development SDKs; Sybase Control Center (SCC).Component 1: Relay ServerThe first component in Sybase Unwired Platform is the Relay Server. The Relay Server acts like a reverse proxy that allows devices to communicate with the platform through the firewall that has common opened ports. The Relay Server is a set of extensions that runs on Microsoft IIS or Apache Web server.Component 2: Unwired ServerThe second component in Sybase Unwired Platform is the Unwired Server. The Unwired Server is an application server that acts as a container for MBOs. MBOs are packaged and deployed on the Unwired Server. The Unwired Server is a container for Workflow applications also. A production environment may have several Unwired Servers running in a clustered environment. Note:Workflows App se deployan directamente en Unwired ServerNative Apps se deployan en el deviceComponent 3: Data TierThe third component in Sybase Unwired Platform is the Data Tier. The Sybase Unwired Platform mobile applications do not talk to the EIS directly. Therefore, the Data Tier acts like a mediator between the device and EIS. The Data Tier is a cache for mobile application data. In addition, the Data Tier manages clustering and monitoring databases. The Data Tier manages the CDB and Advantage Databases. A single Data Tier can serve multiple Unwired Servers in a clustered environment. To do this, you need to have the Data Tier run on Microsoft Failover ClusterData Tier Databases 1The Data Tier supports five databases. The first two databases are the Consolidated Database (CDB) and the Messaging Database. The CDB caches runtime MBO data. CDB supports only the Sybase SQL Anywhere database. The Messaging Database is used in MBS applications. It is a temporary storage location for storing individual messages, when the device is offline. The Messaging Database supports only the Sybase Advantage database.Data Tier Databases 2The Cluster, Monitoring, and Logging databases are Data Tier databases. The Cluster Database is located in the server tier that contains configuration information about the cluster. It supports only the Sybase SQL Anywhere database. The Monitoring Database is used to collect server runtime metrics for analysis or troubleshooting, when enabled. Monitoring Database is a Sybase SQL Anywhere database. The Logging Database is used to collect application run-time metrics used for analysis or troubleshooting, when enabled. Logging Database is a Sybase SQL Anywhere database. Sybase Unwired Platform ClustersWhen installing Sybase Unwired Platform, a cluster is automatically created. You can cluster both the Server and Data tiers in a server. A server can be a member of only one cluster. Clusters serve two common purposes. They provide high-availability / failover and allow Load Balancing. Load balancing is implemented using O/S or third-party hardware and/or software solutions. Primitive (round-robin) load balancing can be achieved using the Relay Server. Cluster StrategiesClustering in a single machine provides a nonredundant environment. It is used by a developer where the Data and Server tiers reside on the same machine. Clustering on two nodes is a primitive architecture where the Data Tier is on one node, and the Server Tier is on another node. Clustering on three nodes is an architecture with two Server Tier nodes and one Data Tier node. Clustering on N+2 nodes is a redundant architecture with multiple Server Tiers supported by a relay server(s) and two Data Tier nodes.Component 4: Unwired WorkSpaceThe Unwired WorkSpace allows developers to manage Mobile Application Projects; design and deploy MBOs to development or test servers; design, deploy, and customize Workflow applications; generate the code to be used with the client API to create Native applications; manage the connections to EIS sources; explore EIS data. You can drill down into an SAP BAPI to view its operations, inputs, and outputs.

MODULE IISystem Design and InstallationDesign Considerations for Sybase Unwired Platform.

Installation ConsiderationsBefore you begin installing Sybase Unwired Platform, consider these pre-requisites: The type of environment that you are building (Is it a development, testing, or production server) The extent of clustering capabilities usage in your environment The Operating System on which the platform will be installed The need of a Microsoft Failover Cluster in your environment The implementation of load balancing in the environment The number of Server Tier nodes that you wish to install The number of Relay Servers that are required (if any)

Clustered EnvironmentsA cluster consists of two or more servers or nodes that work together to provide application services. The benefits of creating a clustered environment are redundancy or fail-over and load balancing. Load balancing is important in a more scalable environment, where you can easily install additional servers to the cluster based on your business needs. In a Sybase Unwired Platform environment, two types of clusters can be created. They are the Server Tier and the Data Tier. When installing the Server Tier, a cluster is automatically created. You also have an option to name the Server Tier cluster during installation. Data Tier clustering requires Microsoft Failover Cluster.Environment OptionsThe Sybase Unwired Platform can be installed for different reasons.In a scenario where developers need a local installation on their machines, a single server environment can be built, where the Server Tier and Data Tier exists on the same machine. Another scenario is where developers need a production-like environment to test their applications prior to migration to production. In such a case, a multiple server environment can be built, where the Server Tiers and Data Tiers are installed on separate machines or may be clustered.Additional Configuration OptionsAdditional Configuration options include options for load balancing and Relay Servers. In your environment, a load balancer can be added in front of the Relay Server by enabling a Windows Network Load Balance Cluster. To do this, you need to provide static IP addresses. You can also use third-party load balancing for hardware and/or software. When using Relay Servers, a Single Relay Server option results in a chokepoint with no redundancy. To embed Relay Servers with Windows Failover Cluster, you need to provide Active Directory, Domain, and DNS. The Failover cluster is always mandatory for a Data Tier.Downloads and Licensing processesInformation about LicensesSybase Unwired Platform uses a process called SySam to manage licenses. The SySam license file controls the base number of devices or clients that can be registered, the number of servers you install in your cluster, and the expiration dates for devices and servers. Each server in the cluster must be licensed. Multiple servers cannot share a single license. However, the servers of a cluster can share the device or client licenses.License ModelsThe two types of SySam license models that are available are the Unserved or local license that is specifically tied to a machines Physical Address and host name. You can access the Physical Address or host name by using a command-line utility. Use the Physical Address of the primary wired Ethernet adapter. The Served licenses are licenses that are generated and installed into a SySam license server and used during product installation.Selecting License TypeThe CPU License or CP is only available for enterprise server editions.Creating Client LicensesClient licenses are mandatory and must be generated. The single license allows the client to run only on one application, whereas unlimited licenses allow the client to run on multiple applications. Licenses are generated based on classes. The Class A license is generated for hand-held devices such as iPhone, WM, and BlackBerry. The Class B licenses are for Win32 devices, such as Laptop or tablet computers.Post Installation: Location of LicensesAfter installing the license file, you can view the license file in the licenses folder.C:\SYBASE\UNWIREDPLATFORM\SERVERS\UNWIREDSERVER\LICENSESChanging licenses after installationAfter installing the software, you can change the license. During the installation, the bin folder is created. The bin folder contains the license.bat file that allows you to upgrade or update SUP licenses without having to rerun the installer. It can be used for both served and unserved license models. You can change licenses at a command prompt using the license.bat PE LT command.Microsoft Failover ClusterPreparing to Install Microsoft Failover ClusterThe first step to install Sybase Unwired Platform is the Data Tier installation. If Data Tier clustering is required, you first need to install the Microsoft Failover Cluster. The Microsoft Failover Cluster can be configured on Windows Server 2008 Enterprise R2 with the assistance of the IT department. The IT team will provide static IP addresses for the server. Before you begin installing the Microsoft Failover Cluster, you need to install the Active Directory Domain Controller and a DNS server on the Domain Controller.Domain CreationAfter selecting the Active Directory Domain Services option in the Server Roles page, you need to provide the Fully Qualified Domain Name (FQDN) of the forest root domain.

Enabling the DNS ServerAfter providing the domain name, you should enable the DNS server as a part of the Active Directory domain controller installation.Post Domain WorkThe domain controller will not contain any of the Sybase Unwired Platform software.The role of the domain controller is to manage other servers within that domain. You need to create additional servers that will host the Data and Server Tiers. The class lab shared environment has two Data Tier nodes named supdata2 and supdata3. They act as an active and passive server respectively. These two servers are members of the supcourse.domain.Adding the Failover Cluster FeatureAfter installing an Active Directory domain and a DNS server, you need to install the Microsoft Failover Cluster. In the active machine or supdata2, in the Server Manager Console, under the Features section, click Add Features and then select Failover Clustering to install Microsoft Failover Clustering. After the Failover Clustering feature is installed, you need to configure the cluster based on your business needs.Create Shared StorageIn this setup, the Data Tier requires a shared storage to control the physical database files. To set up or view the shared storage, you need to use the Failover Cluster Manager utility. After you installed the Microsoft Failover Cluster and created a cluster, the Failover Cluster Manager utility is installed. In the Failover Cluster Manager utility, expand the Storage node to view the shared storage. This shared storage could either be a disk cluster or a RAID array to store the database files. For the class lab environment, a shared E drive is created to be used by the members of the cluster for storage.Deployment Edition InstallationPre-SUP Installation Requirements During the installation process, the User Account Control (UAC) should be temporarily disabled. The user who is installing Sybase Unwired Platform should have administrator privileges. Therefore, the user should run the setup.exe file with the Run as Administrator option. If the company policy permits, create a new user account with static credentials for the install. Otherwise, ensure to update the password for the Sybase Messaging Service every time the user password changes. Multiple Installs RequiredWhen creating a clustered environment, you need to run the Sybase Unwired Platform installer multiple times. First, the Data Tier nodes are installed. 3One installation for each node of the Data Tier. Next, the Server Tier nodes are installed. Similar to the Data tier, you will install for each node of the Server Tier. Choosing Install License TypeSybase Unwired Platform supports two types of licenses. They are the Unserved or the local License type and the Served or the remote License type. An unserved license type is a standalone seat license that is managed on the local machine. A served license type is a standalone seat license that is managed from a license server. It requires a license manager host name and license manager TCP port before proceeding further. Select the type of license you wish to install and then click Next.Choosing Edition and Product License TypesTo install a production server, you need to select the Enterprise Server option. For Enterprise Server, the license type would be CPU License. For the Enterprise Developer edition, the license type is Development and Testing. Based on the business requirement, you need to select the edition and license type.Supply SySam DetailsIf you choose the served license type, you need to specify the host name and port number of the SySam license server. Before you begin installing Sybase Unwired Platform, you need to install the SySam license server.Enable Data Tier ConfigurationIn order to change the defaults or install the Data Tier into a clustered environment, the Configure data tier option should be enabled.Data Tier Databases ConfigurationAfter you enable the Data Tier configuration, you will be prompted to configure the databases in the Data Tier. You need to set the port numbers and passwords for all the databases. The Cache database server, Cluster database server, and the LogData database server are SQL Anywhere databases with default password SQL that can be changed during the installation process. The SQL Anywhere database has .db and .log files. The transaction log is the file that is updated on every transaction that occurs between the back-end and front-end. By checking the checkbox, you can specify separate locations for these files. To install into a Microsoft Failover cluster, enable the High availability optionInstallation Progress and CompletionThe time to install a Data Tier node is approximately 10 minutes. At the end of the installation, you need to ensure that there are no errors reported by the installer. You should also confirm that the four Windows services namely Advantage Database Server, Sybase Unwired CacheDB, Sybase Unwired ClusterDB, and Sybase Unwired LogDataDB are created. Finally, you should check if there are any errors logged in the Windows Event log.Data Tier Servers DirectoriesThe Servers folder contains the most important files stored in the folders Advantage, SQLAnywhere, and Unwired Server. The Advantage folder is used by the Messaging server for MBS applications. The SQLAnywhere folder is used primarily by RBS applications. The Unwired Server folder contains only a minimum number of required files, as this is not a Server Tier installation.After installing the first Data Tier node, you can begin installing the second Data Tier node. Before you begin installing the second Data Tier node, you should shut down the active node of the Microsoft Failover Cluster. This allows the passive node to become active, giving it access to the shared data storage E: drive. Repeat the installation of the second Data Tier node in the same way as the first was installedThis completes the installation of the platforms Data Tier.Data Cluster Client Access PointBefore installing the Server Tier nodes, a Client Access Point must be created for the Windows Failover Cluster. The Client Access Point can be created using the Windows Failover Cluster Manager console. In the Failover Cluster Manager console, log in as the Domain Controller Administrator. Right-click Services and applications and then select Configure a Service or Application. This starts the High Availability Wizard. High Availability WizardThe High Availability Wizard configures the cluster so that another server automatically resumes the service or application when a server fails. If the service or application itself fails, it can be automatically restarted either on the same server or on another server in the cluster depending on the options specified. This is also known as failover.Bring All Resources OnlineAfter adding all of the platform services as resources, the client access point on the Failover Cluster Manager screen will show the name of the client access point, the drive where it is stored, all the resources, and their status as offline, initially. Now, right-click on the statuses and set them to online.Adding a Shared Folder to Generic ServiceA shared folder must be added to the Client Access Point. To add a shared folder, right-click the client access point and then select Add a shared folder. Choosing Shared Folder LocationAfter selecting the Add a Shared folder option, the Provision a Shared Folder Wizard opens. Here, the first step is to specify a shared folder location. In the Location box, type in the path or click Browse to locate the folder.Specifying NTFS PermissionsIn the second step, you need to set the NTFS Permissions. As an administrator user, you need to have Full Control rights to the specific folder to set the NTFS permission. Select the Yes, change NTFS permissions option and then click the Edit Permissions button. In the permissions for administrator section, ensure that all the permissions are allowed and then click OK.Setting SMB PermissionsWhile setting SMB Permissions, click the option to enforce full permissions for Administrators.Advantage Database Authentication Error - 1After installing the Server Tier, the status of the Advantage Database service will be online. If the service is offline, then a problem occurred when authenticating the Advantage Database Server. To troubleshoot this problem, navigate to the Data Tier server and check for the registry key value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Advantage\Configuration\TPS_LOGS to find the location of the adsserver.ini file. The default value is: C:\. If the adsserver.ini file does not exist, create it in the location identified in the registry key value, on each data tier server.End of Data Tier InstallAt the end of the Data Tier installation, you will notice that both active and passive nodes are installed. The Client Access Point is created. You can now begin the Server Tier installation. Firewall ports MBS port 5001 and RBS port 2480 may need to be opened for the Server Tier installation to be successful, and Windows Firewall may need to be disabled.Providing Data Tier InformationSince you chose to configure the communication port, the installer prompts you to provide data tier information. The Host name builds the connection to the data tier. Enter the information required regarding Cache database, Cluster database, and LogData database along with the password, which would by default be SQL unless changed during the installation.Server Tier ServicesThe Server Tier installs two Window services, the Sybase Control Center 3.2 and the Sybase Unwired Server.Installation of Second Server Tier NodeRun the Sybase Unwired Platform installer again to install additional nodes within the Server Tier cluster. Three different installation options are available: Install the data tier for your Unwired Platform cluster Install the first server node and connect it to the data tier Install an additional server node and connect it to the data tierVerifying Cluster Members are RunningUnder the Unwired Platform Cluster, click on the Servers tab to view the Server names and their role and status. Use the Sybase Control Center (SCC) to verify that the members of the cluster are running.Post Installation TasksLogging Into the SCCThe login page for the Sybase Control Center is displayed. You can log in to the SCC using the credentials supAdmin as the user name and s3pAdmin as the password. These are the default credentials for a deployment or production server.SAP JCO InstallationSAP JCO installation is mandatory for communications between Sybase Unwired Platform and SAP ECC. The installation is now automatic in Sybase Unwired Platform version 2.1. Downloading DBMS JDBC DriversAs part of the Sybase Unwired Platform installation, the Sybase JDBC drivers are also installed. If you are going to use DB2 or Microsoft or Oracle as the backend EIS, the JDBC drivers for those DBMSs must be downloaded and installed.

Installing JDBC DriversFolder: \UnwiredInstallDir\Servers\UnwiredServer\lib\3rdparty\The JDBC drivers are contained in Java Archive or JAR files. The downloaded JAR files are placed in the Server Tier. There are multiple server tiers, and the JDBC drivers must be placed on every node of the Server Tier. After placing the JDBC drivers, you should restart the serverRelay Server DefinedThe Relay Server is a feature provided by Sybase SQL Anywhere. It is a communication architecture for mobile devices that communicates with Sybase mobile middleware such as Sybase Unwired Platform. A Relay Server acts like a reverse proxy, allowing devices to communicate through the firewall with the platform through commonly opened ports such as port 80. The relay server is a set of extensions that are installed on either Microsoft IIS Web Server or Apache Web Server.Outbound Enablers (RSOE)One or more Outbound Enablers manage communications between the Unwired Server and the Relay Server. The RSOE opens outbound HTTPS connections to the Relay Server to handle both inbound and outbound communication channels. Each RSOE is an Unwired Server process that manages communication on either Messaging port 5001 or Replication port 2480.Relay Server Install FilesThe 32-bit and 64-bit ZIP files for the Relay Server installation are part of the install media and are located in the modules\relayserver folder. You have to extract the appropriate files contents to the Relay Servers wwwroot folder. Path ModificationThe servers Path environment variable is modified in order to include the wwwroot\ias_relay_server\Server folder.Adding a Relay Server ConfigurationTo add a relay server configuration, click the Relay Servers tab on the root node of the Sybase Control Center and then click the New button.Relay Server Farm ConfigurationWhile configuring the Relay Server Farm, you have to specify the farm id(s) and types in the Unwired Server farms information page. You also have to specify a server node id and a token number for each farm id.Relay Server Configuration FileNow that you have completed Relay Server configuration, you will generate the relay server configuration file. In the Relay Servers tab, choose a relay server configuration and then click the Generate button to create an rs.config file based on the defined farms. After selecting the type of configuration for the rs.config file, click Next to save the file in the desired location.Editing the rs.config FileThe generated rs.config file can be edited by changing the start attribute to a value of auto. The verbosity attribute also has to be changed to the maximum value of 5. This setting enables debug information to be written to the Relay Server log fileDestination for Relay Server Config FileAfter performing necessary edits, the generated relay server configuration file is copied to the C:\inetpub\wwwroot\ias_relay_server\Server folder on all of the relay server(s).SQL Anywhere 12 Environment VariableYou can create a new machine system environment variable named SQLANY12. The SQLANY12 variable should specify the relay servers install location. (In Windows/System Properties)ISAPI Handler MappingsAfter updating the Relay Server with the new configuration file, you will edit the handler mappings. In the /ias_relay_Server Home page of the Internet Information Services Manager window, double-click the Handler Mappings icon to edit the Relay Servers ISAPI handler mappings.Enabling ISAPI-dllOnce the Relay Servers ISAPI handler mappings are edited, you have to enable the ISAPI-dll. In the Handler Mappings page, you will notice that the ISAPI-dll is disabled by default. To enable the ISAPI-dll, select ISAPI-dll and then click the Edit Feature Permissions link. In the Edit Feature Permissions dialog box, click the Execute check box to enable the permission.Configuring a State Manager as a ServiceThe dbsvc utility that is part of SQL Anywhere allows creation of Windows Services. A service is created to run the State Manager as a process on a Relay Server node. You should also ensure that the C:\Sybase\logs directory exists for the service to start successfully.Creating Outbound Enabler ConfigurationsTo create an outbound enabler configuration for a given node of the server tier, you will first choose its Server Configuration. Next, select the Outbound Enabler tab and then click the New button.

Configuring Outbound EnablerAfter creating the outbound enabler configuration, you will next configure the outbound enabler. In the Update Configuration dialog box, you will choose a farm type, a relay server host, and then select the server node id

MODULE IIIUnwired Workspace Overview for AdministratorsUnwired WorkspaceInstalling the Sybase Mobile SDK 2The ED(Enterprise Development Server) license is recommended for development environment and not for production purposes. Each installable component is available on the host and clustered systems. For a development server, the license type is set to DT(Development and Test License Type Servers). This type of license provides unlimited license on CPU/Cores or host configuration for single host or multiple hosts or clusters. This license is applicable for Enterprise Development Server and Enterprise Server.Unwired WorkSpace User InterfaceLet us explore the Sybase Unwired WorkSpace user interface. The WorkSpace Navigator pane lists all the files related to a project. The Enterprise Explorer pane contains connection profiles information. In this pane, you can navigate to the Web Services, SAP Servers, Unwired Servers, REST Web Services, and Database Connections. The Properties View window displays the properties of the selected object. The Diagram Window displays project diagrams. The Problems tab displays warnings and errors generated in a mobile application project.Introduction to the Mobile Business Objects (MBOs)Mobile Application RequirementsTo create a Native or Workflow based mobile application, you need to create two main components. These are Mobile Business Objects and User Interface. MBOs are designed using the Unwired WorkSpace and are deployed to an Unwired Server. Native UIs are created with the IDE of your choice. Workflow UIs are created with the Unwired WorkSpace by using the Mobile Workflow Forms Editor. MBO DefinedAn MBO is an object that contains attributes and operations. The attributes define the data-makeup of the object, and operations define what the object is capable of doing. Native and Workflow applications contain screen to display and edit data. The fields that are displayed or edited are derived from the MBOs attributes. The types of changes that can be performed depend on the MBOs operations.MBO Data SourcesMBOs extract data from sources such as SAP BAPI/RFCs, Database tables or stored procedures, SOAP Web Services, and REST Web Services. In this case, the MBO attribute will be mapped to a column in a database table. When data is extracted from external sources, you need to create connection profiles in the Unwired WorkSpace. These connection profiles provide design-time connectivity needed for development and testing.MBO AttributesAttributes are mapped to a data source when an MBO is created. For example, if the Data Source is a database table, then, in the Attributes Mapping tab, Attributes are mapped to columns using the SELECT statement.MBO OperationsMBO Operations have a name and a type. The operation types are CREATE, UPDATE, DELETE, and OTHER. The OTHER operation type does not allow data manipulation. Configuration of the Unwired WorkspaceConnection ProfilesYou can create connection profiles in the Enterprise Explorer pane. EIS Connection profiles must be created before you begin application development.Create New Unwired Server Connection ProfileYou can create a New Connection Profile to the Unwired Server with the help of connection profile parameters. The default password is set to s3pAdmin. The Port number was set during installation.Configuration of the Unwired WorkspaceImporting and Exporting ProjectsMobile application projects and connection profiles can be exported from one Unwired WorkSpace to another. The exported mobile application projects and connection profiles retain all reference information such as data sources, roles, generated code, and connection information. When a project is exported from Unwired WorkSpace, the connection profiles are not part of the export.Exported SAP Connection ProfileConnection profiles are exported as XML files, and the credentials are visible unless the file is encrypted.Importing a Connection ProfileOn the Enterprise Explorer, click the Import button. Specify the exported profile path. When the import process is complete, the connection profiles will be automatically refreshed in the Enterprise Explorer.Post-Import TasksAfter importing the project and the connection profile to an Unwired WorkSpace, you may need to modify the project components. You should verify that the connection profiles are referencing the correct Data Source and Sybase Unwired Server. You should also verify that the connection profile is using the appropriate credentials to connect to both the back-end data source and the Unwired Server.Project DeploymentDeployment MethodsOnce a mobile application or workflow is complete, it must be deployed to the Unwired Server. Developers can use Unwired WorkSpace to deploy an application to a test server. Administrators are responsible for deploying applications to a production environment using the Sybase Control Center.Setting Deploy OptionsWhen deploying an application, you need to select a deploy mode and verify the version number, package name, and the synchronization method.Deploying JARs. During deployment, a JAR file can be selected to deploy with the application. This wizard to deploy JARs is enabled only when the developer uses the Advanced Developer profile option.

MODULE IVUsing Sybase Control Center for AdministrationSybase Control Center (SCC)Using the Sybase Control Center (SCC)The Sybase Control Center (SCC) is an administrative tool used in the Sybase Unwired Platform. It is installed with the Runtime package. A Windows service named Sybase Control Center 3.2 is installed on each of the Server Tier machines. The Sybase Control Center has two administrators, the Platform Administrator and the Domain Administrator. The Platform Administrator has a cluster-wide administration access to the Unwired Platform. The default username is supAdmin. The Domain Administrator access is limited to a domain assigned by the platform administrator. The default username is supDomainAdmin.Server Environment AdministrationBasic Administration Tasks

The basic administrative tasks on a server environment are

monitoring licenses reviewing or modifying communication and DCN ports managing replication-based synchronization settings managing message-based synchronization settings configuring Apple Push notifications configuring BlackBerry Enterprise Server communications creating Domains; managing EIS Connections.Monitoring LicensesA license is mandatory for each server tier and mobile device. However, these licenses have expiration dates. The devices will not be able to connect to the server, if there are not adequate licenses. All the license related error messages are logged in the Server log. Monitoring the number of licenses and their expiration dates are part of the administrators tasks.Reviewing Licensing Information 2Sometimes, the number of devices exceeds the total device license count. In such case, the access to the server is not permitted unless the license allows an Overdraft mode. An overdraft mode temporarily allows devices to access the server during peak times.Reviewing Licensing Information 3When the Device license expires, the Unwired Server generates a license expiration error, and the connection requests from the registered devices are rejected.Exceeding License LimitsWhen users exceed license limits, administrators can upgrade the license and manually change the license by using the batch file named license in the \bin folder. Alternatively, administrators can delete the inactive device users.Server Communication Ports 1Developers must create Unwired Server connection profiles in the Unwired Workspace. These profiles use port 2000 to access the server.Replication Listener PortsIn the Replication tab, administrators can configure or monitor the ports used by the RBS device applications. The listener ports use a proprietary protocol based on HTTP. In the Replication tab, administrators can set the maximum cache size and the number of worker threads used in synchronization. If the client application performance is not acceptable, increase the synchronization cache size and thread count. 2480 normal port and 2481 for secure portReplication NotificationWhen the CDB changes, notifications are sent to the device. As part of the notifications configuration, you can either enable or disable the server-initiated that is push-based or client-initiated that is pull-based notifications. These notifications require application code. You can also specify the frequency that the Servers notification table is polled.In the Messaging tab, you can configure the ports used by RBS device applications. It uses a strongly encrypted HTTP-based protocol. Listening on multiple synchronization ports may provide greater flexibility and reliability. Consider adding another port, when virus detection results in dropped packets or connections. All messaging traffic is still funneled to a single listener. Default ports: 5000 normal and 5001 for secure portApple Push Notification Configuration 2To create and download the Certificate file and to obtain a password, you must be a registered Apple developer. The MobileWorkflowPushDistCert is a sample Certificate file provided with SUP.2195 and 2196 is used for Apple PushBlackBerry Enterprise Server ConfigurationBlackBerry devices must go through BlackBerry Enterprise Server (BES) before accessing the Unwired Server. In the Messaging tab, in the BlackBerry Push Configuration section, administrators can configure the BES server ports. By default, port 8080 is used for the BES server connectivity.DomainsDomains provide a logical partitioning of a hosting organizations environment. For example, a host of Sybase Unwired Platform can create domains for different departments within a company or even have domains that support individual companies. Server connections, packages containing MBOs, role mappings, logs, and so on can be viewed and managed within a domain. Domain Administrator has the rights to perform domain management tasks such as package deployment and management, connection profiles, and so on.Reasons to Create DomainsThere are a number of reasons to create domains. Basically, domains allow multiple customers to be segregated within the same Unwired Server cluster. Administrators can configure a different security configuration for different Domains.This reduces exposure since the Domain Administrator can access only certain portion of the overall Server environment such as package management, logs, connections, and security within the domain.EIS Connection ManagementMBOs require connections to back-end data repositories. EIS connection supports different types of connectivity. They are JDBC, SAP, and Web Service such as SOAP and REST. Connection profiles are created during the Unwired WorkSpace design-time, so that a developer can design applications. The Administrator must create server connection pools for the corresponding connection profiles. The Developer can also create server connection pools from Unwired Workspace.Other Connection Types SOAPThe connection profiles for SOAP Web Services require the address of the service, specified with a URL. The authentication properties such as user name, password, and certificate can also be specified by clicking the command. Other Connection Types - RESTThe REST connection profiles are similar to SOAP. The REST connection profiles require the Resource Base URI.Other Connection Types - DatabaseThe database connection profiles require port numbers, JDBC Database URL, user id, and password.Creating a Connection TemplateConnection templates provide common connection properties and values for a specific pool type.Package ManagementPackage ManagementAdministrators are responsible for managing packages. The administrative tasks that are part of the Package Management are deploying MBO packages to production servers, deploying Mobile Workflow applications to production servers, configuring deployed MBO packages, and configuring Mobile Workflow applications. Using the SCC to Manage PackagesAdministrators can manage packages by using the Sybase Control Center. In the Sybase Control Center, expand the Packages node, and then select a package you wish to configure. On the right pane, Sybase Control Center provides various options to enable or disable packages; configure Package settings; map physical roles to logical roles; manage Cache group settings; manage Synchronization group settings; configure subscription templates; administer Applications; review Client logs; view asynchronous operation replay; and view Personalization keys.Package Deployment ProcessTo deploy a package to a server, you need to specify certain configuration settings in the Deploy Wizard. In the Deploy wizard, you need to define the deployment unit or deployment descriptor and deployment mode; select the production-level security configuration for the package; remap the roles to production values; and configure the production server connections.Deploying MBO Packages to Unwired Server 4After selecting the jar file, you need to specify the deployment mode. The different types of deployment modes are the Update mode, which is the default mode, that updates the package with updated objects; the Noclobber mode that prevents the deletion of a package of the same name on the target server from being deleted; the Replace mode which replaces a package on the server; and the Verify mode that verifies a package and returns any errors. However, it does not deploy a package. Select a deployment mode and then click Next.Deploying MBO Packages to Unwired Server 9After successful deployment, a message is displayed. The package is deployed to the Unwired Server and is displayed in the Packages view of the Sybase Control Center. Regardless of whether an MBO package is deployed as an RBS or MBS package, it is labeled as UNIFIED in the Sybase Control Center. Unified packages can be used for both replication and messaging device application clients.Configure a Cache GroupWhile setting the cache interval, the EIS data is cached in the consolidated database (CDB), and the devices get their data from the CDB. You have to set the interval to balance between devices getting stale data and the network traffic involved in updating the cache. A higher value makes the data more stale, whereas a lower value would cause a delay when the client synchronizes because the cache would be updating more often. You can set the Refresh Policy as Scheduled or On Demand. If the cache group was created as scheduled, then the Schedule tab would be active and the cache schedule could be modified.Warning About Cache GroupsThe default cache group is set to On Demand with a cache interval of 0h 0m 0s. This means that every time the client synchronizes, there will be a delay because the cache has to be updated first. This may not be the best performing option possible.Synchronization Groups and SubscriptionsThe Unwired Server alerts the device users to update mobile business object data based on synchronization group and subscription settings. When the MBOs in a synchronization group are updated, the users subscribed to those synchronization groups receive either a data update or a device notification which depends on the type of application. Notifications to Update Client Data 1Notifications to update client data vary depending on the type of application. In MBS or message-based synchronization applications, clients directly receive data updates. The change detection interval for the synchronization group determines how often the MBS applications push MBO data to the client when cache refreshes occur. In RBS or replication-based synchronization applications, clients receive device notifications. Both the change detection interval of the synchronization group and the notification threshold of the subscription determine how often the RBS clients receive device notifications.Notifications to Update Client Data 2Data updates through device notifications occur as the Unwired Server checks the cache for data updates to MBOs according to the change detection interval configured. If there are data changes, the server generates device notifications. Once the RBS subscription notification threshold expires, the Unwired Server delivers the device notifications to clients subscribed to the synchronization group. Clients receive the device notifications and synchronize data for the MBOs. Notifications to Update Client Data 3Administrators can use subscription templates to specify the notification threshold for a particular synchronization group. These templates are used to create subscriptions for device users. For RBS devices, the subscription settings ultimately determine when the device notifications are delivered. For example, if data for a synchronization group is updated every two hours but a device user's subscription indicates a notification threshold of three hours, the Unwired Server postpones delivering these updates for three hours. Configure a Synchronization Group 1Synchronization groups are defined by the developer and are part of the deployment package. Changes to the Change Detection Interval can be made by the administrator after the package is deployed. The administrator can choose a package and select the Synchronization Group tab. Then, select the group to manage and click Properties.Configure a Synchronization Group 2Change detection interval defines the time that the push notifications are sent if a change is detected. The interval can be in hours, minutes, or seconds. Change detection triggers a diff-calculation for sending data changes to subscribed clients. These calculations can adversely affect performance. Therefore, the administrator and developer must jointly determine this interval value, before configuring it in a production environment.Managing SubscriptionsSubscriptions define how data is transferred between a users mobile device and the Unwired Server. During data modification, users are notified about the changes. Unwired Server allows push updates to the users mobile device. Administrators can create subscription templates for RBS packages to allow a device user to be notified when information is available. Subscription templates are optional and required only if an administrator wants to define preset subscription properties. Creating a Subscription Template 1Enable / Configure the Notification Mailbox 1Notification Mailbox monitors incoming emails to Unwired Server. It uses a listener to scan all the incoming email messages delivered. When the listener identifies an email message corresponding to a matching rule, it knows which workflow application needs to process the message. The listener then uses a distribution rule to determine which workflow user receives the special email that allows displaying the workflow forms. Saving changes to the Notification Mailbox configuration deletes all email messages from the account; therefore it is necessary to backup existing messages before saving changes.Enable / Configure the Notification Mailbox 2In the Sybase Control Center, select the Workflows node, and then select the Notification Mailbox tab to configure the Notification Mailbox. From the Protocol drop-down list, you can either select POP3 or IMAP, based on the protocol of the mail server. The Use SLL option, when enabled, encrypts the connection between the Unwired Server and the email server. In the Server and Port boxes, enter the connection properties required for the Unwired Server to connect to the email server. Default values of the port are 110 for unencrypted data and 995 for encrypted data. In the Truncation limit field, enter the maximum number of characters that can be taken from the original email message and downloaded to the client during synchronization. Messages will be truncated to the number of characters specified. The default truncation limit is 5000. In the Poll seconds field, enter the number of seconds the listener sleeps between polls. During each poll, the listener checks the master inbox for new email messages to process. The default duration is 60 seconds.Configuring a Mobile Workflow PackageWhen configuring a mobile workflow package, you can set general properties, matching rules, and context variables; assign workflows; and assign users properties. The Mobile workflow package must be deployed before the configuration.Configure Matching Rules 1Configure Matching Rules 3From the Field drop-down list, select a field in the email from which the parameter value should be extracted. The fields could be From, To, Subject, CC, Body, or Custom. If you select From, then the parameter value is extracted from the line of the email message that indicates the name of the sender of the email. The parameter value can also be extracted using expressions. An expression includes various operators, such as ##Equals which specifies that the field must exactly match the text in the label; ##Begins with which indicates that the field must begin with the specified text in the label ##Ends with which indicates that the field must end with the specified text in the label; ##Contains which specifies that the text in the label must exist somewhere in the field; and ##Regular expression which searches for text that matches the specified pattern. Configure Context VariablesTo configure the context variables of a workflow application, click the Context Variables tab. The variables for the mobile workflow are displayed. Timeouts are displayed in seconds and Message Length in bytes. An administrator can change some of the variables if necessary for a production environment. Select the variable and click the Modify button to change a context variable.Assign Workflows to Device Users 1Users can be assigned to or unassigned from mobile workflow packages through the Application connections tab. You can click the Assign workflow button to get the user list.Application and User Management tasksApplications in the SCCAdministrators manage and monitor applications using the Sybase Control Center. An application is defined as a native application or mobile workflow container instance on a device. Native application is a single binary deployed to a device that may use one or more MBO packages. Mobile workflow application is a collection of workflow packages and constitutes as one application. One or more MBO packages can be assigned to an application.When administrators deploy an MBO package to the Unwired Server, applications are automatically created. The default application name is the package name. Application ID is automatically assigned upon application deployment. It differs based on type of application client. The Default and HWC or mobile workflow applications are created during Unwired Server installation and are displayed on this screen.Modify / Review Application PropertiesOnce an application is registered, you can associate the application with one or more domains and packages. On the Application tab, select an application and then click Packages to view the application properties. In the Review assignment window, the domains and packages assigned to the application are displayed. Click the plus button to add a domain or package to the application.Application ConnectionsApplication connections can be made by associating an application instance with a user. One application can be used by many users, or a user may be associated with many applications. Click the Register button to create a new application connection. This is similar to the Device Users in Sybase Unwired Platform releases prior to release 2.1.Register Application ConnectionsBefore assigning users to workflow applications, you need to register and activate the users.Modifying Application ConnectionsWhen a device activation code expires, you can reregister an application connection by using the options in the Application Connections tab. You can also clone an application connection in the event that a user gets a new or alternate mobile device. Cloning retains the user information so it can be associated with another device.

MODULE VData Change Notification DCN and PUSHData Change Notification and PushThe Data Change Notification (DCN) is a mechanism that alerts and sends EIS changed data to the CDB associated with an Unwired Server. The DCN messages are formatted using JavaScript Object Notation (JSON) and are sent over an HTTP or HTTPS connection. The DCN listener ports are 8000 for HTTP and 8001 for HTTPS/secure. Push is a mechanism that allows Unwired Server to notify clients of new MBO data without waiting for the next MBO synchronization. Administrator DCN ResponsibilitiesDCN administrator is responsible for creating the DCN messages. For example, administrators can create an after-update trigger that will create the DCN message and deliver it to the Unwired Server. Administrators should review the DCN processing logs and work with responsible parties to correct the error conditions. Administrators are also responsible for configuring secured and unsecured ports to process DCN messages.Data Change Notification Advantages

When data is modified in the back-end EIS system, the Data Change Notification allows you to re-populate only the changed data and not the entire MBO cache data. It also allows the MBO cache to be updated in near real-time by the EIS rather than on an Unwired Server driven schedule or client initiated synchronization. This reduces the traffic to and from the Unwired Server. Data Change Notification ensures that there is consistency between the EIS and the Unwired Server CDB.Change Reconciliation with DCNIn order to implement DCN from the EIS to the actual device, two changes must be reconciled which include the change from the EIS to Unwired Server CDB for refreshing the data and the change from the CDB to the client database for synchronization.Types of DCNThere are two types of DCN. They are Regular DCN and Workflow DCN. The Regular DCN provides Native Mobile Application DCN functionality to replication-based synchronization (RBS) and message-based synchronization (MBS) clients. The Workflow DCN (WF-DCN) provides DCN functionality to workflow clients by extending regular DCN for MBS workflow clients.DNC With or Without PayloadThe DNC with Payload requires a JavaScript Object Notation (JSON) string, dcn_request. This string contains one or more :upsert and :delete operations. It directly updates the Unwired Server cache (CDB), with either of the built-in direct cache-affecting operations such as :upsert for update or insert and :delete. However, the DNC without Payload instructs the Unwired Server to sync an MBO for read operation and invokes one or more MBOs CUD operations.DCN Backend ConfigurationRegular DCN and Workflow DCN must be configured either with or without Payload. Both these DCN types can be created through database triggers; EIS system events external integration processes such as user exits and Java.The EIS systems configuration is required to support JSON and HTTP(S). The EIS must be enabled to send the HTTP(S) requests to the Unwired Server.Flow: Regular DCN with RBSThe flow of regular DCN messages between the client and the RBS involves several stages. Initially, the EIS data associated with an MBO is updated. Next, the EIS pushes a DCN message that contains new or changed MBO data through configured HTTP(S) port. The DCN service receives the message and then executes the upsert function by updating or inserting into the CDB partitions for that corresponding MBOs. The DCN upsert operation also sets the changed flag of an MBO package to true. After the modification, the Unwired Server sends a response message back to the EIS that contains the status of each DCN in the submitted message. After the message is responded back to the EIS, the Unwired Server generates a message for the client indicating that it should synchronize. The message is then pushed from the Unwired Server to the device. Now, the client receives the message and issues a synchronization request to the Unwired Server. The Unwired Server, in turn, retrieves the new or updated data based on the client synchronization parameter and returns it to the client. Flow: DCN with PayloadThe flow of message with the DCN payload involves different stages.1. Initially, some events initiate the DCN request. For example, a database trigger could initiate the DCN. T2. The Unwired Server cache or CDB could be updated directly from the EIS, or the DCN request could originate from a source other than the EIS. The actual data or payload is applied to the cache through either an :upsert or a :delete operation. 3. Finally, the Unwired Server returns a DCN status message to the requester.Flow: DCN Without PayloadThis slide depicts the flow of message in DCN without payload.The message flow in the DCN without payload involves different stages.1. Initially, the DCN requester sends an MBO operation execution request, along with operation parameters, to Unwired Server. 2. Then, the Unwired Server executes the operation or the MBO operation. It also updates the consolidated database, depending on the operation's cache update policy. 3. Finally, the Unwired Server returns a DCN status message to the requester.DCN CommunicatonThe DCN communication is an HTTP(S) call to the DCN port for activating a specific servlet to notify the Unwired Server. The default DCN port is 8000. The call can either be a GET or POST. The response received from the Unwired Server to the EIS can either be ignored or processed. Before processing the DCN, the HTTP request can be altered to utilize the existing event notifications.To alter and filter the DCN, you can use the DCN Filter Java classes.DCN Loggin, Sizing and MonitoringThe DCN Log

The DCN log captures data for data change notifications between an enterprise information system (EIS) and an MBO package. There are two types of DCN log, namely, General DCN and Workflow DCN. The general log captures information such as time, user, package, MBO, and error. Similarly, the workflow log captures information such as time, user, package, operation, subject, from, to, body, and error.Enabling/Disabling DCN LoggingYou can configure HTTP logging to record request event information logged by DCNs. By default, the HTTP logging for DCNs is enabled, and it prints the output to /Servers/ UnwiredServer/logs/ http.log file. To disable the HTTP DCN logging, you need to follow certain steps. First, open /Servers/UnwiredServer/ Repository/Instance/com/sybase/djc/server/ApplicationServer/${yourserver}.properties file. Then, delete the enableHttpRequestLog line and save the file. After saving the file, you have to restart the Unwired Server to reflect the changes made.This slide displays the locations of the -http.log file and the {yourserver}.properties file.Changing Post SizingThe default size of an HTTP request is 10 MB. However, to handle larger data change notifications, you have to stop all the Sybase Unwired Platform services. Next, open the jetty-web.xml file and locate the Set property. Increase the value to 100MB and then save the file. Finally, restart the Sybase Unwired Platform services.DCN History StatisticsDCN history statistics provides historical information for monitored packages. The detailed data provides specific information on past notification activity for packages. The history statistics displays information in several categories, such as Domain to which the package affected by the DCN belongs Package displays the name of the package that contains data changes MBO is the name of the MBO to which the notification applies Notification Time is the date and time when the Unwired Server received the DCN Processing Time is the time that Unwired Server used to process the DCN. DCN Performance Monitoring StatisticsThe DCN performance monitoring highlights key totals and identifies average, minimum, and maximum values for primary activities. The calculations are dynamic and are based on the data currently available in monitoring database for the specified time period. The table lists the key performance indicators and their description. Monitoring Device HistoryDevice Notifications can be captured and monitored using various methods:

Device Notification Statistics which provide data about the occurrence and frequency of notifications sent from Unwired Server. Device Notification History Statistics which provide specific information on past device notifications, indicating which packages, synchronization groups, and devices were involved in synchronization request server to replication synchronization devices. Device Notification Performance Statistics which provide a general indication of the efficiency of notification processing and the total demand of synchronization requests on the system. Implementing Regular Data Change NotificationJSON Digression JavaScript Object Notation (JSON) is a lightweight, text-based open standard designed for human-readable data interchange. JSON is used to serialize and transmit structured data over a network connection. JSON Strings can be automatically parsed or marshalled by the eval() JavaScript function into an object. JSON schemas can be used to verify a JSON String. The JSON Parsers are available for many languages. DCN URI TemplateThe template of a Request URI for issuing a DCN is displayed. You will also notice the different parameters used in the template.The cmd [dcn|wf] parameter represents the regular DCN or workflow DCN. In the username, enter the name of the user with DCN role assigned. In the password, enter the password. The domain parameter refers to the name of the SUP Domain that will be notified. In the package parameter, you need to provide the details of the package name including version string in format package_name:version_info. The dcn_request is the JSON string containing the operation name and parameters. The dcn_filter parameter is optional. It refers to the custom filter class name used to pre-process the DCN request and post-process the DCN status message. Similarly, the ppm parameter is also optional. It is a Base64-encoded map of personalization parameters.POST or GET?There are two HTTP methods which are allowed namely, POST and GET. All request parameters in DCN are present either in the URI or in the POST body. However, usage of POST is always recommended. If you are using HTTP BASIC authentication, the JSON encoded DCN request is always sent as the HTTP POST body. The syntax of the HTTP BASIC authentication is http://:8000/dcn/HttpAuthDCNServletdcn_requestThe dcn_request parameter contains a two part JSON string, namely the package name and message array. The package name in the dcn_request is required for backwards compatibility. This is generally ignored, and instead, the package name in the request URI is used. dcn_request MessagesEach dcn_request message includes a set of parameters: ##Message id (id) is the identification that is used to track the DCNs sent to the Server. This value will be returned in the DCN response. ##Mobile Business Object (mbo) is the name of the MBO that should be updated. ##Operation name or (op) is the operation that this DCN should invoke. ##Bindings (cols) is the name value pairs representing the attributes and values of an MBO. :upsert and :delete OperationsThe two important operations of DCN are :upsert and :delete. The :upsert operation is used to inject data into the Unwired Server cache or CDB for a specified MBO. This operation performs in place update or insert to the Unwired Server cache. The :delete operation is a specially built-in DCN operation and is not the MBOs delete operation. This operation is used to delete data from the Unwired Server cache for a specified MBO. It performs in place delete to the Unwired Server cache.

:upsert

The :upsert operation requires to pass the entire key attribute(s) of the MBO in order to locate the correct row. You can also use other MBO attributes in the :upsert operation. In the :upsert operation, all columns should use the MBOs attribute names, and not the data source column or parameter names.:deleteThe built-in :delete operation requires to pass the entire key attribute(s) of the MBO in order to locate the correct row. While using the :delete operation, you have to ensure that all columns should use attribute names instead of column names. User-defined OperationsThe User-defined MBO operation requires the name of the user-defined operation. For example, in the Customer MBO, createCustomer uses the CREATE operation. It also requires all parameters used in the MBO operation. While using the User-defined MBO operation, all columns should use the MBO parameter name. The User-defined operations support any type of operations such as CREATE, UPDATE, DELETE, and OTHER.Multiple Messages in a Single DCNA single DCN may contain multiple messages, and each message will contain a specific operation. For each message in the array, you get a result description in the DCN response. To distinguish between message results, you must use the message id.DCN ResponseUnwired Server returns a JSON string which contains a status message for each message sent. You have to use a custom DCN filter to alter the response representation. The DCN response has three parts such as recordID which is the messageID sent; success which is displayed either as true or false; statusMessage which is a string describing the result. You have to display this string as empty, if success is true. Implementing Workflow Data Change NotificationDCN for Workflows (WF-DCN) OverviewWF-DCN is very similar to Regular DCN. It sends notifications to devices to keep the mobile workflow and the EIS in sync when a change in the EIS occurs. You can start server-initiated workflows with a WF-DCN. You must decide whether you will notify server-initiated device users through the Notification Mailbox feature in the Sybase Control Center or the WF-DCN as you cannot implement both for the same device user. The two modifications for WF-DCN are that the cmd URI parameter is now known as wf instead of dcn, and the message format has some new parameters. New WF-DCN ParametersNew parameters are added to the message so as to be compliant with the Workflow Email Notification mechanism. The Username or to parameter refers to the SUP user name and not the username used to register the device. The subject parameter refers to the workflow message. The Originator or from parameter is the one from whom the workflow message originates. The Body of the workflow message or body parameter can embed customized information. The received is a parameter which indicates the received time of the Mobile Workflow message. The read parameter indicates whether the Mobile Workflow message is read. The priority parameter denotes whether the Mobile Workflow message has a high priority, and The list of dcn request or data parameter has the JSON format string as previously seen in dcn_request. WF-DCN Without Payload 1The cache group policy of MBOs used in the WF-DCN without payload must be online. The online MBO contains the findByParameter object query with the same parameters defined in the load operation. The query is triggered by the workflow server-initiated starting point after extracting the parameter values from the WF-DCN message body.WF-DCN With Payload 1When the EIS has new or modified data to push to Unwired Server, it initiates an HTTP request to the WF-DCN URL. The WF-DCN message contains the new or changed data object. When the WF-DCN message reaches Unwired Server, the workflow engine evaluates the matching rule against all registered workflows. If a matching rule matches this message, the workflow server starting point for that workflow is triggered to process the message. The data object included in the WF-DCN message is applied to the MBO CDB table by inserting new records or updating existing records. The workflow server-initiated starting point extracts parameter values from the message body and triggers the MBO object query to retrieve the newly inserted or updated record. The workflow engine converts the MBO data and WF-DCN message into a workflow email, then pushes it to the device mobile inbox via the MOCA protocol.WF-DCN With Payload 2According to the MBO cache group policy, the cache group policy of MBOs used in WF-DCN with payload must be DCN. An example of message format is shown in the slide.Email Data and WF-DCN With PayloadThe message must contain e-mail information such as Subject, To, and From. Message must include Package name, MBO name, Attribute name, and Attribute value. The message can include multiple MBOs.Processing MessagesAfter Unwired Server receives the message, a matching workflow server-initiated starting point parses the message, extracts data fields from the message, and sets the extracted data into the parameter of an object query operation. Since the MBO uses an online cache policy, the object query is mapped to a load operation. The data is then passed into the load operation as a load parameter to trigger MBO data refresh. WF-DCN ResponseA WF-DCN Response is also a JSON string, but it differs from a Regular DCN Response. WF-DCN responses include two parts which are the result of processing the Mobile Workflow request and the result of processing the general DCN requests.PUSH- Push OverviewPush Overview

Push is a mechanism to notify mobile clients of changes made to the cache or CDB. Unwired Server determines when individual clients need to be notified of data changes. Current Unwired Server push notification options for BlackBerry is through the HTTP configured by Sybase Control Center; for Windows Mobile and Windows, it is through the Light Weight Polling (LWP); and for iOS, it is through the Apple Push Notification Service (APNS).Pushable Applications Mobile applications are modified to register for Push Notifications on the Unwired Server; to implement a Push Listener, which is a separate application for Windows; and to use built-in APIs for BlackBerry. These modifications implement logic to react to Push notifications. MBS synchronized applications are inherently pushable.

MODULE VISecurity Administration - RESUMENIntrusion Detection/Prevention SoftwareWhen using an Intrusion Detection or Prevention software, you should be aware that these type of programs can cause problems in Sybase Unwired Platform. The Personal Firewalls or Intrusion Detection or Prevention software such as McAfee Host Intrusion Prevention can cause platform components to malfunction or not function at all. Unwired Server uses IP communications with all components through the primary network interface. Therefore, any malfunction or dysfunction of the components creates a security threat.Platform Administration SecurityFor secure platform administration, you need to enable authentication and Role Based Access Control (RBAC) for Administrator logins; change default certificates used for the Unwired Server and the SCCs HTTPS listeners; enable and configure encryption; secure multiple domains.Enabling Authentication and RBACTo enable authentication and RBAC, you need to perform these steps: First, log into the Sybase Control Center with the installation-defined user name and password. In the Security node of the navigation pane, click admin to make changes to the admin security configuration and replace the PreconfiguredUserLogin security provider. Next, disable Authentication Caching and increase Log Levels. Validate or test the changes made to the admin security configuration. Finally, enable Authentication Caching and decrease Log Levels.Definition of Installation Admin PasswordDuring Unwired Platform installation, a password is defined for the supAdmin super-user account. For example, you can set the password as s3pAdmin.Sidebar: Choice of Authentication Provider 2The Login Modules shipped with Sybase Unwired Platform include: LDAP, which stores the users and groups in an LDAP server CertificateValidation, which performs authentication services only NTProxy, which allows the operating system's security mechanisms, such as Active Directory, to validate user credentials HttpAuthentication, which authenticates the user name and password through HTTP or HTTPS calls to an EIS, using a GET against a URL that requires BASIC authentication. This can be configured to retrieve a cookie with the configured name and add it to the JAAS subject to facilitate a single sign-on. Sidebar: Choice of Authentication Provider 3

Additional Login Modules shipped with Sybase Unwired Platform include: SAPSSOToken - Deprecated. You can instead use HttpAuthentication when SAP SSO2 token authentication is required. PreConfiguredUser authenticates the Unwired Platform Administrator user whose credentials are specified during installation and is not for production use. CertificateAuthentication is used to implement SSO with an SAP enterprise information system (EIS) with X.509 certificates. Unwired Server does not perform any authorization. It defers authorization to an SAP system. Increasing Log Levels for TestingBy default, the security log level setting is INFO. For testing purpose, change the log level to DEBUG.Predefined Platform Logical Roles 1Unwired Platform contains two predefined platform logical roles, namely SUP DCN User and SUP Administrator. The SUP DCN User role is used by the Unwired Server to authorize any DCN event such as updating data in the cache, executing an operation, and triggering a workflow package. The SUP Administrator role is assigned to administrators, also referred to as platform administrator. The platform administrator is a superuser of the Sybase Control Center who can perform all administrative operations.Role Mapping 1Logical roles have to be mapped to the Physical roles. To do this, select the admin configuration within a domain. This is a domain-specific configuration for the security configuration.csi.properties and roles-map.xmlChanges implemented for the admin security configuration must be repeated for the Sybase Control Center by editing the file called csi.properties.Enable Caching and Decrease Log LevelsAfter testing the changes made in the admin security configuration, you need to reverse these changes: ##Return the Authentication cache timeout values edited earlier, to their original value. The default value is 3600 seconds. ##Return the Server log settings for the security component from Debug to Warn. At this stage, you control who can log into and administer the platform.More About Security ConfigurationsMultiple security configurations can be created by the platform administrator. The admin security profile is the default profile provided with Unwired Platform. Other security configurations can also be added. Security configurations include additional properties such as Settings and Audit tabs. Security configurations are assigned to packages as part of the deployment or post-deployment configuration. These security configurations determine how the platform authenticates and authorizes application users.Security Configuration Settings PropertiesThese are the key properties of a Security Configuration:

Authentication cache timeout defines how long authentication results should be cached before a user is required to re-authenticate. Maximum allowed authentication failure refers to the maximum number of invalid login attempts after which the user is locked. Authentication lock duration defines the time duration for which the user is locked, after the maximum number of login attempts is reached. Security Configuration Audit PropertiesSecurity Configuration Audit properties are used to report all audit events to evaluate the security system implementation for Unwired Platform. Each successful authentication creates a session key that shows up in the subsequent security checks for that user, which enables traceability. However, unsuccessful authentications are also logged. Each authorization records the roles checked, or the resource accessed.Defining New Audit ProviderThe Audit Provider can set these audit parameters: Filters define which events are to be recorded; Format defines the audit record format, which is currently only XML; Audit File defines where the audit records are sent.Audit Log LocationBy default, the name of the log is default-audit.log.Management PortsUnwired Server has two management ports: 2000 is the unsecured port and 2001 is the secured port.Default Security Profiles 1During installation, two security profiles are created, namely domestic and domestic_mutual. If you choose the domestic profile for communication, then Unwired Server sends its certificate to the client Sybase Control Center or DCN. The client will be configured to trust the Unwired Servers certificate. Therefore, Unwired Server does not require a client certificate in return. Alternatively, if you choose the domestic_mutual profile for communication, it is a two-way stream. Both client and server exchange their certificates.Default CertificatesDuring installation, the installer generates default or dummy certificates with alias names sample1 and sample2. HTTP listeners use these default certificates. As per the security policy, you cannot use the default certificates. Therefore, after installing the platform, administrators must replace the default certificates with production-ready or real certificates. Instead of replacing the certificates associated with the sample1 or sample2 alias, you can create new security profiles. A security profile points to a certificate alias. The default profile points to sample1 alias. The default_mutual profile points to sample2 alias.Replace Default CertificatesYou can create and use the new server certificates under the alias of sample1 and sample2. If you want to implement mutual authentication, you should use the sample2 certificate. There are two different ways of creating certificates. One method is using the PKI systemThe other method of creating certificates is by using the platforms keytool utility. This utility generates self-signed certificates.TerminologyKeystore is the location where encryption keys, digital certificates, and other credentials are stored for Unwired Server runtime components. Truststore is the location where trusted certificates such as Certificate Authority (CA) certificates are stored. Truststore is used when Unwired Platform makes an outbound connection over SSL to another server with a server certificate. Unwired Server checks that the server certificate is in the truststore or is signed by a CA certificate in the truststoreSCCs Keystore / Truststore Locations\Sybase\SCC-3-2\plugins\com.sybase.supadminplug_2.1.0\securitySecuring Multiple DomainsFor securing multiple domains, Sybase recommends that the Platform Administrator create at least one new tenant domain in the Sybase Control Center; restrict the use of the "admin" security configuration on the "default" domain to administration authentication only; assign at least one domain administrator; create and assign at least one new security configuration.Unwired Server - MBS Devices/AppsWhen you install MBS applications (including Mobile Workflow applications), an RSA keypair is created during the platforms installation. When a device first connects to Unwired Server, it retrieves the public key and the server uses it to secure all future communications. In an MBS application, you have to register the device users. Registration adds the user name and authorization code to a whitelist. When the device connects, it passes th