This section describes configuration settings needed for:
M-Business Anywhere server and client communication
M-Business Anywhere and Unwired Accelerator integration
Make configuration changes in the following files:
global.properties.xml – see “Configuring global.properties.xml”.
server.xml – see “Configuring server.xml”.
If you installed the M-Business Anywhere server and
Unwired Accelerator on different machines, modify the following
files:
gridlayout1.jsp – see “Configuring gridlayout.jsp”.
server.xml – see “Configuring server.xml”.
If you installed M-Business Anywhere server on a different
machine than Unwired Accelerator, change the localhost
alias
in gridlayout1.jsp to the machine name on which
the M-Business Anywhere server was installed.
In a text editor, open the gridlayout1.jsp file (located in the %SYBASE%/UA65/tomcat/webapps/onepage/portlets/templates/ mobile directory).
Search for: String MS_ROOT_URL = "http://localhost:8091"
Replace localhost
with
the name of the M-Business Anywhere server name and port. This is
not required if M-Business Anywhere and Unwired Accelerator are
installed on the same machine.
Save and close the file.
Database PODs are installed once you modify this file. PODs
are binary files compiled from C code to access the Client Extension
API. PODs are installed automatically during installation, and enable
you to run applications even when the mobile devices are not connected
to the server.
For more POD information, see Administrator Guide for M-Business Server (located at http://hostname:8091/enterprise_doc/Admin_MBiz.pdf, where hostname is the machine on which the M-Business Anywhere server is installed).
This section describes settings in the global.properties.xml file used to integrate M-Business Anywhere and Mobile Web Studio. The settings include:
MB.Enabled – enables connection from Mobile Web Studio to the M-Business Anywhere database, AGDB.
MB.AutoRegistration – determines how user accounts are handled between Mobile Web Studio and M-Business Anywhere. See “Self-registration” for information.
alwaysValidateSession – enables personal channels to work properly on mobile devices.
Modifying the global.properties.xml file
In a text editor, open global.properties.xml (located in %SYBASE%\UA65\tomcat\webapps\onepage\config).
Search the file for: <Property
name="MB.Enabled"
.
By default, MB.Enabled is set to false. Set it to true as shown below to enable M-Business Anywhere integration with Portal Interface and Mobile Web Studio. You must also set the AGDB connection information in the server.xml file, as described in “Configuring server.xml”.
<PropertyGroup name="MBusinessGroup" descripton= "properties for configuring M-Business Server in the Portal and Studio."> <Property name="MB.Enabled" value="true" description="(true/false) true to enable MBusinessintegration Portal and Studio. false to disable it." menugroup="10"/> </PropertyGroup>
Change the value if necessary.
Search the file for: <Property
name="MB.AutoRegistration"
.
By default, MB.AutoRegistration is set to false as shown:
<Property name="MB.AutoRegistration"
value="false" description="(true/false)
true to enable auto MBusiness user registration when a user is created
in EP. false to disable it." menugroup="10" />
Change the value if necessary, using information about the MB.AutoRegistration parameter in “Self-registration”.
Search the file for: <Property
name="alwaysValidateSession".
By default, alwaysValidateSession is set to true. For personal channels to work properly on a mobile device or Portal Interface, make sure alwaysValidateSession is set to false. Otherwise, you see a message similar to “Your submission has been recorded and will be sent during the next Synchronization” when you try to access an application on the PDA or mobile device.
Change the value if necessary.
Save the file and close it.
The global.properties.xml property, MB.AutoRegistration, determines how user accounts are handled when Unwired Accelerator and M-Business Anywhere are integrated.
If MB.AutoRegistration is set to true, when a user joins the Portal Interface, or a user is added to Mobile Web Studio, the user automatically joins the M-Business Anywhere server with the same user name and password.
If MB.AutoRegistration is set to false, Mobile Web Studio does not self-register to M-Business Anywhere. The Studio Admin user can register a Mobile Web Studio user in M-Business Anywhere using M-Business | User/Roles, and selecting “Create M-Business user.”
If a Mobile Web Studio user already exists, but does not have an account in M-Business Anywhere, the M-Business Anywhere administrator can create an account for the user, or the Mobile Web Studio user can self-register in M-Business server or in Mobile Web Studio.
The user names in Mobile Web Studio and M-Business Anywhere
server must match. If you create a user in M-Business Anywhere,
an account is not created for the user in Mobile Web Studio.
Set the JDBC connection from Mobile Web Studio to the AGDB database in server.xml. JDBC connections to these databases are also established in this file:
portaldatabase
sampledb
mpharma
msales
Configuring the server.xml file
In a text editor, open server.xml (located in %SYBASE%\UA65\tomcat\conf).
Search for "jdbc/agdb
(including
the quotation mark).
Review the defaults or set the correct values for these parameters:
url – typically, you do not modify the JDBC connection URL for the M-Business Anywhere database (AGDB). M-Business server uses port 8099, and the default URL is:
jdbc:sybase:Tds:localhost:8099</value>
If you installed the M-Business Anywhere server on a
machine other than Unwired Accelerator, modify the JDBC connection
URL. Change
localhost
to
the name of the machine on which the M-Business Anywhere server
was installed.
username – enter the AGDB user name. The default is “dba”.
password – enter the AGDB user password. The default is “SQL”.
maxActive – enter the maximum number of connections. The default is 20.
maxWait – enter the maximum wait period. The default is 20000.
removeAbandoned – indicate whether to remove abandoned connections. The default is false.
logAbandoned – indicate whether to log abandoned connections. The default is false.
These are the default parameters in server.xml:
<ResourceParams name="jdbc/agdb"> <parameter> <name>driverClassName</name> <value>com.sybase.jdbc2.jdbc.SybDriver</value> </parameter> <parameter> <name>url</name> <value>jdbc:sybase:Tds:localhost:8099</value> </parameter> <parameter> <name>username</name> <value>dba</value> </parameter> <parameter> <name>password</name> <value>SQL</value> </parameter> <parameter> <name>maxActive</name> <value>20</value> </parameter> <parameter> <name>maxIdle</name> <value>10</value> </parameter> <parameter> <name>maxWait</name> <value>20000</value> </parameter> <parameter> <name>removeAbandoned</name> <value>false</value> </parameter> <parameter> <name>removeAbandonedTimeout</name> <value>60</value> </parameter> <parameter> <name>logAbandoned</name> <value>false</value> </parameter> </ResourceParams>
Save the file and close it.
Copyright © 2005. Sybase Inc. All rights reserved. |
![]() |