Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

J2EE SETUP

VIEWS: 20 PAGES: 17

									How-to Guide
SAP NetWeaver 2004s




How To…
Setup
Additional
WIN32 J2EE
Engine for
Setup Package
Creation with
MI
Version 1.00 – October 2006




Applicable Releases:
SAP NetWeaver 2004s
(User Productivity Enablement -Mobilizing Business
Processes)
© Copyright 2006 SAP AG. All rights reserved.                contained in this document serves informational
                                                             purposes only. National product specifications may vary.
No part of this publication may be reproduced or
transmitted in any form or for any purpose without the       These materials are subject to change without notice.
express permission of SAP AG. The information                These materials are provided by SAP AG and its affiliated
contained herein may be changed without prior notice.        companies ("SAP Group") for informational purposes
                                                             only, without representation or warranty of any
Some software products marketed by SAP AG and its            kind, and SAP Group shall not be liable for errors or
distributors contain proprietary software components of      omissions with respect to the materials. The only
other software vendors.                                      warranties for SAP Group products and services are those
                                                             that are set forth in the express warranty statements
Microsoft, Windows, Outlook, and PowerPoint are              accompanying such products and services, if any.
registered trademarks of Microsoft Corporation.              Nothing herein should be construed as constituting an
                                                             additional warranty.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,        These materials are provided “as is” without a warranty
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent   of any kind, either express or implied, including but not
Miner, WebSphere, Netfinity, Tivoli, and Informix are        limited to, the implied warranties of merchantability,
trademarks or registered trademarks of IBM Corporation       fitness for a particular purpose, or non-infringement.
in the United States and/or other countries.                 SAP shall not be liable for damages of any kind including
                                                             without limitation direct, special, indirect, or
Oracle is a registered trademark of Oracle Corporation.      consequential damages that may result from the use of
                                                             these materials.
UNIX, X/Open, OSF/1, and Motif are registered                SAP does not warrant the accuracy or completeness of
trademarks of the Open Group.                                the information, text, graphics, links or other items
                                                             contained within these materials. SAP has no control
Citrix, ICA, Program Neighborhood, MetaFrame,                over the information that you may access through the
WinFrame, VideoFrame, and MultiWin are trademarks            use of hot links contained in these materials and does not
or registered trademarks of Citrix Systems, Inc.             endorse your use of third party web pages nor provide
                                                             any warranty whatsoever relating to third party web
HTML, XML, XHTML and W3C are trademarks or                   pages.
                            ®
registered trademarks of W3C , World Wide Web                SAP NetWeaver “How-to” Guides are intended to
Consortium, Massachusetts Institute of Technology.           simplify the product implementation. While specific
                                                             product features and procedures typically are explained
Java is a registered trademark of Sun Microsystems, Inc.     in a practical business context, it is not implied that those
                                                             features and procedures are the only approach in solving
JavaScript is a registered trademark of Sun Microsystems,    a specific business problem using SAP NetWeaver. Should
Inc., used under license for technology invented and         you wish to receive additional information, clarification
implemented by Netscape.                                     or support, please refer to SAP Consulting.
                                                             Any software coding and/or code lines / strings (“Code”)
MaxDB is a trademark of MySQL AB, Sweden.                    included in this documentation are only examples and
                                                             are not intended to be used in a productive system
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other           environment. The Code is only intended better explain
SAP products and services mentioned herein as well as        and visualize the syntax and phrasing rules of certain
their respective logos are trademarks or registered          coding. SAP does not warrant the correctness and
trademarks of SAP AG in Germany and in several other         completeness of the Code given herein, and SAP shall
countries all over the world. All other product and          not be liable for errors or damages caused by the usage of
service names mentioned are the trademarks of their          the Code, except if such damages were caused by SAP
respective companies. Data                                   intentionally or grossly negligent.
1      Scenario ................................................................................................................................... 2
2      Introduction .............................................................................................................................. 2
3      Prerequisites ............................................................................................................................ 3
4      The Step By Step Solution....................................................................................................... 3
    4.1      Setup J2EE Engine on an WIN32 Machine .................................................................... 3
    4.2      Setup and Configure the SAP NetWeaver Mobile Administrator for SPC ...................... 6
    4.3      Create Users and corresponding roles for SPC............................................................ 11
    4.4      Deploy the Mobile Components .................................................................................... 13
    4.5      Create setup package using SPC ................................................................................. 14




                                                                                                                                                        -1-
1 Scenario
You are running your SAP NetWeaver AS (ABAP + JAVA) 2004s not on a Windows
32bit environment. You want to create setup packages using the new functions of SAP
NetWeaver Mobile Administrator.


2 Introduction
With SP09 of SAP NetWeaver 2004s a new administration UI for Mobile Infrastructure
was introduced. It is completely integrated into the SAP NetWeaver Administrator.

The new functionalities coming with SAP NetWeaver Mobile Administrator range from
central monitoring of your mobile landscape to deployment related tasks like assigning
mobile applications to devices, users or groups of users.

Setup Package Creation (SPC) is a new functionality that allows you to create
installation files already containing all required mobile components as well as application
data (for smart sync applications). You can create such an image for an individual user
or for multiple users. These can be easily distributed to the mobile devices.

The process of creating these setup packages just simulates on the server the
interaction the user typically has to execute when setting up the MI Client. Say SPC
installs a client locally, synchronizes several times in order to get it registered with the MI
Server (receive Device ID), get the mobile applications/add-ons deployed and to receive
the business data. Finally the client is packed as an archived file including an installer
program.

Due to the outlined procedure setup packages can only be created on a platform a MI
Client is available for.

If you run your mobile landscape in a non-Windows or 64bit environment you can setup
an additional J2EE Engine to host the SPC functionality.




                    Main J2EE                             ABAP
                         (e.g. Unix)                      (e.g. Unix)




                     Additional
                       J2EE
                          (Win32)

                    Figure 1 - Landscape using additional J2EE for SPC




                                                                                                  -2-
3 Prerequisites
You already have a working mobile landscape, say that you have your ABAP and JAVA
stack (Main J2EE) already setup and running (for more information on how to setup a
complete mobile landscape refer to the Installation Guide for MI).

This guide describes the steps based on SP09. If you run another SP screenshots might
be different.


4 The Step By Step Solution
In the following steps you find detailed information on how to setup an additional WIN32
J2EE Engine and which configuration steps are necessary to use it for SPC.

4.1    Setup J2EE Engine on an WIN32 Machine

1. Install the Java Virtual Machine for
   the J2EE Engine release. Check
   http://service.sap.com/pam
   NetWeaver to find the supported
   SDK/JDK versions for your
   NetWeaver release. Download the
   required JDK/SDK e.g. at
   http://java.sun.com/downloads




2. Download the installation files for the
   J2EE Engine from
   http://service.sap.com/swdc. Choose
   usage type AS Java.

      Extract the downloaded files to a
      local folder and start SAPINST.exe
      (.\NW_2004s_SR1_SAP_Installation
      _Master\IM_WINDOWS_I386
      \sapinst.exe)




                                                                                           -3-
3. Choose the desired setup option for
   the additional J2EE Engine.
   Installing Usage Type AS Java is
   sufficient. Follow the installation
   wizard steps in order to enter e.g.
   location of the required software
   packages, system ID* (SID) for the
   new J2EE Engine or the DB
   installation options. Finally start the
   installation.




    * use a new SID which is unique in
    your system landscape




4. Update the installation to the same
   SP level your productive mobile
   landscape runs on. To do so
   download the required software
   packages from
   http://service.sap.com/swdc, extract
   the files and run JSPM
   (<SAP_HOME>\sap\<SID>\JC<INS
   T_NO>\j2ee\JSPM\). Follow the
   steps of the installation wizard.




                                             -4-
5. Deploy SAP NetWeaver Mobile
   Administrator as well as the SAP
   NetWeaver Mobile Client at the
   same patch level used in the Main
   J2EE. Download the corresponding
   SCA files* from
   http://service.sap.com/swdc and
   place them in the
   <SAP_HOME>\sap\trans\EPS\in
   folder. Deploy them using JSPM.

    You start JSPM using go.bat batch
    file under
    <SAP_HOME>\sap\<SID>\JC<INST
    _NO>\j2ee\JSPM.


* You find the files following
download Support Packages and
Patches Entry by Application
Group SAP NetWeaver SAP
NetWeaver SAP NetWeaver
2004s Entry by Component Mobile
Infrastructure
Download MI Administration 7.00 & MI
Client 7.00




                                        -5-
4.2    Setup and Configure the SAP NetWeaver Mobile Administrator for SPC

The following procedure will only describe the relevant configuration steps in order to run
SPC mechanism. To get the full SAP NetWeaver Mobile Administrator functionality follow
the steps described in the Installation Guide for Mobile Infrastructure.


1. All the information SPC mechanism
   needs to build setup packages
   resides in the ABAP System of your
   mobile landscape. To enable SPC to
   access this information you have to
   deploy and configure the Java
   Resource Adapter (JRA).

      To do so run the deploy tool of the
      J2EE Engine. To start it execute the
      batch file DeployTool.bat under
      <SAP_HOME>\sap\<SID>\JC<INST
      _NO>\j2ee\deploying




2. Create a new project by specifying a
   corresponding name e.g. “JRA”.




                                                                                              -6-
3. Switch to the “Deployer” tab and
   choose Deploy     EAR      Deploy
   module from the menu bar.




4. You can find the JRA archive
   (sapjra.rar) under
   <SAP_HOME>\sap\<SID>\SYS\glob
   al\ra




                                       -7-
5. After loading the module you can
   see the details for the module.
   Switch to the properties tab to set
   the initial properties. The values can
   be altered after deployment using
   the Visual Admin tool.
 Parameter      Value
 SAPClient      Client of the ABAP
                Instance, e.g. 100
 ServerName     Host name of the
                ABAP Instance, e.g.
                miserver.sap.com
 PortNumber     System number of the
                ABAP Instance, e.g. 00
 Language       Language Key, e.g. EN
 UserName       User to connect to the
                ABAP Instance. You
                can reuse the MI
                service administration
                user used to connect
                the Main J2EE to the
                ABAP instance
 Password       Password of the MI
                service administration
                user
6. Choose Deploy Connect
   to connect to your J2EE Instance.
   After successfully connected choose
   Deploy Deployment Deploy
   Module to start deployment process.

    Keep the displayed name and start
    the module after deployment.

    If all steps went fine you can close
    the Deploy Tool.




                                            -8-
7. Start the Visual Administrator by
   executing
   <SAP_HOME>\sap\<SID>\JC<INST
   _NO>\j2ee\admin\go.bat

    Navigate to
    Server Services Connector
    Container. Here you can find your
    newly deployed JRA module. To
    make it available for SAP
    NetWeaver Mobile Administrator you
    need to copy the service to the new
    name “SAPJRAFactory_EN”.
    Further you can copy the service to
    additional languages by using the
    name SAPJRAFactory_<LG_KEY>”.
    Attention: An entry for language EN
    is mandatory.

    Following the tabs Managed
    Connection Factory      Properties
    you can find/edit the parameter
    values entered in the Deploy Tool.


8. Enter configuration of SPC by
   choosing
   Server Services Configuration
   Adapter.
   Choose mobile_setupGeneration in
   the tree on the right-hand side.
   Switch to change mode and enter
   the configuration values by double
   clicking the values. Please find infos
   on the parameters under:
http://help.sap.com/saphelp_nw2004s/h
elpdata/en/43/122f4ef2dc2be8e1000000
0a1553f7/frameset.htm




                                            -9-
9. Configure the download of mobile
   components by choosing
   Server Services Configuration
   Adapter.
   Choose mobile in the tree on the
   right-hand side. Switch to change
   mode and enter the configuration
   values by double clicking the values.
   Please find infos on the parameters
   under:
http://help.sap.com/saphelp_nw2004s/h
elpdata/en/95/239442062bcd6ae100000
00a155106/frameset.htm




                                           - 10 -
4.3   Create Users and corresponding roles for SPC

All the above steps just outline the configuration steps for SPC. This means that all other
deployment related tasks like creating hierarchy groups, device configurations etc. need
to be handled using SAP NetWeaver Mobile Administrator residing in the Main J2EE.
Therefore you should deactivate all other functionality in the additional J2EE for your
users in order to avoid getting mixed up with different J2EE Engines and what to do
where. For that reason you create a new role for SPC just containing the relevant
authorizations.
Beside that you could consider to remove all SPC related actions from all roles of your
Main J2EE to avoid unintentional mistakes.


 1. Create a user for creating setup
    packages using J2EE Engine User
    Management. Open
    http://<host>:<port>/useradmin in
    your browser.
    Port is typically 50000, check
    http://help.sap.com/saphelp_nw200
    4s/helpdata/en/a2/f9d7fed2adc340a
    b462ae159d19509/frameset.htm to
    identify the HTTP port of your
    installation. Logon using the J2EE
    Administration user.

      Choose Create User and create a
      new user by filling in the required
      information.

      Choose Create to create the new
      user.
 2. Create Role for SPC using J2EE
    Engine User Management.

      Enter a name and description.
      Select in the Available Actions the
      following ones:
      - tc~mobile~admin~ump.MaintainSetupPackage
      - tc~mobile~admin~ump.ShowSetupPackage

      Choose Save.




                                                                                              - 11 -
3. Assign the newly created user to
   the role.




                                      - 12 -
4.4   Deploy the Mobile Components

In order to create setup packages you have to redeploy all mobile components in the
additional J2EE. The reason for that is that SPC uses the local SDM to receive the
deployment files (since NW2004s SP10 or after implementing note 974840 – Web
Dispatcher Integration).
If you run a lower SP without having note 974840 implemented you just need to
redeploy the framework files as they are always taken from the local SDM (done with
deployment of NetWeaver Mobile Administrator).
Attention: Deploy same mobile component versions already deployed in the Main J2EE.




1. Redeploy your mobile components
   using JSPM. The steps are the
   same as for deploying NetWeaver
   Mobile Administrator SCA.




                                                                                      - 13 -
4.5   Create setup package using SPC

When all above steps have been executed successfully you can use SPC.



1. Logon to NWA using the above
   created user. If only the above
   created role is assigned to the user
   you can see a screen similar to the
   screenshot aside, only SPC
   functionality of SAP NetWeaver
   Mobile Administrator is available.

      If you may get an error message
      that SLD is not setup you can
      simply ignore it as it is just required
      by the monitoring functions of SAP
      NetWeaver Mobile Administrator.




                                                                        - 14 -
www.sdn.sap.com/irj/sdn/howtoguides

								
To top