Configuration of the SAP ME J2EE Server Component Contents

Transcription

1 Contents Installing the Pre-packaged SAP ME Client Components...2 Installing the SAP ME Client Components...2 Configuring the SAP ME Client Components...5 Configuring the Server Settings...8 Configuring Security Settings...9 Configuring the Load Balancing...9 Configuring the SAP ME Client Component...9 Configuring the SAP ME Client...11 Configuring the SAP ME Proxy...11 Checking the System Properties

2 Installing the Pre-packaged SAP ME Client Components Standard Java components are system components that belong to the base groups only. To install the SAP ME Client Components, proceed as follows: 1. Start the Web Console by using the following link: <server>: machine the SAP J2EE Engine is installed on <port>: the machine's standard port 2. Enter your login data and choose login. 3. Choose Applications Install Pre-Packaged Components. 4. Set the flag for Java Framework device specific components, Mobile engine Client Worker, and Java Framework standard components. 5. Choose Install. Installing the SAP ME Client Components The following SAP ME Client Components are available: File Name Use Files in Combination with the Following Operating System JVM118_32_StrongArm.xar Pocket PC 2002 JVM118_SSL_32_StrongArm.xar Pocket PC 2002 This is an optional file. Use this file only if you want to support https for 2

3 IPAQ. In this case don t use JVM118_32_StrongArm.xar. ME21_lang_PocketPC.xar Pocket PC 2002 ME21_PocketPC_2002.xar Pocket PC 2002 ME21_win2000.xar Windows 2000 ME21_win98.xar Windows Choose Applications Install Pre-Packaged Components. 2. Click on Add new. The following screen appears: 3. Use the Browse Button and go to the folder where archives of the SAP ME Client Components are located. The files have xar as extension. Select the first one. 4. Click on Add to load the SAP ME Client Component into the Web Console database. Depending on the SAP ME Client Component this may need some minutes. 5. After the SAP ME Client Component is successfully uploaded, a description of the package and its version is displayed. Choose Apply to install the SAP ME Client Component. 3

4 6. Repeat these steps for each SAP ME Client Component you want to install. 7. Choose install to finally install all selected SAP ME Client Components (see the screenshot below). 4

5 Configuring the SAP ME Client Components The following SAP ME Client Components must be configured: Mobile Engine 2.1 for Windows 2000 Mobile Engine 2.1 for Windows 98 Language Files ME 2.1 Mobile Engine Worker 1. Choose Applications. A list of all SAP ME Client Components appears: 5

6 2. To configure one of the applications, click on the appropriate link (e.g. Mobile Engine 2.1 for Windows 2000). 6

7 3. Check the Deploy checkbox. 4. Choose Apply to save the modification. 5. For Mobile Engine Client Worker application you have to check the checkboxes for Pre-worker and Postworker, too: 7

8 Do not check these boxes for other SAP ME Client Components! Configuring the Server Settings The Server Settings option allows you to set the parameters that affect the overall server operation. Care should be exercised when setting these parameters because many of the parameters are instantly activated when changes are applied. Parameters that require the server to be restarted after they have been applied are noted where applicable. 1. Choose Settings Server Settings. You can configure the following fields: Field Set Date and Time during synchronization Data Preparation Schedule Interval Server Description Specifies whether the clock of each client device should be synchronized with the server during the Tx-Sync process. The period of time in minutes that the data piping scheduler will pause between attempts to retrieve events from the data piping schedule. Note that the scheduler works from the top of the hour, i.e. a value of 60 minutes causes the schedule to be checked at noon, 1pm, 2pm etc. A schedule of 20 minutes causes the schedule to be checked at noon, 12:20pm, 12:40pm, etc. After this value is applied, the server must be restarted for the changes to take effect. The host name or address of the mail server to be used by the system to send s. 8

9 Field Error Handling During Synchronization Description Defines the behavior of the server when an error occurs during the Tx-Sync process: ABORT - the synchronization will be stopped; until the error is resolved the client device will be unable to synchronize successfully. CONTINUE - the synchronization will be completed. ABORT AND MAIL - the synchronization will be stopped and an will be sent to the person listed as the Group's contact; until the error is resolved the client device will be unable to synchronize successfully. CONTINUE AND MAIL - the synchronization will be completed and an will be sent to the person listed as the group's contact. Soap timeout Maximum number of concurrent synchronizations Return sync estimate during synchronization The period of time in seconds that the Tx-Sync process will allow for each asynchronous SOAP transaction to be executed on behalf of the client device; after this value is applied the server must be restarted for the changes to take effect. Please use the default values! Please use the default values! 2. Choose Apply. Configuring Security Settings The following security settings are necessary: 1. Configure https on SAP Web AS. For more information about this, see the SAP Web AS documentation. 2. You must now specify that the Web Console should use https to synchronize with the client. To do this, choose Settings Client Settings and enter the default URL in the Web Services URL field. When you use https for client synchronization, you do not need to specify a security guard in Settings Security Guard. 3. Choose Apply. Configuring the Load Balancing Add additional servers to balance server load. 1. Choose Settings Load Balancing and then add a server. The server load will then be automatically distributed between the servers that you enter here. Configuring the SAP ME Client Component You must now setup some basic settings for the SAP ME Client Component. 9

10 1. Choose Clients, search for the line with the client type you would like to configure and click on the Setup Icon on the right side. You can enter e.g. the following fields if you choose the win2kx86 client configuration: Variables Description JRT JRT_LIB The path to your Java runtime folder. If you set the adddrive field to false, the path must be fully qualified. If you set the adddrive field to true, the drive letter of your SAP ME installation is used. The path to library folder of your Java runtime. If you set the adddrive field to false, the path must be fully qualified. If you set the adddrive field to true, the drive letter of your SAP ME installation is used. XOOMDIR It is important that for the Win32 platforms the Java VM is located in the location specified here. The path to the Web Console libraries. If you set the adddrive field to false, the path must be fully qualified. If you set the adddrive field to true, the drive letter of your Mobile Engine Installation is used. 10

11 Configuring the SAP ME Client You must now setup some basic settings for the SAP ME client. 1. Choose Settings Client Settings and enter the URL of your SAP ME Web Services (e.g Choose Apply. Configuring the SAP ME Proxy You must now setup the following basic settings for the SAP ME Proxy server: 1. Choose Settings System Properties and enter the URL of your SAP ME Proxy Servlet (e.g. (e.g. your AS Host (AS=Application Server) (e.g. pwdf0758.wdf.sap.de) and your System number (e.g. 58). 2. If you are using a SAP R/3 system as backend, the AS Host and the system number settings correspond to the application server setting and system number setting of the SAPGui/SAPlogon properties of your system. 3. Choose Apply. 11

12 After you finished all your configurations choose logout. Checking the System Properties 1. Check the system.props file in the following directories of your SAP J2EE Installation: \services\servlet_jsp\work\jsptemp\mesync\root\system_properties \services\servlet_jsp\work\jsptemp\meserver\root\system_properties The system.props files in these two locations have to be identical. Best way is to copy the system.props file from the meserver file structure to the mesync folder. 2. Check the content of the file with notepad. Example: ashost pwdf0758.wdf.sap-ag.de sysnr=58 12