This section lists the requirements that must be met before installing the Sun GlassFish Mobility Platform 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 Sun GlassFish Mobility Platform software. See the Sun Java System Mobile Enterprise Platform 1.0 Installation Guide (http://download.oracle.com/820-3750) for more information.
The requirements for Sun GlassFish Mobility Platform are similar to the requirements for Enterprise Server, because the Sun GlassFish Mobility Platform software is deployed on Enterprise 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), Open Solaris 2008.11 |
512 MB |
1 GB |
250 MB free |
500 MB free |
Java SE 6 |
Red Hat Enterprise Linux 4, 5 |
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 |
Sun GlassFish Mobility Platform is supported on all Java ME and GPRS/UMTS enabled mobile devices that support the following specifications:
MIDP 2.0
CLDC 1.1 or CDC 1.1.2
JSR-75
See “Client Device Requirements” in Sun GlassFish Mobility Platform 1.1 Developer’s Guide for Client Applications (http://download.oracle.com/820-7206/ggcmp?a=view) for details on the supported Java ME specifications.
Sun GlassFish Mobility Platform has been tested with the following mobile client devices:
BlackBerry smartphone
Palm Treo 700p or 755p device running the PalmOS software
Palm Treo 700wx device running the Windows Mobile software
Before you can install the Sun GlassFish Mobility Platform 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.
Sun GlassFish Mobility Platform has been tested with the Siebel CRM and SAP ERP systems and with the MySQL and Oracle databases.
If your EIS/EAI system is SAP, you must download some libraries from SAP and must also configure the Enterprise Server to work with the Sun JCA Adapter for SAP, as described in the following sections:
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 GlassFish Mobility Platform 1.1 Developer’s Guide for Client Applications, (http://download.oracle.com/820-7206/ggxcs?a=view), for details.)
You must be a licensed SAP customer in order to gain access to these SAP libraries.
Log in to the SAP site http://service.sap.com/connectors using your authorized login.
Click SAP Java Connector.
In the left-hand menu, click Tools and Services.
Download the SAP JCo archive file for your operating system.
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).
Copy all these files into the Enterprise Server lib directory.
This directory is as-install/lib, where as-install is the directory where you installed the Enterprise Server.
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 Sun GlassFish Mobility Platform installation, this task must be performed on the Enterprise tier (the second tier).
Create the sappool connection pool.
In a browser, go to http://hostname:4848/ and log in to the Enterprise Server Admin Console as admin.
The default password is adminpass.
For a single-tier installation, hostname is the name of the system where Sun GlassFish Mobility Platform is installed. For a two-tier installation, hostname is the name of the system where the Enterprise tier (the second tier) is installed.
In the tree view, expand Resources, then Connectors, and then select Connector Connection Pools.
Click New.
The New Connector Connection Pool panel appears.
Type sappool in the Name field.
Choose sun-sap-adapter from the Resource Adapter drop-down list.
Click Next.
Click Finish.
Create the jcaps/sap connector resource.
Modify the settings for the sappool connection pool.
In the tree view, expand CAPS, then expand Connector Connection Pools.
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.
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.
Click Save.
If you are using a 64–bit JDK, add a JVM setting.
In the tree view, select the Application Server node.
Click the JVM Settings tab, then click the JVM Options sub-tab.
Click Add JVM Option.
In the Value field, type -d64.
Click Save.
Click the Restart Required link.
Click Stop Instance.
Restart the Enterprise Server from the command line:
as-install/bin/asadmin start-domain mep |