Download ibm lotus notes traveler for blackberry

IBM Lotus Notes Traveler supports the transfer of existing administration and synchronization data from the standalone Derby database to the enterprise database. In an HA pool, trace settings are shared. Activating tracing on one server affects all servers. There are many installation and configuration considerations you should review before installing the IBM Notes Traveler server. These mail files are either located on the same server as the IBM Notes Traveler server or they are hosted on remote Domino servers.

If the mobile users are not present in the local Domino directory names. IBM Notes Traveler servers can be deployed as standalone servers, or if a highly available environment is required, as part of a pool of servers. This component is installed by default when you install your IBM Domino server. For information about the types of server and network topologies to consider and details about local and remote mail files, see these topics:.

Considerations should be given to capacity and availability needs of the IBM Traveler servers, location of mail servers, domain of mail servers and directory server compatibility. An internal database is used to store synchronization state data. All of this data is known only to this instance of the server. This configuration is referred to as a stand alone server. It is possible to deploy multiple stand alone servers, however, each server operates independently and does not share information.

What this means in practical terms is that if a user syncs with one stand alone server and then switches to another, the device is treated like a new device and must re-synchronize with the server. In a multi-server standalone environment, the users are load balanced administratively, assigning different URLs to different groups of users. This configuration is referred to as a High Availability HA pool.

In this configuration, all of the sync history and administration information for a device is stored in the enterprise database. The advantage of deploying an HA pool configuration is the ability to balance the load of requests among the pool of servers, seamlessly add capacity, as well as start and stop servers for maintenance without impacting the availability for serving synchronization requests. A user's mail is monitored for changes only on one server in the HA pool. For maximum efficiency, all devices for a user are routed to the IBM Notes Traveler server that is monitoring the mail for that user.

In the event that a server becomes overloaded or unavailable, another server in the pool will takeover the responsibility for monitoring a user's mail and device requests will be rerouted. There are configuration architecture requirements with an HA pool. This typically can be provided by some form of an IP Sprayer.

This allows all devices to be configured for the same address without regard to a specific server that may process the request. The sprayer detects when a IBM Notes Traveler server becomes unavailable and then routes requests to other servers. No additional load balancing functions are required, as the IBM Notes Traveler servers handle the load balancing amongst the servers in the pool.

Servers in an HA pool should be co-located to avoid network latency issues that could affect server to server communication, server to database communication, as well as server to mail server communication. Each component of the configuration should have a redundant counter part to avoid single points of failures.

Likewise, multiple components should not be deployed on the same physical server for example, IBM Notes Traveler server and the database server. Which configuration to choose depends upon availability requirements, infrastructure costs, and geographic requirements. If continuous availability is required, then an HA pool is the best configuration. For smaller deployments, stand alone servers may still be sufficient. In that kind of environment, stand alone servers or multiple HA pools will be needed. Stand alone servers can be added to an HA pool such that a configuration can grow from a stand alone server configuration into a highly available configuration.

For more information on failover and clustering, see Clustering and failover. Where to place your IBM Notes Traveler server in your network depends on the types of devices used and sync types. This section includes a list of possible scenarios and why one might be selected over another. This channel is always initiated from the mobile device. The optional SMS channel is used to notify the mobile device of pending server changes. The IBM Traveler client then carries out the command or begins a data sync. These devices do not support the SMS push channel. The following table provides a summary of the connection types used by the mobile devices and the ports they use by default.

This connection type is best for data syncing. The port uses a secure channel for data transfer between the device and the server. The port uses an unsecured channel for data transfer between the device and the server. These topics describe different network topologies and give more specific information about why each might be used:. During initialization, the IBM Notes Traveler server automatically scans the available network interfaces and uses the first active, non-loopback option.

In most cases, this automatic selection will be adequate. If the server has multiple network interfaces, however, the wrong interface may be selected during initialization. If this happens, the notes. See Notes. The diagrams in this topic shows a network topology where a reverse proxy resides in your DMZ and provides authentication services for the mobile device clients. In this case, the function of spraying or load balancing the device requests is provided by a separate server in the trusted domain.

The third diagram shows the network topology with the authentication proxy also providing the ability to spray the mobile requests to the HA pool of IBM Notes Traveler servers. IBM Mobile Connect can provide the authentication proxy and request spraying capability. This network topology does not allow as much flexibility as the VPN topology. However, it still provides a secure network implementation that does not expose any of the IBM Domino server infrastructure to the Internet or DMZ zones. IBM Notes Traveler has been tested with several reverse proxy products, but most products providing a standard reverse proxy function should be adequate.

These are some items to consider when selecting a reverse proxy:. The diagram in this topic shows a network topology that uses a Virtual Private Network VPN server as the secure access point to the company intranet from mobile devices. The first diagram in this topic shows a network topology that uses a Virtual Private Network VPN server as the secure access point to the a standalone IBM Notes Traveler server on the company intranet from mobile devices.

This solution allows for the most flexibility in terms of what applications can be connected by mobile devices and what protocols they are allowed to use. When you use a secure VPN tunnel between the mobile device and the company intranet, any applications that are running on the device can connect to any company server just as if it were running inside the company network.

For example, you can use the device browser to open pages on an internal website or use instant messaging on the device that connects to internal messaging servers. The VPN typically provides a secure data channel. The type of VPN server that must be installed depends on the mobile device. This connection may disconnect after it is started and will not restart automatically.

In addition, pushed messages may not flow over an Apple VPN connection. As a result, it is suggested you not use a VPN solution if you intend to push messages. Use either the virtual private network or the reverse proxy solution to ensure the best overall security. When using this configuration, take steps to ensure that the IBM Domino server has been secured and does not contain unnecessary data. For example, it is not recommended to host user mail files on the IBM Domino server in this configuration. Consider installing this IBM Domino server in a Domino domain different from your production mail domain.

This configuration has the advantage that no personal records for users are present in the local names. The first diagram shows a direct connection to a stand alone IBM Notes Traveler server within this topology. The port will depend upon the database server used and the configuration for example, port for the JDBC connection to a DB2 Server instance. While it is technically possible to connect the device to the server using HTTP port 80 , do not use this configuration. This command shows connection routing information that shows you if there are any problems with the route between the IBM Notes Traveler server and the specified remote server.

While it is possible to run the IBM Notes Traveler service on the same Domino server that is hosting mail files, it is best to do this only for smaller installations. The Domino remote mail server can be any operating system supported by Domino. This should be done only after the design of the IBM Domino directory has been upgraded. If your network administration does not allow the master IBM Domino directory to be upgraded, then install the IBM Notes Traveler server into a separate, stand-alone domain. However, this requires additional setup, including configuring IBM Domino directory assistance so that the IBM Notes Traveler server can locate the home mail servers of mobile users.

However, there are a number of reasons why you may want to separate your IBM Traveler server domain and your production mail server domains. There are several items you must consider to make this possible. However, when installing in the same Domino domain, many of these items typically work without any additional configuration. This will force all lookups to run against the local directory, which will then use Domino Directory assistance if it is configured and needed to resolve a name.

For Domino setup considerations and information on installing in a High Availability HA environment, please refer to this article. The administrator who installs and sets up IBM Notes Traveler must sign on to the system with a user profile that has the required authorities. The key to any production environment is the enablement of redundancy to account for planned or unplanned outages. When creating a redundant environment, it's important to understand the terminology and options. This is typically utilized with the IBM Domino mail databases. IBM Notes Traveler servers can take advantage of mail database clustering.

High Availability HA is a general term that implies a high percentage of system availability ensured by a redundant infrastructure. If a server in the pool goes offline, devices can connect to other servers in the pool without loss of data. This pool of IBM Notes Traveler servers in conjunction with mail clustering provides highly available mobile mail access. Although clustering and high availability can be considered synonymous, the term High Availability is used with IBM Notes Traveler to avoid confusing the implementation with that of Domino clustering. Disaster recovery DR typically refers to enabling a backup environment that will only be utilized in the event of a failure of the primary service.

A disaster recovery environment may or may not require manual intervention. IBM Notes Traveler, even as a stand alone server, can be setup for disaster recovery. Which degree of redundancy is implemented will depend on both your availability requirements as well as the infrastructure investment desired. IBM Notes Traveler servers can be configured to use a shared enterprise database. The advantage of this type of configuration is the ability to balance the load of requests amongst the pool of servers, seamless add capacity, as well as eliminate the IBM Notes Traveler server as a single point of failure.

Mail servers should be clustered. In the event that a user's mail database becomes unavailable due to a server failure, IBM Notes Traveler will switch to an alternate mail server in the cluster. For more information, see Domino mail clustering. The enterprise database server can be mirrored so that in the event of a database server failure, the servers in the HA pool can reconnect to the secondary database server. The data mirroring allows IBM Notes Traveler devices to generally continue synchronizing without requiring a full recovery sync.


  • bookworm adventures 2 for samsung galaxy y.
  • Install Lotus Traveler for Windows Mobile device synchronization.
  • ios 7 vimeo upload status?
  • vip black app free download?
  • Continue Reading This Article.
  • .
  • !

Most enterprise database servers provide different configuration options with regards to how a database change made on the primary server is also made on the secondary database server. The higher the degree of synchronization, the more impact to the overall response time of a device request. The lower degree of synchronization, the higher the chance that in the event of a failover scenario, some database changes are lost. This can result in a device recovery synchronization for some devices.

A redundant server should be employed to avoid the IP Sprayer from becoming the single point of failure. This section contains a high level check list of the process to deploy a High Availability pool. The specifics on each of these steps is contained in the Installing and Configuring sections. Condensing the number of servers for example, running the database server with a IBM Notes Traveler server can create single points of failure, as well as create performance bottlenecks.

Setting up a IBM Notes Traveler High Availability pool consists of some initial infrastructure setup as well as steps for each individual server. This step is not required on each server if you enable common configuration for all IBM Notes Traveler servers in the pool. The following are best practices to consider when planning for a highly available IBM Traveler Server environment.

IBM Notes Traveler servers in an HA pool communicate server to server for both processing commands, as well as routing requests for load balancing. If failover is configured for the database servers, the database servers should be located within the same network, preferably on the same switch. Transactional response time will be severely impacted if the commits to the secondary database server encounters slow network response time. This will affect the capacity of the overall HA pool. This will reduce the impact of a server failure as well as improve performance.

Size the servers in the HA pool such that there is spare capacity to handle failover. For example, assume a server capacity of devices and a total population of devices. A two server pool will not be adequate, as one server cannot handle devices in the event the other server is taken offline. Therefore, to adequately handle the device load in the event of one server going offline, three servers are required. IBM Notes Traveler servers in a Highly Available HA environment will perform their own load balancing to ensure best possible performance and consistent user experience.

This should not be confused with a network load balancer.

Setting up IBM Traveler on your BlackBerry 10 device - Traveler

HTTP server participation is limited in the sync process and typically only hands off the request to the IBM Notes Traveler server, therefore the network load balancer can use a simple round robin approach. See Deployment checklist for HA for more information on the requirements for a network load balancer. Once the request is passed off to the IBM Notes Traveler server, it will be load balanced for processing. To understand how this is done, it is important to understand the IBM Notes Traveler load balancing terminology.

The master monitor is essentially the IBM Notes Traveler server responsible for handling any and all work for that user. If the user connects multiple devices, each device will be routed to the master monitor for processing. If no device connects, the master monitor assignment will expire after 24 hours. On each device connection, the IBM Notes Traveler server will decide if the master monitor should be moved, or if no master monitor is currently assigned, which server to assign the user.

The algorithm used to assign master monitors is described below. A bias or weighting is used to improve performance when deciding which server should be the master monitor for a particular user. The two types of bias are local server and current master monitor. Local server is simply the current local server for example, the server to which the network load balancer routed the connection.

The current master monitor bias is for the server that is currently assigned as the master monitor for this user. If no master monitor is assigned then no server will get this bias. For each request from the device, the local server will determine what is the best server to handle the request. The best server is determined by comparing the AIs of each server.

If any bias applies to a server, it is added to the AI. The server with the highest computed AI is chosen. If this server is not currently the master monitor, then it gets assigned as the master monitor for the user and the master monitor bias will apply. To prevent thrashing, a user's master monitor can not be switched again for at least 10 minutes.

These notes. It is recommended to only change these values in small increments and monitor the systems for performance changes.

In general, the default values should be sufficient. There are several methodologies to employ with IBM Notes Traveler to recover from a server crash or failure. In the event of a failure, device requests and mail monitoring is shifted to the remaining servers in the pool. For more information, refer to High Availability HA. Alternatively, it is also possible to set up multiple standalone IBM Notes Traveler servers as potential disaster recovery servers for each other.

Each server could have the same access to all the mail files for a user on remote servers. Alternatively this failover could be automated using a front end proxy for example, IBM Mobile Connect. After a device switches to a new server, the sync anchors no longer match between the server and device. The protocol initiates a sync refresh, where all of the data on the device is replaced by a fresh copy of the data from your mail database. If a device switches to another server, then this history is lost due to the fact that these tracking databases are not on the network or shared between IBM Notes Traveler servers.

Likewise, switching back to the original server can also result in a sync refresh. This kind of configuration is useful in a disaster recovery scenario where High Availability is not required. Otherwise, the IBM Notes Traveler server never fails over the connection to an alternate server for mobile users if their primary Domino mail server is down. This section provides information about each IBM Notes Traveler security option and how they can be applied by device type.

You can use this information to plan your security configuration for IBM Notes Traveler on your devices. Device wipe; or when issued to a device managed by BES 10, it wipes only the work perimeter. Whole devices can be encrypted, and enabled and enforced with the security policies in IBM Notes Traveler. First-generation iPhone and iPhone 3G do not. The mail body and all attachments are encrypted using AES bit encryption. This is the case if stored on an SD card or internal phone storage. The rest of the data is stored unencrypted in phone storage. This is implemented based on the Android application security model.

For complete details on Blackberry 10 device security capabilities for both work data and personal data, please refer to BlackBerry Balance technology and Blackberry product documentation. Storage cards can be encrypted. Data in native PIM and e-mail applications is not encrypted, except for Domino encrypted mail. Requires an Android 2. For additional information on defining security polices, refer to Assigning preferences and security settings to devices. For additional information on remotely wiping a device, refer to Remote wipe.

The installation and start up process will handle the migration of configuration information and the upgrading of existing internal databases. See Upgrade considerations for more information. If you are upgrading servers in an HA environment, it is recommended that you upgrade one server at a time. For more information, refer to Upgrade considerations for a Highly Available environment.

As of release 8. As a result, parameter names have been changed. The installation process will migrate supported configuration settings to notes. There are some configuration settings, such as trace settings, that are not migrated. See Configuring IBM Notes Traveler server for more information on the updated configuration settings for this release. For standalone servers, the upgrade process does not require an enterprise database. Upon startup, the server automatically upgrades the existing internal database, retaining any existing data.

Note that the service is unavailable during this upgrade process. In this case, depending on the number of users and the quality of your hardware, a multi-hour maintenance window may be required to perform this upgrade. Note that the upgrade process automatically runs the defragmentation process when upgrading releases. After the upgrade, a server can then be configured as part of an HA pool, if desired. The following information outlines the best practices for moving from one system to another. Change the physical hostname and IP address of the new server to be the value of the old server.

If you choose this option, you should also change the hostname, IP Address and External URL parameters in the Domino server document and any Internet Site documents to match the physical server changes. A Domino server restart is recommended after making these changes. All synchronization and administration data is automatically transferred to the HA pool database.

This process is useful for consolidating an existing set of servers into a single HA pool, as well as moving off servers or transitioning to a different OS. For example, Windows bit servers are not supported in a High Availability pool. The server data is automatically transferred to the HA pool database and then the Windows bit server can be removed from the configuration. There are two strategies for integrating existing servers into an HA pool. One strategy is to build up the HA pool only from existing servers. The advantage of this strategy is that no additional servers are required for the IBM Notes Traveler servers.

The disadvantage is that you cannot validate the configuration until at least one of the servers has been reconfigured for HA.

Install Lotus Traveler for Windows Mobile device synchronization

The second strategy is to set up a new HA pool and then integrate the existing servers into the pool. The advantage of this strategy is that the initial HA configuration can be validated without impacting the existing users. Then the integration of the existing servers can be staged. At the end of the integration, excess servers can be removed from the configuration. The disadvantage of this strategy is the requirement for additional hardware, at least until the integration is complete.

Note that once the new environment is set up and validated, new users can be provisioned for the HA pool. During the upgrade process, existing data and configuration is migrated as necessary. Depending upon the size of the database this process can take a while.

Note that during this upgrade process, the server will not be available for device requests. If the HA pools is configured for secure server to server communication, enable this on the existing servers that will join the HA pool. Upon startup, the server will detect that it is now configured for an HA environment and will start transferring all of the user and administration data to the HA pool database.

The server will not be available for requests until the data transfer is complete. Once the transfer is complete, the server is registered as part of the HA pool. This can be validated from the web administration interface or from any server in the pool. At any point in this process after the data has been transferred, a server can be removed from the HA pool. There are a number of different factors you should consider when planning the type of computer system that will host the IBM Notes Traveler application server.

Initially, it may work fine for a small number of mobile devices, but it will likely experience degraded service later as additional devices are registered with the server. Note that this article provides general guidance only, and if you are looking for more specific information and hardware specifications, consider contacting your IBM Sales Representative and asking them to connect you with a system sizing available through IBM Techline.

The information presented first in this section was derived from testing with IBM Notes Traveler in a stand alone configuration. Much of the information here is applicable to both environments. However, there are significant differences. IBM Notes Traveler and the underlying Domino subsystems require substantial amounts of system memory. The IBM Traveler server must allocate resources to handle device requests as they connect to the server, but also must use resources even when devices are not actively syncing, so that push mail services are possible.

The IBM Notes Traveler server uses additional memory to cache certain data elements to reduce the number of queries made to the back-end Domino mail servers. Furthermore, the Domino HTTP engine requires that a thread is allocated at startup for each potential connection. These threads use a considerable amount of memory and it is recommended that you define the maximum number of HTTP active threads to be equal to 1. Therefore, it is important to select an operating system and Domino server application type that can support the maximum number of mobile devices that are expected to use the IBM Notes Traveler server.

Each of IBM Notes Traveler's supported operating systems are listed below with recommendations for each. This mode gives the applications access to the largest possible virtual memory address space. As a result, there is no worry about running out of application memory in this environment. This combination is capable of supporting the largest number of IBM Notes Traveler devices and is generally only limited by other factors.

Servers running in this environment are capable of supporting devices depending on the availability of other system resources. For more specific information and hardware specifications for this Operating System option, consider contacting your IBM Sales Representative and asking them to connect you with a system sizing available through IBM Techline. As of Domino version 8. This substantially increases the capacity to support additional devices.

This combination is recommended for environments of up to devices. IBM Notes Traveler is a multi-threaded application which makes use of multiple processor cores available in modern servers. Larger installations with more than devices should be running at least eight cores. IBM Notes Traveler makes extensive use of the processor as it converts data from Domino formats to those that are acceptable on mobile devices. It is recommended that a minimum of 8GB physical memory be installed with any system using a bit operating system.

If a bit operating system is being used for a smaller device population, 4 GB of physical memory should be installed. For servers supporting more than devices, 16 GB is recommended. If you are running a bit operating system, it is not recommended to increase the maximum amount of java memory beyond the default MB. Higher values could cause the system to run out of memory. If you require more memory, then you should move to a bit operating environment. For optimal performance for a stand alone server, the IBM Notes Traveler server disk system should be configured to increase the performance of read and write operations to the physical disks.

Using a RAID 0 disk configuration is suggested. IBM Notes Traveler primarily uses the disk system to read and write sync state information for devices that are registered with the server. These numbers were based on the workload used for benchmarking Lotus Notes Traveler 8. The IOPs in deployment may vary based on usage. The bandwidth and speed of the network connection between the IBM Notes Traveler server and the back-end Domino mail servers impacts the response time of synchronization with mobile devices.

It is recommended that back-end mail servers be co-located with the IBM Notes Traveler server or be accessible through a high bandwidth connection. Often this means providing IBM Notes Traveler servers in each geography around the world where you have also positioned clusters of mail servers. Having a large number of users on a slow mail server can impact the performance of other users on the server as threads spend most of their time waiting on high-latency requests with the mail servers.

While it is possible to run the IBM Notes Traveler server on the same physical server as other Domino services such as mail, iNotes, Sametime and BES , this is not recommended unless the deployment of users on the server is very small, typically less than users.

Once additional users are added, all of the applications will be vying for the same resources and the service will degrade.

Performance benchmark tests that combine load tests of IBM Notes Traveler with other application servers are not available, so only consider this route with a minimal numbers of users. However, in general, virtual instances are known to reduce overall capacity of the system when compared to a physical installation. It is important to understand that IBM Notes Traveler is a real-time critical application and any resources allocated to the IBM Traveler instances should be allocated statically.

If dynamic resources are used and other applications on the host are using resources when needed by IBM Notes Traveler, then the service will degrade. It is important to evaluate your IBM Notes Traveler server periodically to determine if you have provided adequate system resources for the number of devices that are using the server. In some cases, you may be able to tweak system configuration variables to improve performance or install additional physical resources to manage the load on a single server.

In other cases, you may need to install additional IBM Notes Traveler servers to handle the mobile device load. This article does not go into the details for how to use these tools, or other third party system management utilities that provide more comprehensive monitoring and reporting capabilities. On Windows, this is ntraveler. On Linux, this is traveler and http processes running from the Domino server directory.

The Domino server provides platform statistic monitoring that must first be enabled on the system. See Platform statistics for information on how to enable Domino server platform statistics. The command tell traveler mem will report both memory usage and CPU usage for the traveler process over the past 24 hours at 15 minute intervals. This report can be used to observe if your system is experiencing higher loads during different parts of the work day. This value is the maximum amount of memory that the Java heap is allowed to expand to. When running on a bit system, this value should not exceed MB.

A value higher than this does not leave enough memory available to other Domino systems. This is the amount of memory that the Java memory heap manager within the IBM Notes Traveler process is currently managing. This value can grow as high as the Max Available value. The number of megabytes that are free within the current heap allocation.

This value does not represent the total amount of memory that is available unless the Current Total has expanded to the Max Available value. However, the value listed as X percent of Max does represent the accurate percentage of total available memory. If it does, consider increasing the Max Available Java memory on the server document. Megabytes of native memory that have been allocated by IBM Notes Traveler and all shared memory allocated by other Domino processes running on the same server.

When running in a stand alone configuration, the primary demand of IBM Notes Traveler on the server disk subsystem is read and writes to its internal database which stores device sync state information. If the disk system cannot keep up with read and write requests, then the overall performance of the system can seriously degrade. Use the Domino platform statistics to review the Platform. This value represents the number of read or write requests that have been queued at the OS level.

A long queue means that the disk is not able to keep up with demand and is a bottleneck for the system. If the disk utilization Platform. AvgQueueLen is greater than the number of disk spindles on this partition, then there is a disk bottleneck. For Linux server, if the disk utilization Platform.

For example, if you have mobile devices, then your HTTP active threads value should be at least 1. The HTTP server task allocates all of these threads at startup time and keeps them active as long as the server is started. The statistic Http. Workers represents the maximum number of worker threads that are available to handle incoming HTTP requests. CurrentConnections is the number of worker threads that are currently performing work, and the statistic Http. PeakConnections is the maximum number of connections used since server startup.

IBM Traveler

Ensure that there are enough worker threads allocated to satisfy the Http. PeakConnections statistic. The capacity planning for the high availability configuration is therefore done for each pool of IBM Notes Traveler servers, together with its shared database management system resources comprising the HA solution configuration. The IBM Notes Traveler HA performance benchmark was executed with up to 10, user devices supported by a single service pool with the relational database systems also configured for high availability. These performance test results are used as the basis for the general capacity guidance in the following HA sections, and were based on the workload used for benchmarking the Lotus Notes Traveler 8.

The resources required in deployment may vary based on usage.

Installing Lotus Notes Traveler on Android device

When planning a high availability service pool the two primary considerations are the total number of unique devices that must be supported by the pool and how much redundant capacity is desired. The redundancy is a decision on how many servers you wish to allow to be out of service at the same time intentionally for planned reasons, or in case of unplanned system outages.

To achieve the goal of high availability, plan for the pool capacity to adequately support the total number of unique devices required when at least one server is off line. However there are practical performance limitations on the total real time transaction processing load to be handled on the relational database server. The server will not be available for requests until the data transfer is complete. Once the transfer is complete, the server is registered as part of the HA pool. This can be validated from the web administration interface or from any server in the pool. At any point in this process after the data has been transferred, a server can be removed from the HA pool.

When data is synced between the server and device, it is done so utilizing a protocol which controls what the message content the HTTP body contains. The protocols are used and supported only for the devices and their features that IBM Notes Traveler supports. There are a number of different factors you should consider when planning the type of computer system that will host the IBM Notes Traveler application server. Initially, it may work fine for a small number of mobile devices, but it will likely experience degraded service later as additional devices are registered with the server.

Note that this article provides general guidance only, and if you are looking for more specific information and hardware specifications, consider contacting your IBM Sales Representative and asking them to connect you with a system sizing available through IBM Techline. The information presented first in this section was derived from testing with IBM Notes Traveler in a stand alone configuration.

Much of the information here is applicable to both environments. However, there are significant differences. IBM Notes Traveler and the underlying Domino subsystems require substantial amounts of system memory. The IBM Traveler server must allocate resources to handle device requests as they connect to the server, but also must use resources even when devices are not actively syncing, so that push mail services are possible. The IBM Notes Traveler server uses additional memory to cache certain data elements to reduce the number of queries made to the back-end Domino mail servers.

Furthermore, the Domino HTTP engine requires that a thread is allocated at startup for each potential connection. These threads use a considerable amount of memory and it is recommended that you define the maximum number of HTTP active threads to be equal to 1. Therefore, it is important to select an operating system and Domino server application type that can support the maximum number of mobile devices that are expected to use the IBM Notes Traveler server.

This mode gives the applications access to the largest possible virtual memory address space. As a result, there is no worry about running out of application memory in this environment. This combination is capable of supporting the largest number of IBM Notes Traveler devices and is generally only limited by other factors. Servers running in this environment are capable of supporting devices depending on the availability of other system resources. For more specific information and hardware specifications for this Operating System option, consider contacting your IBM Sales Representative and asking them to connect you with a system sizing available through IBM Techline.

For more specific information and hardware specifications for this operating system option, consider contacting your IBM Sales Representative and asking them to connect you with a system sizing available through IBM Techline. IBM Notes Traveler is a multi-threaded application which makes use of multiple processor cores available in modern servers. Larger installations with more than devices should be running at least eight cores. IBM Notes Traveler makes extensive use of the processor as it converts data from Domino formats to those that are acceptable on mobile devices.

It is recommended that a minimum of 8GB physical memory be installed with any system using a bit operating system. If a bit operating system is being used for a smaller device population, 4 GB of physical memory should be installed. For servers supporting more than devices, 16 GB is recommended. If you are running a bit operating system, it is not recommended to increase the maximum amount of java memory beyond the default MB.

Higher values could cause the system to run out of memory. If you require more memory, then you should move to a bit operating environment. For optimal performance for a stand alone server, the IBM Notes Traveler server disk system should be configured to increase the performance of read and write operations to the physical disks. Using a RAID 0 disk configuration is suggested. IBM Notes Traveler primarily uses the disk system to read and write sync state information for devices that are registered with the server.

These numbers were based on the workload used for benchmarking Lotus Notes Traveler 8. The IOPs in deployment may vary based on usage. The bandwidth and speed of the network connection between the IBM Notes Traveler server and the back-end Domino mail servers impacts the response time of synchronization with mobile devices. It is recommended that back-end mail servers be co-located with the IBM Notes Traveler server or be accessible through a high bandwidth connection.

Often this means providing IBM Notes Traveler servers in each geography around the world where you have also positioned clusters of mail servers. Having a large number of users on a slow mail server can impact the performance of other users on the server as threads spend most of their time waiting on high-latency requests with the mail servers.

While it is possible to run the IBM Notes Traveler server on the same physical server as other Domino services such as mail, iNotes, Sametime and BES , this is not recommended unless the deployment of users on the server is very small, typically less than users. Once additional users are added, all of the applications will be vying for the same resources and the service will degrade.

Performance benchmark tests that combine load tests of IBM Notes Traveler with other application servers are not available, so only consider this route with a minimal numbers of users. However, in general, virtual instances are known to reduce overall capacity of the system when compared to a physical installation. It is important to understand that IBM Notes Traveler is a real-time critical application and any resources allocated to the IBM Traveler instances should be allocated statically. If dynamic resources are used and other applications on the host are using resources when needed by IBM Notes Traveler, then the service will degrade.

The information and screenshots provided below are available to help determine if the performance problem may exist due to virtual instance instead of at the Traveler level. A short spike in either Usage or Ready indicates that the system is making the best use of the host resources. However, if both values are constantly high, the hosts are probably overcommitted. For more information, refer to this documentation topic.

Usage information is given in a percentage format. The actual amount of memory used is also given. Under the Chart Options , change up the counters. Uncheck everything that was already selected, then check the boxes for Swap in rate and Balloon. Notice that the graph is now displaying in KBps instead of percentages on the left side. On the right it is displaying KB. If a virtual machine has high ballooning or swapping, check the amount of free physical memory on the host not the guest. This leads to memory reclamation, which also may degrade performance.

Engage your VMWare team if high ballooning or swapping is present. If so, most likely the host is running out of memory and taking it from the guest. For more information refer to this documentation topic. Check for peak times of high usage and for latency. In general, latency should be 15ms or under. This indicates that the disk is keeping up with requests. If the latency goes over 25ms, it can impact application performance and end users will be affected. Avg should be below 0.

For example, in the case above, 5. The issue can be solved by either allocating dedicated physical resources to the VM or by moving the IBM Notes Traveler server to a physical machine. It is important to evaluate your IBM Notes Traveler server periodically to determine if you have provided adequate system resources for the number of devices that are using the server. In some cases, you may be able to tweak system configuration variables to improve performance or install additional physical resources to manage the load on a single server.

In other cases, you may need to install additional IBM Notes Traveler servers to handle the mobile device load. This article does not go into the details for how to use these tools, or other third party system management utilities that provide more comprehensive monitoring and reporting capabilities. On Windows, this is ntraveler. On Linux, this is traveler and http processes running from the Domino server directory.

The Domino server provides platform statistic monitoring that must first be enabled on the system. See Platform statistics for information on how to enable Domino server platform statistics. The command tell traveler mem will report both memory usage and CPU usage for the traveler process over the past 24 hours at 15 minute intervals.

This report can be used to observe if your system is experiencing higher loads during different parts of the work day. This value is the maximum amount of memory that the Java heap is allowed to expand to. When running on a bit system, this value should not exceed MB. A value higher than this does not leave enough memory available to other Domino systems. This is the amount of memory that the Java memory heap manager within the IBM Notes Traveler process is currently managing. This value can grow as high as the Max Available value. The number of megabytes that are free within the current heap allocation.

This value does not represent the total amount of memory that is available unless the Current Total has expanded to the Max Available value. However, the value listed as X percent of Max does represent the accurate percentage of total available memory. If it does, consider increasing the Max Available Java memory on the server document. Megabytes of native memory that have been allocated by IBM Notes Traveler and all shared memory allocated by other Domino processes running on the same server. When running in a stand alone configuration, the primary demand of IBM Notes Traveler on the server disk subsystem is read and writes to its internal database which stores device sync state information.

If the disk system cannot keep up with read and write requests, then the overall performance of the system can seriously degrade. Use the Domino platform statistics to review the Platform. This value represents the number of read or write requests that have been queued at the OS level. A long queue means that the disk is not able to keep up with demand and is a bottleneck for the system.

If the disk utilization Platform. AvgQueueLen is greater than the number of disk spindles on this partition, then there is a disk bottleneck. For Linux server, if the disk utilization Platform. For example, if you have mobile devices, then your HTTP active threads value should be at least 1. The HTTP server task allocates all of these threads at startup time and keeps them active as long as the server is started. The statistic Http. Workers represents the maximum number of worker threads that are available to handle incoming HTTP requests.

CurrentConnections is the number of worker threads that are currently performing work, and the statistic Http. PeakConnections is the maximum number of connections used since server startup. Ensure that there are enough worker threads allocated to satisfy the Http. PeakConnections statistic. The capacity planning for the high availability configuration is therefore done for each pool of IBM Notes Traveler servers, together with its shared database management system resources comprising the HA solution configuration.

The IBM Notes Traveler HA performance benchmark was executed with up to 12, user devices supported by a single service pool with the relational database systems also configured for high availability. These performance test results are used as the basis for the general capacity guidance in the following HA sections, and were based on the workload used for benchmarking the IBM Notes Traveler 9 release. The resources required in deployment may vary based on usage. When planning a high availability service pool the two primary considerations are the total number of unique devices that must be supported by the pool and how much redundant capacity is desired.

The redundancy is a decision on how many servers you wish to allow to be out of service at the same time intentionally for planned reasons, or in case of unplanned system outages. To achieve the goal of high availability, plan for the pool capacity to adequately support the total number of unique devices required when at least one server is off line. However there are practical performance limitations on the total real time transaction processing load to be handled on the relational database server.

There are also practical performance limitations on how many unique devices are recommended to be supported per IBM Notes Traveler server in the pool. For a Notes Traveler server in the high availability pool configuration, the recommended maximum number of supported devices is 2, per server. The recommended maximum number of unique devices that a IBM Notes Traveler HA service pool can support is 10, based upon the performance stress testing results. To plan the minimum number of HA service pools required: Total Number of devices divided by 10, rounded up to an integer.

The capacity planning of the relational DBMS systems should be done in anticipation of the ultimate known target number of mobile user devices to be supported, if possible, so that over time it is easy to add IBM Notes Traveler servers into a pool for capacity growth without having to make changes to the database server resources for that pool. The DBMS system should not run on the same system as the Louts Notes Traveler server application, and the DBMS should also be configured for high availability so that this critical shared resource is not a single point of failure.

To support 8, to 10, devices, the recommended configuration should be increased to 8 CPU cores with 32GB of physical memory. For optimal performance of the high availability service pool, the DBMS server disk system should be configured to increase the performance of read and write operations to the physical disks. The capacity planning for the customer choice for an IP Sprayer in front of the IBM Notes Traveler server pool is based upon anticipated traffic frequency from all mobile devices being served, and is typically measured in required connections per second.

The IP Sprayer should also be configured for fail-over, so that it is not a single point of failure. The following topics describe options for installing and uninstalling the server:. Refer to the detailed system requirements for more information. For detailed system requirements, see this article: There are considerations to be aware of when installing on a Linux operating system. There are considerations to be aware of when upgrading within a Highly Available HA environment. These items are outlined in the following list. Be sure to also review the general Upgrade considerations before performing any upgrade.

The user home page is a useful starting place for users. It provides status information, links to client software, and user management options. If the user home page is set as the default website for this server, it can be viewed by pointing any browser to http: If the user home page is not set as the default, it can be viewed by pointing the browser to http: This setting takes effect the first time IBM Notes Traveler is started and can be manually changed at a later time.

Select Next. If you are installing from physical media, skip this step. With version 9. Multi-version support on IBM i is fully implemented from release 9. If your environment contains a release prior to 9. If you do not pre-accept the software agreements, the installation process will restore the product to the system, then stop and wait for acceptance of the agreements before completing the installation. You can skip the following procedure if you are installing from a downloaded image.

When the Work with Software Agreements display appears, you see all IBM licensed programs that require software agreement acceptance and whether the agreement has been accepted. Only licensed programs that are not yet installed appear on this display. You can sign on to another session to respond to the message, or ask the system operator to respond.

You should already have installed Domino. If you intend to install from a downloaded image, you should have downloaded the IBM Notes Traveler server installation package and created the appropriate save files. You should verify that QSYS feature code is also included in your library list, if English is not the primary language of your system. It must be in the form nnn. Traveler uses 32 bit JVM by default. There are two methods to enable 64 bit JVM. You might want to use a customized Java virtual machine JVM during the installation.

Working offline

Make sure that you use Java 1. For example, TravelerSetup. For example,. Set to true if you agree to the terms of the license agreement. If set to false , the application is not installed. Path to the IBM Domino program directory, where the nserver. Path to the Domino data directory, where names. Path to the notes. This URL is either the address of the server or a proxy server. When set to 1 during startup, IBM Notes Traveler sets the user home page as the default website for the Domino server. This location is a useful starting place for users because it provides status information, links to client software, and user management options.

If the IBM Notes Traveler user home page is set as the default, it can be viewed by pointing any device browser to http: If the user home page is not set as the default, it can be viewed by pointing any device browser to http: This setting takes effect the first time IBM Notes Traveler is started and can be changed manually at a later time. This optional property applies only to downgrade installations. If a newer version is already installed, false is the default value and the installation is not allowed. Set to true to override the default and downgrade the IBM Notes Traveler server using silent installation.

On Linux, Domino supports the concept of a multi-instance install. Set this flag to true to allow installation to proceed normally if multiple Domino servers are detected on the Linux OS. Note this option is only available in silent mode installation. This is a useful starting place for users because it provides status information, links to client software, and user management options.

For a description of other installer. Every server that is to be deployed as part of a IBM Notes Traveler High Availability pool is first deployed the same way you install a stand-alone server. The first time that the IBM Notes Traveler server is started, it performs any necessary configurations. You might want to perform additional configurations beyond the basics.

The following topics describe additional configuration options. You can configure a variety of IBM Notes Traveler server settings, including server document settings and notes. For additional more information, refer to Server Document settings. This URL ensures that the server sends a link that the devices can use and should be a URL that IBM Notes Traveler users can always access, whether on an internal network or the internet, and should not change. If there is a reverse proxy in use, the URL should be set using this reverse proxy name.

This communication is only on the local system so no external firewalls ever see this traffic. Controls access to the IBM Notes Traveler server for users with Person documents in either the primary directory of this server or any secondary directories that are trusted for credentials using Domino directory assistance.

You can also select individual names of users, servers, and groups to allow access to the IBM Notes Traveler server. The default blank value means that all certified users and servers can access the IBM Notes Traveler server except any listed in the Not access server field. Select names of users, servers, or groups who should not have access to the IBM Notes Traveler server. You can also use the Access server field to deny access; entering names in the Access server field automatically denies access to those not listed in the field. How frequently a user mail database is checked for changes when it is actively being monitored for Auto Sync.

If you are using an 8. If you are using a version earlier than 8. If this server is configured for High Availability, the Auto Sync TCP port should be disabled as this is not a supported option in this mode. The algorithm to use when sending the connection keep alive message. The keep alive message is sent only if there is no other Auto Sync activity. The initial interval to use for keepalive polling. This value should not be shorter than any network timeout values and not shorter than the minimum interval specified in the next setting.

The minimum interval allowed for keepalive polling. The heartbeat algorithm is not allowed to calculate a value smaller than this value. The maximum interval allowed for keepalive polling. The heartbeat algorithm is not allowed to calculate a value greater than this value. If you are using a Windows Mobile or Nokia client version 8. If a user is inactive for a time greater than this value, the user mail database is no longer actively monitored. As soon as the device is detected by the server after this timeout, the server resumes active monitoring of the mail database.

If a user is inactive for a time greater than this value, the user is purged from the IBM Notes Traveler database. The data must also sync as if it is from a new user. For most installations, changing these settings is unnecessary. They are provided here for your reference in cases where the default values are not compatible with an existing system.

There are only a few parameters that are required to be specified in notes. Any of the optional parameters that are not specified in notes. Many more parameters exist than the ones listed here. All of the IBM Notes Traveler server configuration parameters can be seen in a system dump, or by issuing the command tell traveler config in the Domino console.

Please do not attempt to set any other notes. Unless otherwise specified, the following parameters, by default, are contained in notes. Set during installation to indicate whether the server is running a bit operating system. Default value is true. If true , IBM Notes Traveler automatically optimizes settings for thread and memory usage based on the operating system.

Whether or not to append the Domino domain to the Canonical Name when addresses are converted. For more information, see Name lookup. Whether or not the address cache is enabled for Android devices for data synced server to device. Whether or not the address cache is enabled for devices for calendar data synced server to device using Exchange ActiveSync.

Whether or not the address cache is enabled for devices for contact data synced server to device using Exchange ActiveSync. Whether or not the address cache is enabled for devices for mail data synced server to device using Exchange ActiveSync. Whether or not the address cache is enabled for all devices for data synced device to server. Whether or not the address cache is enabled for Nokia devices for data synced server to device. Whether or not the address cache is enabled for Windows Mobile devices for data synced server to device. Whether or not the address encoding is enabled for devices for data synced server to device using Exchange ActiveSync.

List of fields that count as the canonical name. The rder of these fields are important for priority of results returned. First item has highest priority, then second, and so on. List of fields that count as the internet address. The order of these fields are important for priority of results returned. List of items used for duplicate resolution. If two or more results contain the same value for these items, the first result will be kept and the others discarded. How many items are allowed in the cache before the oldest ones start being deleted to create room for new entries.

Sets how much to bias the AI for each promotion to determine if it is possible to do more promotions. Enables Microsoft Exchange ActiveSync mobile devices to create, rename, move, and delete mail folders from their devices. Note that folder operations on the device are only available when the device is online and is able to connect to the IBM Notes Traveler server. The size of the meeting location field at which IBM Notes Traveler prepends any room information to the meeting description field for Microsoft Exchange ActiveSync devices.

IBM Notes Traveler appends room data to the location field, but ActiveSync devices may truncate the display of the location field. Whether to allow Microsoft Exchange ActiveSync devices to split meetings in IBM Notes into separate meetings when making changes to meetings that apply to current and future instances. When false , changes from the device to split meetings will be rejected by IBM Notes Traveler and a mail message sent to the user stating that the meeting has been restored to its prior state.

When true , IBM Notes meetings will be split into separate instances, as indicated by the device change. Set to true during installation. This value is assumed to be true unless set to false. Determines the number of crashes associated with a Notes document before it is banned. A setting of 0 will disable crash protection. When set to true , a document dump will be performed each time a document is banned. See Repeated crash protection for more details. This parameter is listed here for documentation purposes only.

Please do not modify the value of this parameter. Sets the default logon name used during client configuration. Set to FULL during installation. Default value is the empty string. This parameter indicates that the IBM Notes Traveler server should update the client images that are stored in the database during startup. When complete, this parameter is automatically removed from notes. The following messages are examples:. Notes Traveler: No default value. Set to jdbc: This parameter must be specified to indicate which database to use for synchronization data.

The travelerUtil utility should be used to change this and other related parameters when reconfiguring the server to be in an HA pool. The default value is the empty string. The travelerUtil utility will set this parameter when the database type is changed. Rarely used. If this value is set, then all links will redirect to this URL prefix instead of a user's mail server. The value format would be similar to https: This port will be used for all mail servers.

As a result, it is important that these servers be configured consistently. If your Domino mail servers are configured to use SSL, set this value to https. If not, use the value http. This setting will be used for all mail servers. As a result, it is important that these servers are configured consistently.

Set to 0 to disable Notes link conversion to web links, 1 to enable it. Enabling this feature allows mobile users to read and send encrypted mail messages from their mobile devices. This requires that users load their Notes ID files into their mail files. If encryption is disabled, users cannot send encrypted mail and cannot view it on their devices. To instruct all of the IBM Notes Traveler clients to retrieve their configuration setting from the server, issue the following console command:. This is the complete URL, including https: This can be a proxy or redirected address.

This is used by the server so that links are properly formatted for the device to get to the server as it does for static HTML pages and files. This is used by the server so that links are correctly formatted for the device to get to the server as it does for syncing. This is also in the server document and is overridden by notes. This property can be used to override this selection if the wrong IP address is chosen. This could happen if the server has multiple active network interfaces and it is desirable for the server to use an interface other than the one that was selected.

Set during installation to indicate the installation type. If more than one parameter is specified, they will be separated by a space. This is not recommended. Set to 1 to use the text "Link" and "Notes Link" for the link conversions. Set to zero to use graphical images. Set to 1 to enforce access control for corporate lookup at a user level. Customer should only set to 1 if they use directories that specifically allow and disallow access to certain levels of information. For example, if they use Extended ACL to control lookup results.

If set to 0 or not present , corporate lookup will be performed at a server access level and not user access level, and will therefore not honor access settings such as Extended ACL. This can be useful for older mail programs that do not support HTML. Address Fields that specify a mail address to be used by the device. These fields will be encoded if they contain characters or address formats not supported by mobile devices. The encoded address can then be used on the device to send, reply to or forward mail, and the server will properly decode and send the item.

Default value in desired sort order: The number of records to send to the mobile device for a name look up request. The list is sorted based on order of name lookup items and then truncated to this value. Increasing this value can effect performance of the mobile device. The minimum number of characters that need to be entered before actually performing a name look up search request. Android devices also have a setting on the device to control how many characters are typed before sending the search request. Searching multiple directories can often result in duplicate name look up results being returned.

This field is used to identify fields that are required to be unique in the look up results. For example, name look up will not return two results with the same InternetAddress field using the default settings. Note that the fields specified for unique items must also be specified for name lookup items or the unique item will be ignored during processing.

The installation code performs special processing during the first installation of the IBM Notes Traveler server. Set to 1 to include the original Notes link in the mail as well as the web link. Set to 0 to only include the web link. Sets the interprocess socket connection between the IBM Notes Traveler server and older clients versions 8. This is the servlet listening port number. Add this Notes. It is also used for inter-server communication between servers in an HA pool. Here is the signed Lotus Traveler. This must be sideloaded onto your Playbook while developer mode is enabled no rooting it is just a switch in preferences.

To aid in getting information out to the masses, and after they saw how Lotusphere works apparently, IBM Pulse will stream the keynote from Kevin Cavanaugh. Android 4. For 8. Please apply Traveler 8. Devices under evaluation for possible future support: Here is the announcement of the Tivoli branded software and places to find more information.

Services such as application management and security controls have been delivered by IT organizations for years, but mobile device platforms have unique management needs that disrupt the traditional paradigm. However, rather than implement a separate infrastructure solely for mobile devices, organizations could benefit from a single solution that effectively accounts for these unique needs while providing unified endpoint management. From the Idonotes mailbox: A failed Sametime 8. Lotus Traveler Issue - Help! Registration for the webcast is open!

It will be held Oct 4, at 10am CST. You can stream any previous webcast at the Consultant In Your Pocket site. Recent webcasts include: What's New in Sametime 8. It runs this and next week. Details below! The Lotus User Experience Research team is conducting user research the week of August 22nd extending to the week of Aug 29th as needed and is looking for participants.

You will be asked to attend a minute online session connection details to follow where strategic design direction, encompassing multiple IBM products, will be shown and discussed. We are looking for a diverse audience to represent a rich set of perspectives. This is not a usability assessment of current products nor a commitment to implement what is shown. This is directional research but your feedback will be used to shape the future direction of the products you use. If interested, please tell us a little about yourself and available days and times using the brief survey [ https: Thank you for your time!

Regards, Brian Brian S. Utesch, Ph. Chris' Performance Problem! Edited, produced and brought to you by Spiked Studio Productions. Earlier in the year I had written an article for publication that I am providing following this news coming true. Each year a new theme is launched to drive the flow around the conference as new products are announced and futures discussed.

They soon became self proclaimed, and known to some, as an industry leader in this space. With the recent release of Connections 3. However, the stigma of the name Lotus hangs heavy. It carries with it 20 years of weight from Lotus Notes and the nagging thought of the old anytime you say Lotus.

So how would IBM break away, while moving forward the implementations of such products as Connections, Portal and and freshly remodeled and painted Notes? Removing the Lotus moniker is a first step in that transition. In no way am I hinting or saying that the actual products under the Lotus banner would be retired. Simply the Lotus portion of the name itself. They have begun this movement years ago by placing IBM at the head of each product name.

Removing the Lotus from the middle is not a trivial task. Nor should IBM treat this decision lightly. Back at Lotusphere, Social Business was pushed into everyone's minds as soon as the Opening General Session kicked off. All based on a collection of IBM software properties. From this alone is makes perfect sense for IBM to bring these all together as one brand face and name, much like Cognos was brought into the IBM banner. Since Lotusphere both the products Connections and Sametime have had the Lotus name removed from the product marketing.

While we do still the the name Lotus in the actual installed product in some places, new efforts will not show it when making future announcements and marketing. IBM held massive press events last year around Project Northstar. While much of the press was there, the splash was not made. Where does this leave Lotus in the new IBM picture? As a name that held strength in the enterprise messaging and application platform space.

As a name that still haunts many people as a horrid experience because they were stuck on older versions or never experienced the full customer experience. As a name to soon be retired, it's jersey hung in the banners and all the awards placed high on the IBM trophy case as an acquired, assimilated and merged product line in the IBM behemoth.

Goodbye Lotus brand name. Hello IBM collaboration. Ted is committed to maintaining high customer satisfaction while helping customers align software solutions with their strategic business goals. Products think Sametime, Connections and more will not be going away at all. Many were questioning and looking for a statement from IBM. I think we have some answers they were looking for. This is an overhaul of direction and branding to make IBM seen more as a single package, instead of multiple requirements.

Earlier this year I wrote and article for another online publication which I will post in later today in a follow up article. I would suggest if you want to attend the third year of the North American Lotus User Group gathering, register soon for the vent taking place August , Then stay for the bonus day.