• No results found

Uninstalling Device Files for Mobile

• Complete the Installation Task Flow appropriate for your implementation.

Demo Mode

Use demo mode to review the Mobile Sales application from the device without connecting to the enterprise.

By running Mobile Sales in demo mode, device users can review and evaluate the application functionality without connecting to the SAP backend system.

To allow device users to run Mobile Sales strictly in demo mode, do one of the following:

• For Windows Mobile devices:

1. Run the Sybase Mobile Sales for SAP CRM installer to copy the device files to a local machine.

2. Copy the appropriate .cab files to a location where all device users have access.

3. Each device user navigates to this location from the device, for example using ActiveSync, copies the .cab file and installs the Mobile Sales application.

4. Each device user launches Mobile Sales and selects Yes to launch the application in demo mode.

• For iPhone:

1. Each device user downloads the Mobile Sales application from App Store or iTunes and runs the Mobile Sales installation on the iPhone device.

2. Each device user launches Mobile Sales and selects Yes to launch the application in demo mode.

CHAPTER 4: Planning Your Installation

CHAPTER 5 Installing Device Files for Mobile Sales and Deploying an ESDMA Package Using the Installer

Use the installer to make Windows Mobile device-specific Sybase Mobile Sales for SAP CRM mobile application files available for provisioning from the server and to deploy a CRM ESDMA package.

Prerequisites

• Install the prerequisites.

• Determine if you want the Mobile Sales installer to deploy an SAP CRM ESDMA package. See SAP CRM ESDMA Package Deployment Prerequisites in this guide.

• Shut down any Sybase products or processes, and associated third-party processes.

• If you are installing the CRM ESDMA using the installer, verify that Unwired Server is started.

• Verify that you are logged in with administrative rights.

• Install Sybase Mobile Sales for SAP CRM from the installation media on the same machine where you installed Sybase Unwired Platform and Sybase SAP DOE Connector.

If Sybase Unwired Platform is installed in a cluster, install Sybase Mobile Sales for SAP CRM and deploy the SAP CRM ESDMA to the primary node.

Task

Sybase Mobile Sales for SAP CRM installs in the Sybase Unwired Platform installation directory:<UnwiredPlatform_InstallDir>\UnwiredPlatform\Mobile Sales for SAP CRM, where <UnwiredPlatform_InstallDir> is C:\Sybase if the default location was used to install Sybase Unwired Platform.

1. Insert the Sybase Mobile Sales for SAP CRM installation media.

If you are installing from a Web download, extract the archive to a temporary directory on the local disk, not a shared drive.

2. On the installer welcome page, click Next.

3. Accept the terms of the license agreement.

a) Select the appropriate geographic location and read the license agreement.

b) Select I Do Agree to the Terms of the Sybase License, for the Install Location Specified, then click Next.

4. Select the checkbox if you want the installer to deploy a CRM ESDMA package, then click Next.

If you chose to deploy the SAP CRM ESDMA, the installer prompts you to enter the location of the ESDMA package, and connection information for SAP and SUP. Enter this information, then click Next.

5. Click Install.

The installation log, CRMInstall.log, is available in

<UnwiredPlatform_InstallDir>\UnwiredPlatform\InstallLogs.

Next

Provision the Mobile Sales application to the device.

See also

• Chapter 4, Planning Your Installation on page 11

• Chapter 2, Installation Task Flow for Windows Mobile on page 3

• SAP CRM ESDMA Package Deployment Prerequisites on page 14

CHAPTER 6 Uninstalling Device Files for Mobile Sales Using the

Uninstaller

If you installed Sybase Mobile Sales for SAP CRM using the installation media, you can uninstall the device files using the Add or Remove Programs option on the Control Panel, which launches the uninstaller. Uninstall Mobile Sales before reinstalling or upgrading.

Prerequisites

You must remove the CRM ESDMA package (SAP_CRM:1.0) deployed to Sybase Unwired Server.

Use SCC or the command line utility (CLU) to remove the ESDMA package before running the uninstaller.

• See SCC online help to use the delete option to delete the SAP_CRM:1.0 package.

• See the Sybase SAP DOE Connector Installation Guide, Appendix: SAP DOE Connector Utility to run the removePackages command.

Task

Note: To uninstall the Mobile Sales application from a mobile device, see the user guide for your device type: Sybase Mobile Sales for SAP CRM User Guide for Windows Mobile or Sybase Mobile Sales for SAP CRM User Guide for iPhone.

1. From the Control Panel, select Add or Remove Programs.

2. Select Sybase Mobile Sales for SAP CRM <version> , and click Change/Remove.

3. Click Next in the welcome window.

4. Click Uninstall.

5. Click Finish when the following message appears: The InstallShield wizard has successfully uninstalled Sybase Mobile Sales for SAP CRM <version> .

CHAPTER 7 Troubleshooting ESDMA Deployment

Provides troubleshooting information when the message that the ESDMA deployment was unsuccessful.

If you attempted to deploy the SAP CRM ESDMA and received a message indicating that the deployment was not successful

Issue: Deployment of the SAP CRM ESDMA resulted in receiving a message indicating that the deployment was not successful.

Solution: Check to verify that the Relay Server or Unwired Server port number used was correct. If an incorrect port number was used, the ESDMA deployment fails.

Entering the incorrect port number or host causes problems with ESDMA deployment. The administrator needs to use SCC to delete or CLU to remove the ESDMA package

(SAP_CRM:1.0), then uninstall Mobile Sales for SAP CRM, and reinstall using the correct information.

To use Sybase Control Center: use the delete option to delete the SAP_CRM:1.0 package. See SCC online help for further instructions.

To use CLU:

• On the server where you attempted to run the installation, start up clu.bat.

• Run the removePackages command.

• Log in to Sybase Control Center to verify that the package has been removed.

• See Deploying the SAP CRM ESDMA using the Command Line in this guide for instructions on redeploying the SAP CRM ESDMA.

See also

• Appendix B, Deploying the SAP CRM ESDMA using the Command Line Utility on page 33

CHAPTER 8 Troubleshooting for Windows Mobile

Provides troubleshooting information when installing and configuring Sybase Mobile Sales for SAP CRM for Windows Mobile. See the Sybase Mobile Sales for SAP CRM Release Bulletin for the latest information. For information on Sybase Unwired Platform issues, see the Sybase Unwired Platform Release Bulletin.

Wrong Device for Code

Issue: When entering the Unwired Server connection information, the error Wrong Device for Code appears in the Sybase Settings log.

Solution: Use Sybase Control Center to clone the user, then have the device user restart the client.

1. From Sybase Control Center:

a. Clone the user.

b. Delete the old user.

2. On the device:

a. Verify that Connection Properties are correct.

b. Go to Sybase Settings > Advanced > Restart Client to restart the client.

The client restart should automatically establish a connection.

3. Try again to connect.

Device Is Not Connected to Unwired Server

Issue: Device must be cradled or have network connectivity.

Solution 1: Check that the device is connected to Unwired Server:

Start > Programs > Sybase Settings.

Select Menu > Show Log.

• Check the log for Connected to Server, and look at the timestamp to see if you are currently connected.

Solution 2: Check that device is connected from Unwired Server:

• Start Sybase Control Center. See Sybase Unwired Platform Installation Guide.

• Check if the status is connected and a device value is present. See Checking Unwired Server Status in Sybase Control Center online help.

CHAPTER 9 Troubleshooting for iPhone

Provides troubleshooting information when installing and configuring Sybase Mobile Sales for SAP CRM for iPhone. See the Sybase Mobile Sales for SAP CRM Release Bulletin for the latest information. For information on Sybase Unwired Platform issues, see the Sybase Unwired Platform Release Bulletin.

Connection Fails With No Error Message

Issue: Mobile Sales for iPhone does not always provide connection failed errors on the device.

Workaround: If you suspect that you are not connected to the SAP system, for example, if you did not enter the Unwired Server connection information correctly, you can check on the device or by using Sybase Control Center.

On the device:

1. From within the Mobile Sales application, tap Settings > General > Connection Information.

2. View the Connection status: Failed or Active.

On Sybase Control Center:

1. Start Sybase Control Center. See Sybase Unwired Platform Installation Guide.

2. For the Unwired Platform Cluster, select Users > Messaging. Click Get Trace to retrieve the device log. See also Sybase Control Center online help.

Synchronization with the SAP system is pending for a long period of time

Issue: While starting the Mobile Sales application from your iPhone, the phone shows the synchonization as pending for an excessively long time. This can be an indication that the connection to the SAP system had failed.

Workaround:

1. Resolve the connection issue. Contact the administrator for assistance, if necessary.

2. Unsubscribe the iPhone. See Unsubscribing to Mobile Sales in the iPhone Device User Guide for additional information.

a. From the Mobile Sales home page, select Settings > General > Connection Information.

b. Tap Unsubscribe.

c. Confirm that you want to unsubscribe.

3. Start Mobile Sales, then tap Settings > General > Connection Information to see if the connection is active. Starting Mobile Sales initiates the synchonization process with the successful connection.

APPENDIX A Mobile Sales Configuration File for Windows Mobile

System Administrators can modify the Mobile Sales system configuration for Windows Mobile in the SybaseCRM.Configuration.xml file. You must update and provision this file to the device before logging into the application (subscribing) for the first time.

The Mobile Sales installation for Windows Mobile contains two versions of this configuration file.

File name Location on Windows Mobile device

To change system configuration set-tings for your company, modify this version of the configuration file. Mod-ify options that begin with SYS_. De-vice users can modify the other options in this file by changing application set-tings.

SybaseCRM.Con-figuration.xml Note: Do not modify.

This file is the runtime version of the configura-tion file.

\Program Files\Mo-bile Sales\Data

During application startup, the Mobile Sales application copies the version from the Templates directory to the Da-ta directory. When device users change Settings from within the application, the new values are written to this con-figuration file.

Once you modify the template version of this file, you can provision it to one or more devices.

For personal/developer installations, you can overwrite the default file in the Templates directory, for example, using ActiveSync. For enterprise installations, use Sybase Unwired Platform to provision the configuration file to the device. In Sybase Unwired Platform System Administration, see Systems Administration > Device User Management > Device

Provisioning > Afaria Provisioning and Device Management.

Table 3. Mobile Sales for Windows Mobile system configuration options Configuration option Description

SYS_PushToNativeContact Determines how native contacts synchronize with Mobile Sales contacts.

Automatic – all new Mobile Sales contacts become personal contacts; however, you must manually indicate which new personal contacts become Mobile Sales contacts. Once connected, if you change contact data in one place, it automatically synchronizes it.

Manual (default) – you must indicate which Mobile Sales contacts that you want to copy to your native contacts, and which personal contacts you want to convert to Mobile Sales contacts. Once you indicate this connection, changes to contact data in one place automat-ically synchronizes data between both con-tact instances.

None – you cannot link personal and Mobile Sales contacts.

SYS_PushToNativeCalendar Determines how native calendar entries syn-chronize with Mobile Sales activities.

Automatic – new Mobile Sales activities for meetings, tasks, and appointments become personal calendar entries; however, you must manually indicate which new personal calen-dar entries become Mobile Sales activities.

Once connected, if you change data in one place, it automatically synchronizes it.

Manual (default) – you must indicate which Mobile Sales activities that you want to copy to your native calendar, and which personal calendar entries you want to convert to Mo-bile Sales activities. Once you indicate this connection, changes to data in one place au-tomatically synchronizes data between both instances.

None – you cannot link personal calendar entries and Mobile Sales activities.

Configuration option Description

SYS_MaximumLoginAttempts Indicates the maximum number of incorrect login attempts before the user is locked out of the ap-plication.

SYS_MaximumLoginAttemptsExceeded Indicates whether the device user has exceeded the maximum number of login attempts. If this option is set to true, the user has exceeded the limit. Instruct the device user to edit this file and set it back to false to be able to log into the ap-plication.

SYS_MinimumMemory Indicates the minimum memory required, in MB, for creating the database and initially subscribing to the SAP system. If this minimum memory is not met, a subscribe is not attempted. If the data-base already exists, this parameter is ignored. The default is 2MB.

In organizations where devices are expected to store large data sets, you can increase this value so that storage memory is not exhausted during the initial subscribe.

SYS_SubscriptionBlockSize Determines the number of messages processed in each message processing interaction from the message queue. The default is 10.

Note: Do not set this value to 0. Use caution in setting this value to a large number or increasing it significantly; runtime memory could be con-sumed during the processing of a large block of messages, thus affecting overall performance.

SYS_Enable_Accounts Enables the Accounts facet in the application.

Enter false to disable the functionality and re-move the icon from the home screen.

SYS_Enable_Contacts Enables the Contacts facet in the application. En-ter false to disable the functionality and remove the icon from the home screen.

SYS_Enable_Activities Enables the Actvities facet in the application.

Enter false to disable the functionality and re-move the icon from the home screen.

APPENDIX A: Mobile Sales Configuration File for Windows Mobile

Configuration option Description

SYS_Enable_Leads Enables the Leads facet in the application. Enter false to disable the functionality and remove the icon from the home screen.

SYS_Enable_Opportunities Enables the Opportunities facet in the applica-tion. Enter false to disable the functionality and remove the icon from the home screen.

SYS_Enable_SalesDocuments Enables the Sales Documents facet in the appli-cation. Enter false to disable the functionality and remove the icon from the home screen.

SYS_Enable_Analytics Enables the Analytics facet in the application.

Enter false to disable the functionality and re-move the icon from the home screen.

SYS_AskEnableDemoMode Enables a pop-up asking to run the the CRM app in demo mode. The default is true. Set this pa-rameter to false to disable the pop-up.

If enabled, the user is prompted by the pop-up only once. The user is not prompted each time the user starts the application.

The app can be run in demo mode without instal-ling Sybase Messaging.

SYS_MappingKey Sets the Google maps API key. For additional

information about the Google Maps API and li-censing, see http://www.google.com/enterprise/

earthmaps/maps.html.

Go to http://code.google.com/apis/maps/sign-up.html to sign up and generate the key.

See also

• Chapter 2, Installation Task Flow for Windows Mobile on page 3

APPENDIX B Deploying the SAP CRM ESDMA using the Command Line Utility

If you choose to deploy the SAP CRM ESDMA manually, use the Sybase SAP DOE Connector command line utility (CLU). You can choose the CLU deployment method instead of deploying by using the Sybase Mobile Sales for SAP CRM installer. This task describes specific steps required to prepare and deploy the SAP CRM ESDMA.

Prerequisites

Generate the SAP CRM ESDMA using the ESDMA Editor provided with gateway to SAP NetWeaver Mobile. Download the ESDMA zip file as an ESDMA bundle from gateway to SAP NetWeaver Mobile.

The ESDMA generation process creates a zipped bundle that contains an XML document, very much like an WSDL, that defines necessary metadata for the Sybase SAP DOE Connector.

Task

When you deploy the SAP CRM ESDMA package using the CLU, you must complete steps unique to this type of ESDMA bundle.

Note: General documentation for the CLU is provided in the Sybase SAP DOE Connector Installation Guide, APPENDIX A: SAP DOE Connector Utility. To remove the SAP CRM ESDMA package, the general instructions provided for the removePackages command in that guide apply for this ESDMA package type.

See also

• SAP CRM ESDMA Package Deployment Prerequisites on page 14

• Chapter 7, Troubleshooting ESDMA Deployment on page 23

Preparing the SAP CRM ESDMA for Deployment

Follow these steps to unzip the ESDMA to the directory structure on the server where Sybase Unwired Platform is installed and create the sup-db.xml file.

Prerequisites

Generate and download the SAP CRM ESDMA from NetWeaver Mobile.

Task

1. On the server where Sybase Unwired Platform is installed, create a directory named ESDMA at <UnwiredPlatform_InstallDir>\Servers\UnwiredServer.

2. Extract the contents of the SAP CRM ESDMA to

<UnwiredPlatform_InstallDir>\Servers\UnwiredServer\ESDMA.

3. Under the ESDMA directory, create a directory named META-INF.

4. In the META-INF directory, create a file named sup-db.xml.

a) Copy and paste the following to the contents of the sup-db.xml file.

<package name="SAP_CRM" short-name="SAP_CRM" sup-name="SAP_CRM“

version="1.0“

java-package="com.sybase.sap.crm.db“

cs-namespace="Sybase.Sap.Crm.Db“

oc-namespace="crm_db_"

<!-- Update with new host and port, listener.url must end with / doe/publish. -->

<property

name="listener.url"

value="http://<supserver host name>:<sup listener port>/

doe/publish" />

<database name="crm-database" />

<database-class name="CrmDatabase" />

<personalization-parameter name="language" type="string"

owner="client" />

<include file="afx-esdma.xml" />

</package>

b) Replace the values highlighted with values applicable to your implementation:

<supserver host name> SUP server host name, or SUP server IP ad-dress

<sup listener port> The listener port for SUP server. Use 8000, the default value , or port number set during the Sybase Unwired Platform installation.

Note: Change only <supserver host name> and <sup listener port>. The other values set in the sup-db.xml have been set to match subscription configuration in Sybase

Note: Change only <supserver host name> and <sup listener port>. The other values set in the sup-db.xml have been set to match subscription configuration in Sybase

Related documents