| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel eService Administration Guide Addendum for Industry Applications > Administering Siebel eBanking and Siebel eBrokerage > Siebel Account Aggregation >
Installing and Configuring Account Aggregation
There are several required installation steps to integrate the Siebel application with Yodlee Account Aggregation services. The setup procedures differ depending on the Siebel AAG Solution being used.
Non-Siebel Software Installation (For Datafeed Solution Only)
These tasks describe how to configure the Siebel Account Aggregation Datafeed Solution with Yodlee's SDK service. These instructions assume that Siebel eFinance, Siebel eBanking, Siebel eBrokerage, or Siebel eCustomer for Financial Services have already been installed.
Installation of Java JDK and Yodlee SDK
This section is a guide to the installation of required Yodlee and third-party components. This software should be installed on each physical Siebel Server supporting Account Aggregation.
NOTE: Users are advised to refer to the Yodlee SDK Installation Procedure document for more information on all required software and installation procedures.
Before installing Siebel Account Aggregation components, the customer must first purchase Account Aggregation services from Yodlee, Inc.
The administrator must obtain Yodlee's version 1.5.2 SDK (Software Development Kit) and third-party software as required by the Yodlee SDK, including the Xerces XML Parser, Java Secure Socket Extension (JSSE), and IBM SOAP. Please refer to the Yodlee SDK Installation Procedure documentation for information on how to obtain this software.
The administrator must obtain a valid set of login parameters from Yodlee. This includes a Cobrand ID, Cobrand Password, and a key file. For the data solution, the administrator must obtain a URL for the datafeed connection.
Installation of Java Runtime Environment
The Java Runtime Environment (JRE) must be installed. The Java Runtime Environment is a component of the Java 2 Platform, Standard Edition, version 1.3 or higher.
NOTE: For information on how to obtain the Java Runtime Environment, see the Yodlee SDK Installation Procedure document.
The installation will copy the Java Virtual Machine (JVM) library.
NOTE: In NT, use jvm.dll. In Solaris, use libjvm.so. In AIX, use libjvm.a. Copy the file to a local directory (such as c:\Program_Files\JavaSoft\JRE\1.3\bin\hotspot\jvm.dll). Record this location for future reference.
The installation program will also save a set of JDK classes in a directory such as C:\Program Files\JavaSoft\JRE\1.3\lib. Record this location for future reference.
Installation of Yodlee and Third-Party Software
This software, all packaged in the form of .jar files, will not ship with the Siebel software CD. Please refer to Yodlee SDK Installation Procedure documentation or contact Yodlee, Inc. for information on obtaining this software and other preparatory steps for your environment.
There are three packages to be installed: Xerces XML Parser, Yodlee, and Java Secure Socket Extension (JSSE).
Installation involves copying these three files to each Siebel Server (there is no installation program to run). Record the locations for future reference.
Table 16 lists the installation items and sample locations.
To implement JSSE, you must modify the java.security file, which is usually found in the security subdirectory of the Java library directory. In the file's List of providers and their preference orders section, please add the line security.provider.3, as shown:
security.provider.1=sun.security.provider.Sunsecurity.provider.2=com.sun.rsajca.Providersecurity.provider.3=com.sun.net.ssl.internal.ssl.ProviderThe first two lines are listed by default, and the last one needs to be added.
Set the Operating System Classpath Environment Variable
The Operating System Classpath environment variable should be set to include the Java files installed in the previous steps. In Windows NT/Windows 2000, you can use the Control Panel > System program to set the Classpath, which is an environment variable. Append these paths to the end of your existing Classpath. For example, an addition to the NT Classpath would be
;D:\Yodlee\lib\Yodlee.jar...Figure 3 displays a sample System Properties dialog box.
NOTE: Use a semicolon to separate classpaths, and do not put spaces between paths.
Copy the Yodlee Key File into the Siebsrvr/bin Directory
Rename the key file
aag.txt. These keys expire periodically. When all the keys in your key file have expired, Siebel eBanking will no longer be able to access the Yodlee server.Siebel Software Installation Tasks (For Datafeed Solution Only)
This next section is a guide to the setup changes that must be made to the Siebel software.
- The Customer Application URLs (finsebanking, finsebrokerage, finsecustomer) should be set to include the installation's domain name.
- The Siebel Server should be started.
- The path to the Java Virtual Machine must be specified in the Siebel application configuration files (such as fins.cfg, finsebanking.cfg, finsebrokerage.cfg, finsecustomer.cfg). In the [AccountAggregationUpdate] section, append the JavaVMPath to include the path to your JVM files.
- For Windows NT/Windows 2000 set JavaVMPath = $YOUR_JAVA_INSTALLATION_PATH\...\jvm.dll
- For AIX: JavaVMPath = $YOUR_JAVA_INSTALLATION_PATH\...\libjvm.a
- For Solaris: JavaVMPath = $YOUR_JAVA_INSTALLATION_PATH\...\libjvm.so
Administrators should not change other values unless instructed to do so by Siebel Systems.
- Stop and restart the Siebel Server.
Software Installation (For Hosted Solution Only)
These tasks describe how to configure the Siebel Account Aggregation Hosted Solution. These instructions assume that Siebel eFinance, Siebel eBanking, Siebel eCustomer for Financial Services, or Siebel eBrokerage have already been installed.
- The administrator must obtain a valid set of login parameters from Yodlee, Inc. This includes a Cobrand ID, Cobrand Password, and a key file. For the hosted solution, the administrator must obtain a URL setup by Yodlee for its CCW integrated sign-on service (make sure that this URL is on the same domain as your Siebel Server).
- Copy the Yodlee key file into the siebsrvr/bin directory and rename it
aag.txt. These keys expire periodically. When all the keys in your key file have expired, Siebel eBanking will no longer be able to access the Yodlee server.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel eService Administration Guide Addendum for Industry Applications, Version 7.5, Rev. A Published: 18 April 2003 |
