8/13/2019 MSSA1159

1/22

Oracle Mobile Self-Service Applications Server

Installation Guide

Release 1.0.8.4

March 2003

8/13/2019 MSSA1159

2/22

Contents

Contents........................................................................................................................2Preface ..........................................................................................................................3

Intended Audience............................................................................................................................ 3Getting Started .............................................................................................................4

2.1 MSSA Server Requirements...................................................................................................... 42.2 Using AutoConfig to configure MSSA Server............................................................................. 52.3 Confirming Successful MSSA Server Installation ......................................................................52.4 Granting Mobile Responsibilities ................................................................................................ 5

Server Administration..................................................................................................73.1 mwa.cfg...................................................................................................................................... 73.2 mobile.properties ........................................................................................................................ 8

Device Configuration ...................................................................................................94.1 ......................................................................................................................... 94.2 ................................................................................................................................ 12

4.3 ................................................................................................................................ 14Troubleshooting .........................................................................................................17Server Manager..........................................................................................................18

B.1 Accessing the Server Manager................................................................................................ 18B.2 Monitor Server.......................................................................................................................... 18B.3 Logical Device Manager........................................................................................................... 19B.4 Configure Server...................................................................................................................... 20

Deployment Options ..................................................................................................21C.1 Deploying MSSA Server on De-Militarized Zone (DMZ) ......................................................... 21C.2 Deploying MSSA Server outside the firewall ...........................................................................22C.3 Wireless LAN........................................................................................................................... 22

2

8/13/2019 MSSA1159

3/22

1Preface

The Mobile Applications Server is available in two forms:

Mobile Self-Service Applications Server

Mobile Supply-Chain Applications Server

This manual covers the installation and implementation of the Mobile Self-Service Applications (MSSA) Server. The server will be referred to as the MSSAServer throughout this document.

Intended AudienceThis manual is intended for people responsible for installing the Mobile Self-Service Applications Server, such as:

Database Administrators

System Administrators

Technical Specialists

The setup and install described in this document is required for products such asMobile Financials.

3

8/13/2019 MSSA1159

4/22

2Getting Started

The Mobile Self-Service Application Server is basically a server process thatprovides the run-time engine for Self-Service mobile applications such asFinancials. These Self-Service mobile applications are modules which sit on topof the framework that is provided by the Mobile Self-Service Application Server.

The Mobile Self-Service Application Server functions as a middle-tier betweenhand-held devices (such as PDAs or WAP enabled phones) that function asclients and the database. The following diagram shows an overview of theMobile Self-Service Application Server.

Client(PDA) AR

Mobile Self-Service

Application Server

HCCDatabase

Server

Client

(WAPPhone)

This chapter explains how to install the MSSA Server and contains the followingsections:

MSSA Server Requirements

MSSA Server Installation

Granting Mobile Responsibilities

Confirming Successful MSSA Server Installation

2.1 MSSA Server Requirements

In order to install the Mobile Self-Service Application framework, you must havethe following installed on your machine:

Java Development Kit (JDK) 1.3

o Refer to the README-Config-JDK.html document in the patchfor more information.

Oracle JDBC 8.1.7

4

8/13/2019 MSSA1159

5/22

o Refer to the README-Config-JDBC.html document in the patch

for more information.

Self Service Framework Technology Stack v5.5.1

o Refer to the README-Config-FAQ-Apps-HTTPServer.htmldocument in the patch for more information.

2.2 Configuring the MSSA ServerStarting from release 11.5.7, all configuration files of the Mobile Self-ServiceApplication Server must be configured using the AutoConfig utility except thedevice.cfg file. Once AutoConfig is complete the device_template.cfg file,located in $MWA_TOP/secure, must be manually copied to$MWA_TOP/secure/device.cfg.

In release 11.5.9 AutoConfig will also automatically configure the device.cfgconfiguration file, eliminating all manual configuration.

Administrators should not be editing mwa.cfg, and special care has to be takenwhile editing deviceIP.ini.

Note: Editing these files directly will result in configuration data loss.

2.3 Confirming Successful MSSA Server Installation

To test the MSSA Server install, point your browser to the following URL:http://[Oracle HTTP Server node].[domain]:[HTTP listenerport]/mobile/start

You should get a login screen on your web browser with a username and

password text box.

2.4 Granting Mobile Responsibilities

In order for users to access the mobile enhancements to Oracle Applications,he/she must have the mobile responsibility. The system administrator shouldcreate the user if necessary, and grant the mobile responsibility to the user.

5

8/13/2019 MSSA1159

6/22

6

8/13/2019 MSSA1159

7/22

3Server Administration

This chapter contains information on the configurable parameters in theconfiguration files. Note that these files all contain default values for eachconfigurable parameter and it is advised to not touch these files as AutoConfiggenerates them. If you wish to modify these files, also be reminded that yourchanges will be written over the next time AutoConfig is run to update the file. Inthe future, we may add configuration parameters that can be set to maintain theseparameters through upgrades.

3.1 mwa.cfgThe mwa.cfg file, located in $MWA_TOP/secure, is used to configure serverrelated parameters (such as the login level, application init values, and so forth). Ifyou need to make modifications to this file, you must do so before starting theserver. If you make modifications to this file while the server is running, you mustrestart the server in order for the changes to take effect. Note that in this file,commas are used as token separators. Multiple definitions of the same key areconcatenated in a comma-separated list. The following is a description of theconfigurable properties in the mwa.cfg file.

Property Description

mwa.LogLevel Set this property to establish the appropriate level ofmessages logged to your System Log file. Possiblevalues are: fatal, error, warning, debug, and trace.

Fatal is the most restrictive; it will only displaymessages from fatal errors.Trace is the least restrictive; it will log all messages.

mwa.EnableLogRotation Set this property to enable the log file rotation.Possible values are "Yes" or "No".

mwa.MaxLogFileSize The size (in bytes) that determines when the log fileshould be rotated.

mwa.portalurl This property (a fully qualified url) if present will popup a link on the login page reading portal that willlink to the site specified by the url.

7

8/13/2019 MSSA1159

8/22

3.2 mobile.properties

This file specifies how the mobile zone itself is configured. There are a fewproperties that can be configured.

Property Description

session.timeout This is the amount of time a session shouldbe allowed to exist with no activity.

session.checkFrequency This is how often old sessions are cleaned.It should be set to something around 50000or 60000 (milliseconds)

8

8/13/2019 MSSA1159

9/22

4Device Configuration

All device configurations are done in one file. This file is located in/secure/device.cfg.

The top-level element is . There are three possible child elementsof the top-level. They are:

4.1

The elements provide the main MSSA Server engine, thecorrect set of renderers and the rendering parameters for a particular device. EachLogical Device is an abstraction used to group devices with similar properties andrendering capabilities. Each Logical Device is mapped to a single RendererManager which determines the set of renderers to invoke to produce the bestresults for it. For example, a Motorola phone may be in a Logical Device categoryof PHCOM (Phone.com) and its Renderer Manager would produce WML

(Wireless Markup Language). On the other hand, a Palm VII would be in aLogical Device category of PDAs (Personal Digital Assistants) and its RendererManager would produce HTML.

A System Administrator can also tweak a given Renderer Manager throughLogical Device properties to produce the optimal markup language for a givenLogical Device category. For example, even though both the Compaq iPAQ andPalm VII use the same renderers, the renderers can tell from the Logical Deviceproperties whether or not to render information in color. A table of Logical

Device Properties and their purposes is listed below.

Property Name Required? Multiple?

Description

Name Y N The name of the LogicalDevice.

Default Y N Whether this is the defaultLogical Device, if the devicecannot be mapped to a LogicalDevice.

WildcardCharacte N N Wildcard Character used to

9

8/13/2019 MSSA1159

10/22

r specify the UserAgent with

wildcard expression.

UserAgent Y Y UserAgents that are grouped inthe Logical Device, and

therefore, should use the LogicalDevice's Renderer Manager. Incase of a User Agent string with

wildcard expression, eachLogicalDevice entry is allowedto specify one wildcard characterwith one or more wildcard UserAgent strings. If during runtime,a particular device User Agentstring matches more than onesupplied wildcard expression,the one with the closes match isselected.

MimeType Y N Expected Mime Type and whatthe Mime type of the response tosuch a Logical Device should be.

Cookies N N Whether this device supportscookies.

ImageExtension N N Type of images the LogicalDevices can display

Width Y N The display width

Height Y N The display height

SDUSize N N The SDU Size is the maximumpage size in bytes on web-

enabled phones. This variable isused for menu paging on web-enabled pshones.

MaxDisplayRows N N This parameter allows theadministrator to set themaximum number of rows thatcan be displayed on a menu for agiven device.

Color N N Whether the devices in thiscategory support color.

StyleSetName N N What Style definitions to use.

ColorSetName N N What Color definitions to use.TableDisplay Y N If tables can be displayed on

these devices.

EmailSupport Y N If an email can be sent from theclient devices.

PhoneCallSupport Y N Whether the devices in the groupcan make phone calls.

RendererManager Y N Which set of renderers to use

10

8/13/2019 MSSA1159

11/22

when rendering the applicationpages.

XSLSheet N N Use what XSL sheet to create theMarkup from the XML, when

using the XML RendererManager. (Not used very often)

Each LogicalDevice also defines a StyleSet and a ColorSet. A StyleSet helps therenderers change MSSA Application Styles (such as Prompt, Message, Heading1,and so forth) into markup language. For example, a System Administrator may

determine that on a Palm VII prompts look best in Bold, however, on a Pocket PCprompts look best in Italics(this is an exaggerated example). The administratorcan then have two Logical Devices, one bound to a StyleSet which shows

prompts in Bold,and the other bound to a StyleSet which shows prompts inItalics, even though they have the same Renderer Manager. A ColorSet helps therenderers change MSSA Application colors (such as background and link colors)into markup language. More about ColorSets and StyleSets is covered in later

sections.Logical Devices can be configured in one of two ways.

By editing the device.cfg XML file directly

By using the Server Manager.

4.1.1 Registering a New Device

A UserAgent String identifies each device. If the server does not recognize theUserAgent String of the device, you can add it to the device.cfg file by:

Determining the UserAgent String of the device Associating the UserAgent String with the appropriate Logical Device.

Determining the User Agent String

If a particular device does not register properly when logging into the MSSA

Server, you can determine the logical devices UserAgent string to register withthe server. When a device logs in and is not recognized by the server, the MSSAServer will log the UserAgent string to the log file.

Open up the log file and look for a string near the end of the file that looks likethis:

[Fri Oct 05 13:39:18 PDT 2001] Fail to look up logical

device.

This is the line indicating that there was an error looking up the device. The lineabove it should look like this:

[Fri Oct 05 13:39:18 PDT 2001] MWA_LD_USER_AGENT: Deviceuser agent string: Mozilla/4.0 (compatible; MSIE 5.01;Windows NT 5.0).

All the text after the phrase Device user agent string: is considered to be theUserAgent String. This should be the string used in the next section.

11

8/13/2019 MSSA1159

12/22

Associating a User Agent String with a Logical Device

Identify which Logical Device grouping the device belongs based onMarkup language, size of screen, color support, and so forth.

Under the tag, add a tag with the UserAgent string of the device you would like to bind to this Logical Device.For example, in the following parameter string we have identified a new

Motorola phone using a Phone.com 4.8 browser:

PHCOMMOT-C80/0.0.21 UP/4.8mMWAPhCRendererManager

Now whenever this particular Motorola phone is used, the Phone.com rendererswill be used.

4.2

The element helps the renderers for a given Logical Device renderapplication styles into markup language, as described above. Application Stylesare styles defined by the MSSA Server to ensure consistency across allapplications. For example when a developer wants to create a prompt for hisapplication, he/she will use the application style "Prompt" and bind the style tothe text of the prompt.

For a given Logical Device this application style is then mapped to a specific fontface, font size, font style and font color. By modifying application styledefinitions in a given style set, the system administrator can control how the givenapplication style is rendered on the Logical Device to which the style set is

bound, across the whole system. For example, if the Logical Device PDA isbound to the StyleSet default and the system administrator changes the prompt

style in the default StyleSet so that it is Bold instead of Plain text, then all

prompts appear Bold rather than in Plain text when rendered on client devices inthe PDA Logical Device grouping.

Different Logical Devices can be bound to different StyleSets so that a systemadministrator can decide that all prompts should display in bold on PDAs, and inplain text on phones.

A StyleMap consists of multiple StyleSets, each style set has the followingproperties:

Property

Name

Required? Multiple

?

Description

Name Y N The name of the StyleSet

Inherits Y N What StyleSet it inherits. Often theadministrator simply wants to change asingle style between two LogicalDevices. In this case, he can define a

12

8/13/2019 MSSA1159

13/22

single StyleSet which has all of the styledefinitions for the first Logical Device.It would then inherit the first StyleSet inthe second StyleSet, and only overwritethe styles that are different between theStyleSets.

Style Y Y An element that defines a style

(described in further detail below)

A StyleSet consists of multiple Styles. Each Style has the following properties:

Property

Name

Required? Multiple

?

Description

Name Y N The name of the Style

FontFace Y N The name of the Font face of thegiven style

FontSize Y N The Font Size of the given styleFontColor Y N The name of the Font Color of the

given style

FontStyle Y N The name of the Font Style of thegiven style (i.e., bold, italics, plain)

4.2.1 Common Customizations

There are two common customizations that apply to StyleMaps:

Customization Purpose How To

Modifying style

definition of anapplication style for agiven LogicalDevice.

To make a given

application stylelook differentdepending on agiven LogicalDevice.

Locate the correct StyleSet for thegiven Logical Device from theDeviceInfo.xml file.

Find the above StyleSetinformation from theStyleMap.xml file.

If the definition of the applicationstyle you wish to modify exists inthe StyleSet, then modify it asdesired (that is change the fontface, font size, font color, or font

style).

Otherwise, this application styledefinition is inherited from anotherStyleSet. In this case, you should addthe style in the StyleSet, and define itas desired.

Note: If you modify the inherited

13

8/13/2019 MSSA1159

14/22

definition, you will modify the styledefinition for all Logical Devices

inheriting the parent StyleSetit ishighly recommended that you avoid

doing this.

Creating a newStyleSet for a

Logical Device.

To make a givenLogical Device

have differentstyle definitions.

Locate the existing StyleSet whichmost closely resembles the styledefinitions you would like to havefor the given Logical Device.

Create a new StyleSet that inheritsthe style definitions from theStyleSet above.

Modify whichever applicationstyle definitions that should differon the Logical Device at hand.

Specify the StyleSet for the given

Logical Device as the newly

created StyleSet

4.3

The element helps the renderers for a given Logical Device renderapplication colors into markup language, as described above in the LogicalDevice section. Application colors are colors defined by the MSSA framework toensure consistency across all applications. For example, all background colorswill be grey across all pocket PC devices.

For a given Logical Device, this application color is mapped to a color codewhich can be modified by the system administrator to produce the optimal

rendering. For example, if the Logical Device PDA is bound to the ColorSetdefault and the system administrator changes the background color in the defaultColorSet so that it is grey rather than white, this will affect all applications on

client devices in the PDA Logical Device groupingtheir background color willbe grey instead of white.

A ColorMap consists of multiple ColorSets, each style set has the followingproperties:

PropertyName

Required? Multiple?

Description

Name Y N The name of the ColorSet

Inherits Y N What ColorSet it inherits. Often theadministrator simply wants to change asingle application color between twoLogical Devices. In this case, he maydefine a single color set which has all ofthe color definitions for the first LogicalDevice. It will inherit this first ColorSet

14

8/13/2019 MSSA1159

15/22

in the second ColorSet, and onlyoverwrite the colors that are differentbetween the ColorSets.

Color Y Y An element that defines a color

(described in further detail below)

A ColorSet consists of multiple Colors. Each Color has the following properties:

Property

Name

Required? Multiple

?

Description

Name Y N The name of the Style

ColorDesc Y N The 24-bit color code of the givencolor (i.e., White = #FFFFFF)

4.3.1 Common Customizations

Similar to the StyleMap, there are two common customizations for ColorMaps:

Customization Purpose How To

Modifying the colordefinition of anapplication color fora given LogicalDevice.

To make a givenapplicationcolor lookdifferentdepending on agiven LogicalDevice.

Locate the correct ColorSet for thegiven Logical Device from theDeviceInfo.xml file.

Find the above ColorSetinformation from theColorMap.xml file.

If the definition of the application

color you wish to modify exists inthe ColorSet, then modify it asdesired (i.e., change theColorDesc).

Otherwise, this application colordefinition is inherited from anotherColorSet. In this case, you should addthe color in the ColorSet, and define itas desired.

Note: If you modify the inheriteddefinition, you will modify the colordefinition for all Logical Devices

inheriting the parent ColorSetit ishighly recommended that you avoiddoing this.

Creating a newColorSet for a

To make a givenLogical Device

Locate the existing ColorSet whichmost closely resembles the color

15

8/13/2019 MSSA1159

16/22

Logical Device have different

color definition.definitions you would like to havefor the given Logical Device.

Create a new ColorSet that inheritsthe color definitions from the

ColorSet above.

Modify whichever applicationcolor definitions that should differ

on the Logical Device at hand.

Specify the ColorSet for the givenLogical Device as this newlycreated ColorSet.

16

8/13/2019 MSSA1159

17/22

5Troubleshooting

Q: System log file is not created.

A: First make sure that JServ has been configured properly. If the Self-ServiceFramework has been properly installed and configured, this should be fine. If thisis working properly, then check the jserv.log file in the log directory. Thereshould be an error message describing what is wrong with your currentconfiguration. The directory specified for logging may not be writeable or it maynot exist.

Q: ApacheJServ complains that it cannot find

oracle.apps.mwa.wap.engine.WapServlet

A: Verify that apps.zip is in the classpath.

Q: The system log file says that the AOL/J pool cannot be created

A: Verify the dbc folder is valid and the name of the .dbc file is a valid .dbc filewithin that folder. Also, make sure the Apps database is running.

Q: The system log indicates that the server came up properly, however, you

get a HTTP 404 error when trying to connect.

A: Verify that you have specified the mount point using the ApJServMountproperty for the framework zone in the jserv.conf file.

Q: Images do not appear on PDAs.

A: Verify an alias has been created in the httpd.conf file.

Q: The jserv.log file has an error specifying it cannot find the [$MWA_TOP]

directory.

A: Verify that you have specified the following in the zone.properties file:servlet.start.initArgs=oracle.apps.mwa=[$MWA_TOP]

( where start is the alias given to the servlet )

17

8/13/2019 MSSA1159

18/22

B

Server Manager

This chapter contains the following sections:

Accessing the Server Manager

Monitor Server

Logical Device Manager

Configure Server

B.1 Accessing the Server Manager

The Server Manager for Mobile Self-Service Applications (MSSA) has threemain functions: monitor server, configure server, and Logical Device manager. Itprovides a web-based graphical interface for monitoring and configuring theMSSA Server.

To access the Server Manager:

Login to Self-Service Web applications as a user with the MWA ServerManager responsibility.

Select MWA Server Manager from the Self-Service Section.

You are then presented with six server manager links, including three for theMobile Self-Service Applications Server: Monitor Server, Device Manager andConfigure.

B.2 Monitor Server

The "Monitor Server" page displays detailed information about the MSSA Server,which includes status information and detailed information about current activesessions. The following is a screen shot of this page.

This page has two tablesthe first table summarizes the status information aboutthe MSSA Server which includes server up time, total number of requests servedsince startup, total number of sessions, and total number of active sessions. Thesecond table shows detailed information about each current active session. Itdisplays the session ID, session user name, creation time, and last access time.

18

8/13/2019 MSSA1159

19/22

The table also contains a column titled "Terminate" which provides links toterminate the corresponding session. To terminate a session, click on the icon inthe "Terminate" column of the corresponding session row. This will lead to aconfirmation page. The confirmation page lists the detailed information about thesession you are going to terminate. Click the "Terminate" button to actually endthe session; alternatively, click "Cancel" to discard the operation.

Click the "Refresh" button near the bottom of the page to refresh the informationon this page.

B.3 Logical Device Manager

Mobile Self-Service Applications stores Logical Device information in XMLformat. Administrators can edit the deviceinfo.xml files in the[$MWA_TOP]/admin directory to register User Agent strings for existing LogicalDevices or create new Logical Devices. The server manager tool provides a set ofweb-based graphical user interface for the Logical Device management. Besidesease of use, it also eliminates the grammar errors in the XML file that hand

editing may introduce.To use the Logical Device management tools, either select "Device Manager"from the server manager home page, or click the "Self Service" tab on otherserver manager pages, and then click the "Device Manager" link.

The first page of the device manager will present a table that summarizes existingLogical Devices, and all User Agent strings that are registered to those devices.The following is a screen shot of the page.

To register a new User Agent string, click the "Add User Agent" button at thebottom of the page and to display the next page.

On the page shown above, enter the new User Agent string in the edit box. In the"Device Type" drop down list, select an appropriate device type that you want toregister. If you cannot find an appropriate device type, then select one that isclosest to the one you want to use. You will now be able to change the settingsand create your own Logical Device. Click "Submit" to proceed to the next step.

On the "Device Information" page, you can view and modify all attributeinformation about the Logical Device you selected on the previous page. If you

change the device name, a new Logical Device will be created. The attributes of aLogical Device include the description of the physical dimensions, such as screen

height, maximum display rows, and so forth. They also contain rendering specificcharacteristics, such as color display, email support, and style sets. The mostimportant information is the "Renderer Manager" attribute which selects therenderer manager java class. If you selected an XML renderer manager, then theXSL style sheet must be specified in the "XSL File Name" edit box. You should

19

8/13/2019 MSSA1159

20/22

put the XSL file in a directory under [$MWA_TOP] and specify it asdir/filename. For example, "admin/myxsl.xsl".

See Section 4 of this manual, for a detailed explanation of the meaning of eachLogical Device attribute.

Click the "Submit" button to submit your changes. The "Device Summary" pageis displayed. It includes a table that summarizes the Logical Device that you have

updated or created.

When you click "Submit", the device manager will update your deviceconfiguration file with the new information. The XSL style sheet is parsed tocheck if there are grammar errors. Upon completion, a message page is displayedwhich will indicate if the update was successful or not. Click the "OK" button onthe message page to return to the beginning of the Device Manager.

To be able to update the device configuration or other configuration, the apacheuser needs to have write permission to the directory (usually[$MWA_TOP]/admin where those configuration files are located.

B.4 Configure Server

The "Configure" page allows the user to modify properties in the mwa.cfg file. Toget to the page, either select the "Configure" link from the Server Manager homepage, or click the "Self Service" tab on any other Server Manager page, and thenclick the "Configure" link.

The "Configure" page is divided into the following three regions:

The "Mobile Self-Service Applications" region allows you to view and modifysome major attributes that affect the Mobile Self-Service Applications Server,

such as the default user name and password..

The "Log" region allows you to change the logging behavior of the server,including the log level, log file path, and log file name.

The "Database" region allows you to view the contents of .dbc files. This regionis Read Only because users should not change the .dbc files. Select the .dbcfile name from the "DBC file" list, and click "View" to view the content of theselected .dbc file.

After making your changes, press the "Save" button to save the change to yourmwa.cfg file. Please make sure that the file and directory that contain the file are

writeable to the Apache user. Press "Cancel" to discard the changes.

20

8/13/2019 MSSA1159

21/22

CDeployment Options

This chapter contains the following sections:

Deploying MSSA Server on the De-Militarized Zone (DMZ)

Deploying MSSA Server outside the firewall

Wireless Local Area Network (LAN)

C.1 Deploying MSSA Server on De-Militarized Zone (DMZ)

DMZ is a "neutral zone" between the corporate intranet and internet. Bothexternal and internal users can access servers on the DMZ, however it preventsdirect access between internal and external computers.

This deployment option utilizes the DMZ concept for deploying mobileapplications:

Since Oracle Apps Instance (Database Node) stores crucial information and it is

accessed by both mobile and other clients (Forms, web, etc.), the database node

should reside inside the firewall. However, the MSSA Server has to be accessibleby the Mobile Gateway (e.g., WAP (Wireless Application Protocol) Gateway).For this reason, it has to be placed on the DMZ. It can also be placed outside thefirewall but putting it on DMZ is a safer option.

In this configuration, an exterior router should be modified to allow HTTP trafficfrom outside to the MSSA Server on DMZ, on a given port. This means theAccess List (ACL) of the exterior router has to be changed to allow connectionsfrom any machine on the Internet to only access MSSA Server using port 80.

It is good practice to add an extra layer of security by using Oracle ConnectionManager. This product is shipped with Oracle 8/8i/9i Enterprise Edition and it canbe used to proxy Net 8 traffic in both directions. It also is capable of adding extrafiltering options at the Net 8 level on top of router filtering. Since the OracleConnection Manager would act like a proxy, .dbc files on the MSSA Server haveto point to the Oracle Connection Manager instead of pointing directly to the DBNode. Also, Oracle Connection Manager should be configured to forward Net 8requests received from the MSSA Server to the DB Node.

Access Lists (ACL) of the interior router should also be modified to allow Net 8traffic between Oracle Connection Manager on the DMZ to the DB Node on the

21

8/13/2019 MSSA1159

22/22

internal network on given ports (which are specified in .dbc files, and OracleConnection Managers configuration files).

It is relatively hard to deploy this configuration because you must configure two

routers, setup an extra machine on DMZ, and morehowever, it is safe comparedto other options.

C.2 Deploying MSSA Server outside the firewallThis option may be useful if there is no DMZ. In this case, .dbc files on theMSSA Server must be modified to point to the Oracle Apps Instance inside thefirewall, and the firewall access list must be modified to allow connections fromthe MSSA Server on the given Net 8 port to the Oracle Apps Instance.

C.3 Wireless LAN

The access-point based topology is the common choice for building Wireless

LANs. An access point is a basic device that connects wireless devices to theLANs or wireless backbone. Using this topology, wireless clients cancommunicate with any other wireless/wired client.

22