Installation Guide

SAP Biller Direct

3.0

Document Version 1.00 May, 2004

Based on
mySAP Financials Accounts Receivable Accounting (FI-AR) /
Accounts Receivable and Payable (FI-CA)

SAP Biller Direct 3.0 Installation Guide

May 2004

Copyright
Copyright 2004 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,
OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM
Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World
Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product
specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP Biller Direct 3.0 Installation Guide

May 2004

Icons in Body Text

Icon

Meaning
Caution
Example
Note
Recommendation
Syntax

Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help General Information
Classes and Information Classes for Business Information Warehouse on the first page of any
version of SAP Library.

Typographic Conventions
Type Style

Description

Example text

Words or characters quoted from the screen. These include field

names, screen titles, pushbuttons labels, menu names, menu paths,
and menu options.
Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT

Technical names of system objects. These include report names,

program names, transaction codes, table names, and key concepts of a
programming language when they are surrounded by body text, for
example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their
paths, messages, names of variables and parameters, source text, and
names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.

<Example text>

Variable user entry. Angle brackets indicate that you replace these
words and characters with appropriate entries to make entries in the
system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

SAP Biller Direct 3.0 Installation Guide

May 2004

Installation of SAP Biller Direct 3.0..................................................................................... 5

Introduction................................................................................................................... 5
Installation Procedure Step by Step ............................................................................. 6
Planning the Installation................................................................................................. 7
Preparing the Necessary Documentation..................................................................... 7
Scheduling the Necessary Software ............................................................................ 8
Preparations ................................................................................................................10
System Settings in Contract Accounts Receivable and Payable (FI-CA) .......................10
Making System Settings in Accounts Receivable Accounting .......................................11
Installation ...................................................................................................................12
Installing the SAP J2EE Engine .................................................................................12
Starting the SAP J2EE Engine ...................................................................................13
Deployment ..............................................................................................................13
Starting SAP Biller Direct...........................................................................................15
Testing the Installation ..................................................................................................15
Troubleshooting ...........................................................................................................15

SAP Biller Direct 3.0 Installation Guide

May 2004

Installation of SAP Biller Direct 3.0

SAP Biller Direct is a J2EE-based Web application that you can use to present customer
accounts in your Internet portal. It enables your customers to pay bills online, and also enter
inquiries and complaints online. SAP Biller Direct prepares the accounting data for display on
the Web and also forwards data entered by your customers on the Web to the SAP R/3
system.
So that your customer is able to use the Web application, you have to use one of the following
browsers, and also enable Javascript and Cookies:

Microsoft Internet Explorer Version 5.5

Microsoft Internet Explorer Version 6.0

Netscape Communicator Version 7.00

Netscape Communicator Version 7.01

Netscape Communicator Version 7.02

Mozilla Version 1.6

Customers who have a suitable browser and use the Biller Direct service can log on via the
Web server with their user ID and password and then carry out the functions described under
SAP Biller Direct User Modes in the configuration guide.

Introduction
In the following you are given an introduction to installing the application SAP Biller Direct on
Windows and UNIX platforms. The description covers all steps and settings that are
absolutely essential for operating the application and that result in the standard configuration
of the application SAP Biller Direct. For more detailed information see the configuration guide
and the modification guide.
Providing a biller is using accounts receivable accounting or contract accounts receivable and
payable as back end, the component SAP Biller Direct can be used to:

Present bills, credits, and payments to the billers customers in the Internet

Inform customers of new bills and credits electronically (such as by SMS or e-mail)

The component SAP Biller Direct enables your customers to:

Pay open receivables online by credit card or bank transfer, or offset them against
credits

Contact you in writing via the Internet

The customer can either log on to the customer portal direct with his ID and password, or
access it via a hyperlink sent to him by e-mail (see Electronic Notification of Customers in the
configuration guide) and then enter his user and password there.
The customer can then display any open bills, for example. If an optical archive has been
connected in the SAP R/3 back end, bills from the optical archive are displayed. You can find
a detailed description of the bill display in the configuration guide in the sections Displaying
Bills, Credits, and Payments and Displaying Bill Details. If a customer pays a bill, it receives
the status In Process. If the bill has been paid the status changes to Processed. For detailed
information on this see the configuration guide sections Payment of Bills in Balance Mode and
Payment of Bills in Standard Mode.

SAP Biller Direct 3.0 Installation Guide

May 2004

Notes for the Implementation

SAP Biller Direct is part of the Electronic Bill Presentment and Payment process that you can
alternatively use with Accounts Receivable Accounting (FI-AR) or Contract Accounts
Receivable and Payable (FI-CA).
Before you commence with the installation, read the SAP Notes given in the
section Preparing the Necessary Documentation [Seite 7] . They contain the
latest information about the installation, including any revisions to the installation
documentation. Make sure that you are reading the latest version of the SAP
Notes. You can find the SAP Notes in the SAP Service Marketplace
(http:\\ service.sap.com/notes) or via the SAPNet R/3 front end.
To ensure the transfer of data between the Web application and SAP R/3 system is secure
SAP strongly recommends you:

Install Secure Socket Layers (SSL, HTTPS) on the SAP J2EE Engine in addition.

Use Secure Network Communications (SNC). You can find detailed information on
using SNC in SAP Service Marketplace under the Internet address
service.sap.com/security in the navigation bar on the right of the screen
under Security in Detail Secure System Management:

SNC Users Guide

Cookbook: Configuring SNC for the AGate/SAP System Connect

SAP recommends that you operate SAP Biller Direct with SSL encryption under HTTPS. For
more information on SSL encryption visit the SAP Help Portal under SAP NetWeaver
SAPWeb Application Server (6.30) SAP NetWeaver Components J2EE-Technology in
SAP Web Application Server Administration Manual Installation Information PostInstallation Procedures.

Installation Procedure Step by Step

Use
You can use the following tables as checklists when you install the system and make the
individual steps.
The tables contain all the required steps planning, preparation and installation.
You can use the links to obtain a description of the individual steps and additional information
designed to help you execute the activities.

Process Flow
The following is the recommended procedure for the installation:
...

1. Print the following tables.

2. Work through the individual activities in the order described.

If a step is required for your installation, the link for this step will take you to the
relevant unit.

Carry out the procedure as described there.

Once you have successfully carried out the activity, cross off the corresponding
entry in your printout. This will enable you to follow the progress of your
installation.

Continue with the remaining steps in the list.

SAP Biller Direct 3.0 Installation Guide

May 2004

Planning
Careful planning is the prerequisite for a successful installation.
!

Activity
Preparing the Necessary Documentation [Seite 7]
Scheduling the Necessary Software [Seite 8]

Preparation
Before you install SAP Biller Direct, carry out the following activities:
!

Activity
System Settings in Contract Accounts Receivable and Payable [Seite 10]
Making System Settings in Accounts Receivable Accounting [Seite 11]

Installation
The following table describes the installation procedure.
!

Activity
Installing the SAP J2EE Engine [Seite 12]
Starting the SAP J2EE Engine [Seite 13]
Deployment [Seite 13]

Planning the Installation

Before you commence the installation of SAP Biller Direct, make sure you have met the
requirements that are described in the following units.

Preparing the Necessary Documentation

Before commencing the installation, read the following SAP Notes. They contain the latest
information about the installation, including any revisions to the installation documentation.
You can find the SAP Notes in the SAP Service Marketplace under
http:\\service.sap.com/notes.
List of related SAP Notes
SAP Note
Number

Title

Relevant for

713534

SAP Biller Direct 3.0: Installation

(component FI-AR)

Accounts Receivable Accounting

713536

SAP Biller Direct 3.0: Installation

(component FI-CA)

Contract Accounts Receivable and Payable

713540

SAP Biller Direct 3.0 Installation

Note (JAVA component)

Accounts Receivable Accounting,

Contract Accounts Receivable and Payable

SAP Biller Direct 3.0 Installation Guide

May 2004

You can find information about the following areas on the SAP Service Marketplace.
Description

Internet Address

Title

SAP Notes

service.sap.com/notes

See above

Security

service.sap.com/security

SNC Users Guide

Cookbook:
Configuring SNC for
the AGate/SAP
System Connect

Scheduling the Necessary Software

A prerequisite for installing SAP Biller Direct is that you have already installed FI-CA as part
of the following listed Industry Business Solutions, or you have installed FI-AR.
Required Software
If you are using FI-AR, the following software components are required:
SAP R/3 4.6C

PI 2004_1 for 4.6C

SAP Web AS 6.40

SAP Biller Direct 3.0

(Java front end for
SAP Web AS 6.40)

R/3 Enterprise

PI 2004_1 for R/3

Enterprise

SAP Web AS 6.40

SAP Biller Direct 3.0

(Java front end for
SAP Web AS 6.40)

ERP

PI 2004_1 as a
component of ERP

SAP Web AS 6.40 as

a component of ERP

SAP Biller Direct 3.0

(Java front end for
SAP Web AS 6.40) as
a component of ERP

If you are using FI-CA, the following software components are required:
SAP R/3 4.6C

R/3 Enterprise

FI-CA Industry Release 4.64

for the following solutions:

mySAP Insurance

mySAP Utilities

mySAP
Telecommunications

mySAP Media

mySAP Public Sector

(Public Sector FI-CA)

SAP Contract
Accounts Receivable
and Payable (FI-CA)

FI-CA Industry Release 4.71

for the following solutions:

mySAP Insurance

mySAP Utilities

SAP Web AS
6.40

SAP Biller Direct 3.0

(Java front end for
SAP Web AS 6.40)

SAP Web AS
6.40

SAP Biller Direct 3.0

(Java front end for
SAP Web AS 6.40)

SAP Biller Direct 3.0 Installation Guide

R/3 Enterprise

mySAP
Telecommunications

mySAP Media

mySAP Public Sector

(Public Sector FI-CA)

SAP Contract
Accounts Receivable
and Payable (FI-CA)

FI-CA Industry Release 4.72

for the following solutions:

mySAP Insurance

mySAP Utilities

mySAP
Telecommunications

mySAP Media

mySAP Public Sector

(Public Sector FI-CA)

SAP Contract
Accounts Receivable
and Payable (FI-CA)

May 2004

SAP Web AS
6.40

SAP Biller Direct 3.0

(Java front end for
SAP Web AS 6.40)

You install contract accounts receivable and payable using transaction SAINT. The
transaction has documentation to help you with this. If you do not use SAINT for the
installation, you can find the corresponding installation guide on the software CD in the DOCU
directory. The SAP Notes relevant for installing FI-CA can be found in the following composite
SAP Notes.

Industry Solution

SAP Notes

Title

mySAP Utilities

91097

Overview: Notes on the R/3

Add-on IS -U/CCS

mySAP Telecommunications

99514

Overview: Notes on the R/3

Add-on IS -T

mySAP Public Sector

217192

Overview: Notes on the R/3

Add-on IS -PS-CA

mySAP Media

125559

Overview: Notes on the R/3

Add-on IS -M

mySAP Insurance

100103

Overview: Notes for SAP

Insurance

SAP Contract Accounts

Receivable and Payable

439897

Overview: Notes on R/3 AddOn component FI-CAX

SAP Biller Direct 3.0 Installation Guide

May 2004

Preparations
To achieve an operational installation of SAP Biller Direct:
...

1. Make the required system settings in the back-end system you are using.
2. Meet the technical prerequisites for installing the Web application.
3. Start the J2EE Engine.

System Settings in Contract Accounts Receivable and

Payable (FI-CA)
Before you can start installing SAP Biller Direct, you have to make the following settings in FICA.
Define the Application Area
The application area is contained in the delivery as the standard setting. If there is no
application area in the clients you use for SAP Biller Direct or it is not active, or you have
defined several application areas, you must enter one active application area (see Basic
Functions Application Area).
Define Payment Methods
Create separate payment methods for SAP Biller Direct (for example, for payments by credit
card or automatic debit/bank collection), since the identification of an item with this payment
method affects further processing. Assign these payment methods to a company code. In the
field SAP Biller Direct Payment Method, enter EBPP/Web. This enables the system to
recognize that it is dealing with payment transactions for a Web application. If you also want
to process outgoing payments with SAP Biller Direct you must create separate payment
methods for this because each payment method can only be used as an incoming payment
method or an outgoing payment method (for example, paying out a credit that a Web user
would like to arrange using a credit card). To ensure you define the payment methods
completely, make the following entries in the Implementation Guide (IMG) for FI-CA:

Payment methods per country (see Business Transactions Payments

Incoming/Outgoing Payment Creation Define Payment methods)

Define specifications for the company code (see Business Transactions Payments
Incoming/Outgoing Payment Creation Define Specifications for Responsible
Company Code)

Create Contact Classes and Contact Actions for Customer Contacts

To be able to store and process inquiries, complaints, and reasons why you have made a
partial payment for a bill - customer contacts - you have to define contact classes and related
contact actions (see Implementation Guide for Contract Accounts Receivable and Payable
Configuration of Contract Accounts Receivable and Payable Management of Customer
Contacts). The system settings you need to make for this are in the Implementation Guide for
FI-CA under Basic Functions Customer Contacts and Customer Portal in the Internet
Settings for Customer Portal on the Internet (Release 4.64), or Integration Financial Supply
Chain Management Biller Direct Settings for the Customer Portal on the Internet
(Release 4.71).
Specifications for Handling Payments and Credit Memos
The settings in the following activities of the Implementation Guide for Contract Accounts
Receivable and Payable under Integration Financial Supply Chain Management Biller
Direct are mandatory even if you do not use these functions:

Define Default Values for the Settlement of Credits

10

SAP Biller Direct 3.0 Installation Guide

Define Specifications for Overpayments

Define Clearing Account for Overpayments

May 2004

Create a Number Range for Recording the Activities of Web Users

Create interval 01 for number range object EBPP_EVENT. To do this, in the SAP Easy Access
Menu choose Tools ABAP Workbench Development Other Tools Number Ranges.
For a detailed description of all settings for the logging function, see the configuration guide
under Logging User Activities.
Create Users for SAP Biller Direct in FI-CA
Create the following user master records as described in the configuration guide under User
Management in Contract Accounts Receivable and Payable:

One or more reference user master records as the carrier of the authorization
information

a pool user master record

You have to maintain the data for this pool user master record later with Extended
Configuration Management (XCM) for the Web application.

a user master record for each Web user

You only need this user master record if you have configured the SAP User
Management Engine (UME) of the Web AS 6.40 so that the SAP R/3 system is used as
the central user management.
Assign a reference user to this user master record in accordance with the
authorizations you wish to grant, and reference a business partner in the user master
record (see SAP Easy Access menu under Administration User Maintenance
Users, and once in the transaction choose Goto References).
You should also consult the sections on user management in the configuration guide
under User Management, and under Business Customizing Configuration of the
Web Application Configuring the Web application with the XCM Defining Data for
User Management, and also the documentation for the component UserManagement in
XCM.

Making System Settings in Accounts Receivable

Accounting
Procedure
Define Payment Methods
Create payment methods for SAP Biller Direct as described in the configuration guide in the
section Defining Payment Methods.
To ensure you define the payment methods completely, make the following entries in the
Implementation Guide (IMG) for FI-AR:

Payment methods per country (Financial Accounting Accounts Receivable and

Accounts Payable Business Transactions Incoming Payments Automatic
Incoming Payments Payment Method/Bank Selection for Payment Program Set
Up Payment Methods per Country for Payment Transactions)

Payment methods per company code (Financial Accounting Accounts Receivable

and Accounts Payable Business Transactions Incoming Payments Automatic
Incoming Payments Payment Method/Bank Selection for Payment Program Set
Up Payment Methods per Company Code for Payment Transactions)

11

SAP Biller Direct 3.0 Installation Guide

May 2004

Assign payment methods (Financial Accounting Accounts Receivable and Accounts

Payable Financial Supply Chain Management Biller Direct Edit Payment
Methods).

Create and Assign Text IDs

To be able to store and edit inquiries, complaints, and reasons for partial payments on bills,
you define and assign text IDs as described in the configuration guide in the section Creating
and Assigning Text IDs.
The system settings you need to make for this can be found in the Implementation Guide
under Financial Accounting Accounts Receivable and Accounts Payable Financial
Supply Chain Management Biller Direct Assign Text ID.
Create a Number Range for Recording the Activities of Web Users
Create interval 01 for number range object EBPP_EVENT. To do this, in the SAP Easy Access
Menu, choose Tools ABAP Workbench Development Other Tools Number
Ranges. You can find a comprehensive description of all the possible settings for logging in
the section Logging the Activities of Web Users in the configuration guide (see Business
Customizing Configuration of Accounts Receivable Accounting Implementing Additional
Functions).
Create Users for SAP Biller Direct in Accounts Receivable Accounting
Create the following user master records as described in the configuration guide under User
Management in Accounts Receivable Accounting:

One or more reference user master records as the carrier of the authorization
information

a pool user master record

You have to maintain the data for this pool user master record later with Extended
Configuration Management (XCM) for the Web application.

a user master record for each Web user

You only need this user master record if you have configured the SAP User
Management Engine (UME) of the Web AS 6.40 so that the SAP R/3 system is used
as the central user management.
Assign a reference user to this user master record in accordance with the
authorizations you wish to grant, and reference a customer in the user master record
(see SAP Easy Access menu under Administration User Maintenance Users, and
once in the transaction choose Goto References).
You should also consult the sections on user management in the configuration guide
under User Management, and under Business Customizing Configuration of the
Web Application Configuring the Web application with the XCM Defining Data for
User Management, and also the documentation for the component UserManagement in
XCM.

Installation
SAP Biller Direct runs on the SAP J2EE Server. Data exchange between SAP Biller Direct
and the accounting system is made real time by Remote Function Call (RFC) using the SAP
Java Connector (JCo).

Installing the SAP J2EE Engine

...

1. Install the SAP Web Application Server 6.40 as described in the installation guide. The
current version of the installation guide for the SAP Web Application Server 6.40 can
be found under the Internet address service.sap.com/instguides in the SAP

12

SAP Biller Direct 3.0 Installation Guide

May 2004

Service Marketplace under SAP Net Weaver in Detail Solution Life-Cycle

Management Installation Installation & Upgrade Guides SAP Components
SAP Web Application Server Release 6.40 and higher. Select there the relevant
installation guide for the platform and database that you are using.
2. The only prerequisite for operating SAP Biller Direct 3.0 is the system variant SAP Web
AS J2EE System (without ABAP Engine) that is described in the SAP Web Application
Server 6.40 installation guide.
3. For a relatively straightforward installation, in which all the required components for the
J2EE system are installed centrally on a computer, choose the installation option SAP
Web AS 6.40 J2EE system (J2EE only) MAXDB SAP Web AS 6.40 J2EE system
(Central System) CustomInstallation: Web AS 6.40 for <databasesystem> (Central
System) and follow the instructions relating to this in the installation guide.
4. When the installation is complete, execute the activities described in the guide under
Post-Installation Activities, such as the start and stop of the J2EE Engine test and the
installation of the SAP license.

Starting the SAP J2EE Engine

...

1. Start the SAP Management Console.

On the left-hand side of the screen the SAP Management Console displays a node for
the SAP system in the tree structure, for example C11.
2. Place the cursor on this node and choose Start using the right mouse button. When
you do this, the database, central service and J2EE instance are started.

Deployment
...

1. To deploy the configured SAP Biller Direct application on the SAP J2EE Engine, first
ensure that the SDM server has been started. If this is not the case, switch to directory
<Directory>:\usr\sap\<SAPSID>\JC<instancenumber>\SDM\program (for
example, C:\usr\sap\C11\JC00\SDM\program) and execute StartServer.
2. Start the SDM Remote GUI by executing RemoteGui in the same directory as
StartServer.
3. A window for the GUI of the Software Deployment Manager is displayed. Choose the
Connect to SDM Server icon, and in the window which then appears enter the
password for logging on to the SDM server. The initial password supplied by the
system is sdm.
4. Once you have successfully logged on, a window with the tab page SDM Repository,
Deployment and Log Viewer is displayed. Change to the tab page SDM Repository,
and choose the icon Deployment Parameter Substitutions.
5.

Choose the icon Add Public Substitutions variables.

6. Insert the new substitution variable com.sap.fin.scenario . If you do not enter

a value for this substitution variable, SAP Biller Direct is started with the standard
scenario. If a scenario is required, enter the scenario name here.
7. Change to the tab page Deployment and choose the icon Add SCA/SWC/SDA to
Deployment List.
8. In the next window, choose the file FSCMBD<nn>.SCA.
9. Continue the deployment by confirming each of the following steps with NEXT.

13

SAP Biller Direct 3.0 Installation Guide

May 2004

10.

Once you have reached the last page, choose Start and start the deployment of the
application SAP Biller Direct on the SAP J2EE Engine entered.

11.

The steps carried out in connection with the deployment are logged in the log file
defaultTrace.trc of the J2EE Engine. You can display this log file with the SAP
J2EE Engine Administrator. Start the SAP J2EE Engine Administrator as follows:
a. Choose
<Drive>:\usr\sap\<SAPSID>\JC<instancenumber>\j2ee\admin (for
example C:\usr\sap\C11\JC00\j2ee\admin) and execute go.
b. A window for the GUI of the SAP J2EE Engine Administrator is displayed. Here,
select your administrator and choose Connect. The password is identical to the
administrator password that you entered during the installation.
c. Navigate to the LogViewer. Choose Server Services LogViewer to do this.
In the right hand side of the screen you will find the file default.trc in the
folder Server .\log. You can view the trace by double-clicking on this file. For
detailed information on the LogViewer see the J2EE Engine 6.40
documentation.

12.

Exit the deployment of SAP Biller Direct by choosing CONFIRM.

Repeated Deployment
If you want to deploy the file FSCMBD<nn>.SCA repeatedly following the initial deployment,
you have to make the following additional entries after step 5 (see above):
...

1. Choose Show Deployment Configuration after selecting file FSCMBD<nn>.SCA on the

tab page Deployment in the lower right-hand part of the window (Deployment
Configuration).
2. Select the button Update deployed SCAs/SDAs that have the same or lower
component versions than the selected SCAs/SDAs on the following subwindow shown,
in the area Settings for Updating SCAs/SDAs. The entry is not required for the first
deployment.
3. Continue the deployment by confirming each of the following steps with the button
Next.
4. Once you have reached the last page, choose Start and start the deployment of the
application SAP Biller Direct on the SAP J2EE Engine entered.
5. The steps carried out in connection with the deployment are logged in the log file
defaultTrace.trc of the J2EE Engine. You can display this log file with the SAP
J2EE Engine Administrator. Start the SAP J2EE Engine Administrator as follows:
a. Choose
<Drive>:\usr\sap\<SAPSID>\JC<instancenumber>\j2ee\admin (for
example C:\usr\sap\C11\JC00\j2ee\admin) and execute go.
b. A window for the GUI of the SAP J2EE Engine Administrator is displayed. Here,
select your administrator and choose Connect. The password is identical to the
administrator password that you entered during the installation.
c. Navigate to the LogViewer. Choose Server Services LogViewer to do this.
In the right hand side of the screen you will find the file default.trc in the
folder Server .\log. You can view the trace by double-clicking on this file. For
detailed information on the LogViewer see the J2EE Engine 6.40
documentation.
6. Exit the deployment of SAP Biller Direct by choosing CONFIRM.
7. Exit the SDM Remote GUI by choosing GUI Exit in the Software Deployment Manager
menu.

14

SAP Biller Direct 3.0 Installation Guide

May 2004

Starting SAP Biller Direct

SAP Biller Direct is started following the first deployment. Error messages are issued telling
you that you must configure at least one scenario with Extended Configuration Management
(XCM) before you can use SAP Biller Direct. To configure a scenario, call up XCM by entering
the path [protocol]://[server]:[port]/[billerdirect-contextroot]/admin/xcm/init.do in your browser.
Enter http://localhost:50000/bd/admin/xcm/init.do in your browser.
When you call up the XCM you will require authentication. The application has been
configured in such a way that you can log on with every J2EE Engine administrator, meaning
with every user in the administrator group. For additional information on authorized users for
calling up the XCM, see the Security Guide.
Detailed information on the configuration can be found in the Configuration Guide in the
section Configuring the Web Application, and in the online XCM documentation.

Testing the Installation

Through the deployment SAP Biller Direct is transported to the server and started. You can
now call up the Web application in the browser with http://Server name/context name. You
can choose one of the following variants as the start URL for calling up the application from
your portal:

File

Layout

frameset_top_html.jsp

Company logo, portal menu, application

menu

frameset_application_html.jsp

Application menu with menu bar

frameset_stand_alone_html.jsp

Application menu with tab pages

To test the installation, start a browser, such as the Internet Explorer, and enter the URL of
your SAP Biller Direct application (for example http://<server>/bd)

Troubleshooting
If errors occur during the installation, you have to analyze them and then rectify them.
If no error messages are generated when you deploy the application but you are still unable
to call it up, check files output.log and error.log of the J2EE Engine for any
corresponding error messages when starting the application. You can find these log files in
directory
<Drive>:\usr\sap\<SAPSID>\JC<instancenumber>\j2ee\cluster\server0\log
\console_logs.

15