iPlanet BillerXpert 4.6 Consolidator Edition Release Notes

Version 4.6

These release notes contain important information available at the time of the 4.6 release of iPlanet BillerXpert 4.6 Consolidator Edition. New features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using iPlanet BillerXpert 4.6 Consolidator Edition.

An electronic version of these release notes can be found at the iPlanet documentation web site: http://docs.sun.com/. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

These release notes contain the following sections:

• What's New in BillerXpert Consolidator Edition, Version 4.6
• Known Problems and Limitations
• How to Report Problems
• For More Information

What's New in BillerXpert Consolidator Edition, Version 4.6

---

New Technical Features

iPlanet BillerXpert 4.6 is the next version of iPlanet BillerXpert Consolidator Edition. Built on the iPlanet E-Commerce-Ready Infrastructure, iPlanet BillerXpert Consolidator Edition provides high performance, scalability, high availability, and integration with expertise applications and systems.

The following are new features for iPlanet BillerXpert 4.6 Consolidator Edition:

• Certification to Oracle 8.1.7, Enterprise and Standard editions
• Certified to Oracle 9i, Enterprise and Standard editions. See Limitations section for additional information.
• Certification to iPanet Application Server (iAS) version 6.5
• Certification to iPlanet Web Server (iWS) version 6.0
• Certification to LDAP version 5.0
• Multiple BSP Support

• Configured in the BXOFXSIGNON Oracle table

BillerXpert Consolidator Edition is the OFX client in relation to Billing Services. As an OFX client, the BXCE must submit username/password to the OFX Server (i.e. BillerXpert direct). This username/password is stored in the BXOFXSIGNON table. One can view the contents as:

SQL> desc bxofxsignon;

Name	Null?	Type
OFXUSERID	NOT NULL	VARCHAR2 (128)
PASSWORD	NOT NULL	VARCHAR2 (128)
BILLERNAME	NOT NULL	VARCHAR2 (128)
FID	NOT NULL	VARCHAR2 (128)
ORGID	NOT NULL	VARCHAR2 (128)

SQL>

To add a BSP name/password, use the insert command:

SQL> insert into BXOFXSIGNON values ( `OFXuser'. `password', billerid', `fid', `org' ) ;




---

Note

If SignOn for a biller is not in this table, the SignOn info in $CSX_HOME/java/csxpert.conf will be used for billing service. The SignOn for CMD line program, e.g. findBiller, does not use this table. It uses the SignOn info in $CSX_HOME/java/csxpert.conf The SignOn for OFX payment client does not come from this table. It is configured from CSP Admin GUI.

---




• Conversion of NAS proprietory AppLogic/HTML Template components to J2EE components:

1. Conversion of all AppLogic classes into Java Servlets with a one-to-one mapping.

2. Conversion of all HTML templates to JSP pages with a one-to-one mapping.

3. JavaBean components now carry dynamic data from the Servlets to the JSPs. These replace the existing TemplateData and TemplateDataMap classes.

Implementation

All servlets will extend from the following Base Class: CSXBaseServlet. This class will provide the following methods as described in Table 1:

Table 1    CSXBaseServlet base class methods 

public void init(ServletConfig cfg)	Servlet initialization method. This will be called by iAS when the servlet is loaded for the first time. This method simply stores a reference to the ServletContext in an instance lvariable called context
protected void init(HttpServletRequest request, HttpServletResponse response)	This method will be called first by the doGet() and doPost() methods. This saves the request and response objects into instance variables, and also instantiates a new BXStatus object which will be used during this request
protected boolean init(int whichContext, HttpServletRequest request, HttpServletResponse response)	This method will be called by Servlets that require to use any of the XXXContext objects. Many ejbs require the context objects to be passed as parameters for their constructors. The whichContext variable may contain one of the following constants:
	CSXBaseServlet.BILLING_CONTEXT	new CSXBillingContext is instantiated
	CSXBaseServlet.MEMBERSHIP_CONTEXT	new CSXMembershipContext is instantiated
	CSXBaseServlet.PAYMENT_CONTEXT	new CSXPaymentContext is instantiated
	CSXBaseServlet.ALL_CONTEXT	All of the above are instantiated
protected void releaseBXDBContext()	Releases all of the above contexts, if they have been instantiated
protected CSXSession getSessionProxy()	Returns reference to the CSXSession object that stores session data. The CSXSession object itself is stored in the HttpSession. This method creates the session if it does not already exist (by calling the getSession() method)
protected CSXSession getCSXSession()	Extracts the CSXSession object from the HttpSession and stores it in an instance variable. It creates the session if it does not already exist (by calling the createCSXSession(String onlineName) method)
protected CSXSession createCSXSession(String OnlineName)	Creates a new CSXSession object and places it in the HttpSession
public boolean verifyUserSession(HttpServletRequest req)	Checks if the HttpSession and CSXSession are valid. Returns true if valid and false if not. To be called at the beginning of every servlet request, except for signon.
public void displayTemplate(String template)	Forwards the current request to the JSP page named by the "template" parameter
protected void displayErrorMsg(String templateFile)	Forwards the current request to the JSP page. Also processes error messages present in the BXStatus object, so that they appear in the output page.
public boolean logActivity(String act, String billerID,String userID)	Logs an activity in the audit trail. Called by servlets that need to make an entry into the activity log.
public void displaySessionTimeout()	Redirects the user to the login screen. Called by servlets that detect that the Session is invalid

JavaBean objects will be used to carry dynamic data from the Servlets to the JSP pages. These Beans will be populated by the servlet and saved as a request attribute. The request will then be forwarded to the JSP. The JSP can retrieve the Bean from the request attribute, and format it for display.

All JavaBeans will extend the base class CSXBaseBean, which provides convenience methods for formatting data for the user's locale.

Table 2 lists existing applogics and the corresponding servlet:

Table 2    Applogic to Servlet Conversion 

Table 3 lists the existing HTML templates and the corresponding JSP pages:

Table 3    HTML Template to JSP Page Conversion 

Known Problems and Limitations

---

iPlanet BillerXpert Consolidator Edition includes the following limitations and considerations:

Additional Requirements for Oracle 9i:

When using Oracle 9i as the database server, the following parameters must be added in the /etc/system file. The parameters are:

• seminfo_semmls=1024
• seminfo_semopm=100
• seminfo_semvmx=32767

Problem [4676865]

Events are dependent on the Application Server start time. For example: In the Admin console, events can be setup at one hour intervals. After setup, events are triggered on the hour as scheduled. However, if the Application Server is restarted, the scheduled events trigger one hour after the App Server restart time. In essence, events trigger on the hour (1pm, 2pm, etc.) after the App Server restart, for example 1:30pm, then events will now be triggered at 2:30pm, 3:30pm, etc.

How to Report Problems

---

If you have problems with iPlanet BillerXpert, contact iPlanet customer support using one of the following mechanisms:

• iPlanet online support web site at http://www.sun.com/service/sunone/software/index.html

From this location, the CaseTracker and CaseView tools are available for logging problems.

• The telephone dispatch number associated with your maintenance contract

So that we can best assist you in resolving problems, please have the following information available when you contact support:

• Description of the problem, including the situation where the problem occurs and its impact on your operation
• Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
• Detailed steps on the methods you have used to reproduce the problem
• Any error logs or core dumps

For More Information

---

Useful iPlanet information can be found at the following Internet locations:

• Other BillerXpert Consolidator Edition Documentation —

http://docs.sun.com/coll/S1_ecomm_ce46

• Software Products Information —

http://www.sun.com/software/

• Sun ONE Documentation —

http://docs.sun.com/

• Support Services & Knowledge Base —

http://www.sun.com/service/sunone/software/index.html

• Consulting and Professional Services Information —

http://www.sun.com/service/sunps/sunone/index.html

• Developer Information —

http://developer.iplanet.com/

• Software Training —

http://www.sun.com/software/training/