Oracle Mobile Application Server Changes in Release 12: Administrator’s Guide An Oracle White Paper January 2007

2

Contents

CONTENTS ......................................................................................................................................................................................1 1. INTRODUCTION ....................................................................................................................................................................3

1.1 OVERVIEW...........................................................................................................................................................................3 2. NEW ENVIRONMENT VARIABLES IN R12......................................................................................................................4 3. CHANGED DIRECTORY STRUCTURE IN R12................................................................................................................5 4. DETAILS OF CHANGES – DIRECTORY STRUCTURE..................................................................................................6 5. DETAILS OF CHANGES – SECURITY ...............................................................................................................................8 6. DETAILS OF CHANGES – AUTOCONFIG ENGINE......................................................................................................10 7. DOCUMENT REFERENCE .................................................................................................................................................11

7.1 CURRENT DOCUMENT REFERENCES ..................................................................................................................................11 8. FAQ..........................................................................................................................................................................................12

3

1. Introduction

1.1 Overview This document details the changes made to the Mobile Application Server (MWA) configuration for Release 12 (R12).

The following changes were made:

o Changes to R12 directory structure

o Changes for Security

o Changes for Autoconfig Engine

4

2. New Environment Variables in R12

The following is the new environment variable introduced in R12.

o $INST_TOP

The following are the new directories that the MWA server uses:

o $INST_TOP/admin/scripts

o $INST_TOP/admin/install

5

3. Changed Directory Structure in R12 Prior to R12:

o The MWA server startup files were located under “$MWA_TOP/bin” directory

o The MWA server configuration files were located under “$MWA_TOP/secure” directory

In R12, these files are available under $INST_TOP/admin/scripts and $INST_TOP/admin/install directories, and the MWA server use the files only from these directories.

Note: Though the directories under $MWA_TOP continue to exist, the MWA server no longer uses those files.

The only exception is the MWA Dispatcher. The MWA Dispatcher startup file continues to reside under $MWA_TOP/bin directory and MWA server uses the same file.

Directories used by MWA server prior to R12 Directories used by MWA server in R12 for the same purposes

$MWA_TOP/bin $INST_TOP/admin/scripts

$MWA_TOP/secure $INST_TOP/admin/install

6

4. Details of Changes – Directory Structure The following table provides the following details:

o Functionality

o Name of the file

o Location and Usage in 11i

o Location and Usage in R12

Note: mwactl.sh/cmd means that the value applies to both the mwactl.sh (UNIX Shell) and the mwactl.cmd (Win NT) scripts.

(Continued in next page…)

Functionality Name of the file Location Usage Location Usage

Startup the MWA Server mwactl.sh/cmd $MWA_TOP/bin

mwactl.sh/cmd start <port_number> $INST_TOP/admin/scripts

mwactl.sh start <port_number

Shutdown the MWA Server mwactl.sh/cmd $MWA_TOP/bin

mwactl.sh/cmd -login adminuid/pwd stop<port_number>

mwactl.sh/cmd -login adminuid/pwd stop_force <port_number> $INST_TOP/admin/scripts

mwactl.sh -login adminuid/pwd stop_force <port_number>

Kill a user's MWA Session mwactl.sh/cmd $MWA_TOP/bin

mwactl.sh/cmd -login adminuid/pwd killsession <session_name> <port_number> $INST_TOP/admin/scripts

mwactl.sh -login adminuid/pwd killsession <session_name> <port_number>

Startup MWA Dispatcher mwactl.sh/cmd $MWA_TOP/bin

mwactl.sh/cmd start_dispatcher $INST_TOP/admin/scripts

mwactl.sh start_dispatcher

Shutdown MWA Dispatcher mwactl.sh/cmd $MWA_TOP/bin

mwactl.sh/cmd stop_dispatcher $INST_TOP/admin/scripts

mwactl.sh stop_dispatcher

11i R12

7

Functionality Name of the file Location Usage Location Usage

Modify configuration parameters like:a) DBC File locationb) Log level and Log files locationc) Default Telnet portsd) Dispatcher configuration etc. mwa.cfg

$MWA_TOP/secure

Modify the corresponding parameters in the file

$INST_TOP/admin/install

Modify the corresponding parameters in the file

Modify Device Key configuration mapping

deviceIP.ini

$MWA_TOP/secure

Modify the corresponding parameters in the file

$INST_TOP/admin/install

Modify the corresponding parameters in the file

Modify MWA Device Profile options

default_key.ini,gui_key.ini

$MWA_TOP/secure

Modify the corresponding parameters in the file

$INST_TOP/admin/install

Modify the corresponding parameters in the file

Register MWA Services with GSM Framework

mwamscasvc.sh/cmd

$APPL_TOP/prodcomn/admin/install/<s_contextname>/

mwamscasv.sh/cmd username/password

$INST_TOP/admin/install

mwamscasv.sh/cmd username/password

11i R12

8

5. Details of Changes – Security In 11i, the system received the UserName and Password as command line arguments from the respective scripts. These were used to connect to the applications database. Passing the UserName and Password as command line arguments has the disadvantage of allowing them to be visible in the process table of the environment.

In R12, all the scripts that previously accepted the input parameters in the command line now accept these parameters in the following ways:

o Existing format: <script_name> <command> username/password

o Secure format (for UNIX shell scripts):

o <script_name> <command> <Enter key>

o <username> <Enter key>

o <password> <Enter key>

o Secure format (for NT scripts):

o <script_name> <command> <Enter key>

o <username>/<password> <Enter key>

This applies to all scripts that accepted the Username and Password instead of command lines as well.

Note: These enhancements do not affect the existing use of the scripts.

The following table provides the details.

(Continued in next page…)

Functionality Valid usage in 11i Valid usage(s) in R12

mwactl.sh/cmd -login adminuser/password stop_force <port_number>

a) mwactl.sh/cmd -login adminuser/password stop_force <port_number>

b) mwactl.sh stop_force <port_number> <Enter> username <Enter> password <Enter>

c) mwactl.cmd stop_force <port_number> <Enter> username/password <Enter>

mwactl.sh/cmd -login adminuser/password stop <port_number>

a) mwactl.sh/cmd -login adminuser/password stop <port_number>

b) mwactl.sh stop <port_number> <Enter> username <Enter> password <Enter>

c) mwactl.cmd stop <port_number> <Enter> username/password <Enter>

Shutting down the MWA Server

9

Functionality Valid usage in 11i Valid usage(s) in R12

Kill a user's MWA Session

mwactl.sh/cmd -login adminuid/password killsession <session_name> <port_number>

a) mwactl.sh/cmd -login adminuser/password killsession <session_name> <port_number>

b) mwactl.sh killsession <session_name> <port_number> <Enter> username <Enter> password <Enter>

c) mwactl.cmd killsession <session_name> <port_number> <Enter> username/password <Enter>

Register MWA Services with GSM Framework

mwamscasvc.sh/cmd username password

a) mwamscasvc.sh/cmd username password

b) mwamscasvc.sh -nopromptmsg <Enter> username <Enter> password <Enter>

c ) mwamscasvc.cmd -nopromptmsg <Enter> username/password <Enter>

10

6. Details of Changes – Autoconfig Engine Autoconfig Wrapper Scripts

In R12, Autoconfig manages all MWA services. Because the Autoconfig engine cannot directly use the existing scripts, wrapper scripts were created for the Autoconfig engine to use. The wrapper scripts use the existing MWA scripts to manage services.

The Autoconfig engine uses the following wrapper scripts:

o $INST_TOP/admin/scripts/mwactlwrpr.sh

o $INST_TOP/admin/scripts/mwactlwrpr.cmd

These scripts are to be used only by the Autoconfig engine. These scripts do not change the existing use of any other scripts.

Autoconfig Scripts

The Autoconfig scripts stopall (adstpall.sh) and startall (adstrtal.sh) manage MWA services when the following configuration parameters are set to enabled in the environment context file (<APPL_TOP>/admin/<CONTEXT_NAME>.xml):

o s_other_service_group_status

o s_mwastatus

The default value of these parameters is disabled. Set the parameters to enabled prior to running Autoconfig. See Oracle Applications Maintenance Utilities and Oracle Applications Maintenance Procedures for detailed instructions on managing configuration parameters and server processes using Autoconfig.

11

7. Document Reference

7.1 Document References

Document Name Comments

Oracle Applications Upgrade Guide: Upgrading from Release 11i to Release 12

See: Post-Upgrade Tasks for Supply Chain Management

Using AutoConfig to Manage System Configurations with Oracle Applications 11i

Note: This document is also valid for Oracle Applications Release 12.

OracleMetalink note 165195.1

12

8. FAQ

In R12, where do I find the scripts for startup and shutdown of the MWA server?

Script files for MWA server admin activities are available under $INST_TOP/admin/scripts directory. The names of the files remain unchanged from 11i.

I want to change a few configuration parameters in mwa.cfg. I also want to make some device related changes in default_key.ini. Where do I find these files?

All configuration and parameter files are available in the $INST_TOP/admin/install directory.

Are there any changes to the MWA Dispatcher in R12?

The MWA Dispatcher location and use has not changed in R12.

Will the enhancements made for security and Autoconfig engine change the existing use of MWA-related scripts?

No, the enhancements provided do not change the existing use of these scripts. These changes introduced improved ways of using these scripts.

13

White Paper: Mobile Application Server Changes in R12: Administrator’s Guide January 2007 Author: Ashwin Kumar Chandrasekaran Reviewers: Wilson Lau, Ben Chihaoui OracleMetaLink note 394495.1 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000125 Fax: +1.650.506.7200 www.oracle.com Oracle Corporation provides the software that powers the internet. Oracle is a registered trademark of Oracle Corporation. Various product and service names referenced herein may be trademarks of Oracle Corporation. All other product and service names mentioned may be trademarks of their respective owners. Copyright © 2000 Oracle Corporation All rights reserved.