Sun Java System Mobile Enterprise Platform 1.0 Release Notes

Hardware and Software Requirements

This section lists the requirements that must be met before installing the MEP software.

These requirements are in addition to the requirements for the sync database you use (either MySQL or Oracle). Consult the database documentation for information about those requirements. If you use Oracle software for the sync database, it is strongly recommend that you install it on a different system from the one where you install the MEP software. See the Sun Java System Mobile Enterprise Platform 1.0 Installation Guide for more information.

The requirements for MEP are similar to the requirements for Application Server, because the MEP software is deployed on Application Server. Table 1–1 shows these requirements.

Table 1–1 Supported Operating Systems

Operating System 

Minimum Memory 

Recommended Memory 

Minimum Disk Space 

Recommended Disk Space 

JVM 

Sun Solaris 10 (SPARC, x86) 

512 MB 

1 GB 

250 MB free 

500 MB free 

Java SE 6 

Red Hat Enterprise Linux 4 

512 MB 

1 GB 

250 MB free 

500 MB free 

Java SE 6 

Microsoft Windows 2003, Microsoft Windows XP Professional 

1 GB 

2 GB 

500 MB free 

1 GB free 

Java SE 6 

Supported Mobile Devices

MEP is supported on all Java ME and GPRS/UMTS enabled mobile devices that support the following specifications:

See Client Device Requirements in Sun Java System Mobile Enterprise Platform 1.0 Developer’s Guide for Client Applications for details on the supported Java ME specifications.

MEP has been tested with the following mobile client devices:

Before you can install the MEP client software on a Palm Treo device, the device must have the IBM J9 Java Virtual Machine (JVM) installed on it. You must obtain the J9 JVM from IBM.

A Palm Treo device running the PalmOS software must have a memory card.

Supported EIS/EAI Systems and Databases

MEP has been tested with the Siebel CRM and SAP ERP systems and with the MySQL and Oracle databases.

Configuring the Sun JCA Adapter for SAP

If your EIS/EAI system is SAP, you must download some libraries from SAP and must also configure the Application Server to work with the Sun JCA Adapter for SAP, as described in the following sections:

ProcedureTo Download the SAP Libraries

The SAP Java Connector toolkit (SAP JCo) is a middleware component that enables the Sun JCA Adapter for SAP to communicate directly with SAP. This component is required by the SAP BAPI OTD Wizard, which you use when you develop an Enterprise Connector that accesses a Sun JCA Adapter. (See Accessing a Sun JCA Adapter for an EIS/EAI System in Sun Java System Mobile Enterprise Platform 1.0 Developer’s Guide for Enterprise Connectors for details.)

You must be a licensed SAP customer in order to gain access to these SAP libraries.

  1. Log in to the SAP site http://service.sap.com/connectors using your authorized login.

  2. Click SAP Java Connector.

  3. In the left-hand menu, click Tools and Services.

  4. Download the SAP JCo archive file for your operating system.

  5. Unzip the archive file into a directory of your choice.

    After you unzip the archive, you will find a JAR file named sapjco.jar. You will also find one or two libraries specific to your operating system (the number varies depending on the version of SAP you are using).

  6. Copy all these files into the Application Server lib directory.

    This directory is as-install/lib, where as-install is the directory where you installed the Application Server.

ProcedureTo Configure the Application Server for the SAP Adapter

You need to create a connector connection pool and a connector resource for the Sun JCA Adapter for SAP, and then set properties for the connector connection pool. On a two-tier MEP installation, this task must be performed on the Enterprise tier (the second tier).

  1. Create the sappool connection pool.

    1. In a browser, go to http://hostname:4848/ and log in to the Application Server Admin Console as admin.

      The default password is adminpass.

      For a single-tier installation, hostname is the name of the system where MEP is installed. For a two-tier installation, hostname is the name of the system where the Enterprise tier (the second tier) is installed.

    2. In the tree view, expand Resources, then Connectors, and then select Connector Connection Pools.

    3. Click New.

      The New Connector Connection Pool panel appears.

    4. Type sappool in the Name field.

    5. Choose sun-sap-adapter from the Resource Adapter drop-down list.

    6. Click Next.

    7. Click Finish.

  2. Create the jcaps/sap connector resource.

    1. In the tree view, expand Resources, then Connectors, and then select Connector Resources.

    2. Click New.

      The New Connector Resource panel appears.

    3. Type jcaps/sap in the JNDI Name field.

    4. Choose sappool from the Pool Name drop-down list.

    5. Click OK.

  3. Modify the settings for the sappool connection pool.

    1. In the tree view, expand CAPS, then expand Connector Connection Pools.

    2. Click sappool.

      If the sappool connector connection pool does not appear in the tree view, expand another node, then expand Connector Connection Pools once again. You should now see sappool.

    3. Specify Client Connection Settings as indicated in the following table.

      Name 

      Description 

      Client Connection Mode 

      Choose Automatic if it is not already selected 

      Application Server Hostname 

      The name of your SAP server 

      System Number 

      The system number given you by SAP (often 00) 

      Client Number 

      The client number given you by SAP 

      User 

      Your SAP user name 

      Password 

      Your SAP password 

      Language 

      The language you use for SAP access 

      System ID 

      The system ID of your SAP installation 

      Use the default values for all other settings.

    4. Click Save.

  4. If you are using a 64–bit JDK, add a JVM setting.

    1. In the tree view, select the Application Server node.

    2. Click the JVM Settings tab, then click the JVM Options sub-tab.

    3. Click Add JVM Option.

    4. In the Value field, type -d64.

    5. Click Save.

    6. Click the Restart Required link.

    7. Click Stop Instance.

    8. Restart the Application Server from the command line:


      as-install/bin/asadmin start-domain mep