Installation Guide for Oracle Self-Service E-Billing > Configuring IBM WebSphere > Process of Configuring the IBM WebSphere Application Server for the Billing and Payment J2EE Application >

Modifying the Configuration XMA File for the Billing and Payment Application

Follow these steps to modify the configuration for the notification mail server.

This task is a step in Process of Configuring the IBM WebSphere Application Server for the Billing and Payment J2EE Application.

To modify the configuration XMA file for the Billing and Payment application

1. Open the notification.xma.xml file, found in the EDX_HOME/xma/config/com/edocs/common/notification folder (or the EDX_HOME\xma\config\com\edocs\common\notification folder on Windows). In the path, EDX_HOME is the location where Oracle Self-Service E-Billing is installed.
2. Find the bean ID in the TrueTransporterBean. Modify the mail server properties to point to your company mail server:

   "mail.host: Fully qualified IP address or name of a host running the SMTP which can be used to send email.

   "mail.transport.protocol: Specifies the default message transport protocol.

3. If your company mail server requires mail account authentication, set the following properties. If not, set the mail.smtp.auth property to false, or remove the three properties:

   "mail.smtp.auth: If true, attempt to authenticate the user. Need set a mail account registered in your mail server.

   "mail.user: If mail.smtp.auth is true, set the user name to use when connecting to the mail server.

   "mail.password: If mail.smtp.auth is true, set the user password to use when connecting to the mail server.

4. If your company mail server requires SSL connection, set the mail.smtp.socketFactory.class property. If not, then remove the property:

   "mail.smtp.socketFactory.class: If set, specifies the name of a class that implements the javax.net.SocketFactory interface. This class will be used to create SMTP sockets. For SSL connection, please set to javax.net.ssl.SSLSocketFactory

   Example of a TrueTransporterBean:

   <bean id="TrueTransporterBean" class="com.edocs.common.notification.extensions.TrueTransporter" scope="singleton">

   <property name="template">

   <ref bean="XSLTemplateBean"/>

   </property>

   <property name="mailProperties">

   <props>

   <!-- For non authentication mail server

   <prop key="mail.host">mail.oracle.com</prop>

   <prop key="mail.transport.protocol">SMTP</prop>

   -->

   <prop key="mail.host">mailserver.mycompany.com</prop>

   <prop key="mail.transport.protocol">SMTP</prop>

   <!-- For requiring authentication mail server -->

   <prop key="mail.smtp.auth">true</prop>

   <prop key="mail.user"> emailaccount@mycompany.com </prop>

   <prop key="mail.password"> emailAccountPassword </prop>

   !-- For SSL connection mail server-->

   <prop key="mail.smtp.socketFactory.class">javax.net.ssl.SSLSocketFactory</prop><prop key="mail.smtp.socketFactory.port">465</prop>

   </props>

   </property>

   </bean>

5. If your company mail server does not use the SMTP default port 25, set the mail.smtp.socketFactory.port property, indicating which port to use with the specified socket factory.
6. If your company mail server requires an SSL connection, follow Exporting and Linking the PayPal Payflow Pro Certificate (AIX Only) to install your mail server certification into IBM WebSphere.
7. If your mail server has properties not shown in the default properties list, see Administration Guide for Oracle Self-Service E-Billing and Implementation Guide for Oracle Self-Service E-Billing for details.

The following procedure describes how to modify the configuration in the globalConfig.xma.xml file.

To modify the configuration in the globalConfig.xma.xml file

1. Open the globalConfig.xma.xml file, found in the EDX_HOME/xma/config/modules folder (or the EDX_HOME\xma\config\modules directory on Windows).
2. Find the bean ID called globalConfig. Modify the properties.

   Property	Value
   ebillingHostName	The correct server name or IP address where the Billing and Payment application is deployed.
   csrHostName	The correct server name or IP address where the Customer Service Representative application is deployed.
   ebillingApplicationName	The Billing and Payment application name.
   csrApplicationName	The Customer Service Representative application name.
   ebillingHttpPort	The Billing and Payment application HTTP port.
   ebillingSSLPort	The Billing and Payment application SSL port.
   csrhttpPort	The Customer Service Representative application HTTP port.
   csrSSLPort	The Customer Service Representative application SSL port.

   For example:

   <beans>

   <bean id="globalConfig" class="com.edocs.common.configuration.core.GlobalConfig" scope="singleton">

   <property name="encryptAccountNumbers"><value>true</value></property>

   <!-- default value -->

   <property name="ebillingHostName"><value>sdcbd80a036</value></property>

   <property name="csrHostName"><value>sdcbd80a036</value></property>

   <property name="ebillingApplicationName"><value>ebilling</value></property>

   <property name="csrApplicationName"><value>ebillingcsr</value></property>

   <property name="ebillingHttpPort"><value>9083</value></property>

   <property name="ebillingSSLPort"><value>9443</value></property>

   <property name="csrhttpPort"><value>9084</value></property>

   <property name="csrSSLPort"><value>9444</value></property>

   </bean>

   </beans>