Sei sulla pagina 1di 23
Treasury Package - Upgrade Guide TRP January 2014 V.1.0 (2014-03-22)

Treasury Package - Upgrade Guide TRP January 2014

V.1.0 (2014-03-22)

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 Table of Contents Part 1 – Preconditions and

Table of Contents

Part 1 Preconditions and Hints

 

4

TWA and Internet Explorer 8

4

Application Logfiles

4

 

4

Part 2 Step by Step Upgrade

 

6

Treasury Package

6

Dealware

6

Versions related to TRP October ____________________________________________________________

6

New Version ____________________________________________________________________________

7

Mercury

7

7

7

New Version ____________________________________________________________________________

8

Web Application ___________________________________________________________________________

8

Versions related to TRP October ____________________________________________________________

8

New Version ____________________________________________________________________________

9

Integration

 

9

Twister

for

Customware.Classic

9

Twister for Customware.Net

 

9

Versions related to TRP October ____________________________________________________________

9

Twister Manager

 

10

Versions related to TRP October ___________________________________________________________

10

TPFeed

10

Deprecated RPCs

 

10

TAFeed

11

Infoware

 

11

Part 3 Tool

Inventory

13

Production Tools

 

13

 

13

13

13

15

16

18

CancConfTicket

 

18

CsvAccountEntry

19

DeleteOrphanedBundles

19

 

2

|

P

a g e

Financial Applications

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 MergeSingleFPA 19 Setup 19 AllowSingleExposureAceReg 19 ClearAllTwisterSysLogEntries 19

MergeSingleFPA

19

Setup

19

AllowSingleExposureAceReg

19

ClearAllTwisterSysLogEntries

19

ClearTwisterNonImportedSysLogEntries

19

Colors

20

DealwareSpanishHelpForRel4033 __________________________________________________________

20

DwDeleteQuipuUsers

20

20

20

20

20

EnableLocalSwiftCreateForRel42x

21

FixDWClientExit

21

SetExpirationDateTo30

21

SetupPwd

21

21

SetPasswordPolicyTo41xStandard

21

Change Control

22

Related Documents

23

Financial Applications

3

|

P

a g e

Upgrade Guide Treasury Package TRP Jan 2014

Part 1 Preconditions and Hints

Upgrade Guide Treasury Package – TRP Jan 2014 Part 1 – Preconditions and Hints

This section was covered previously by the Frequently Asked Questions section and the DevOps/Infrastructure chapter of the Release Notes. It will contain also implications for other Quipu Modules/Applications, if relevant.

TWA and Internet Explorer 8

In several Banks, still workstations using Windows XP are in use. The newer versions of Internet Explorer

(9, 10) cannot be used on these workstations. The “Treasury Web App” (previously called “Webforms”) is

NOT compatible with Internet Explorer 8. Please, keep in mind to use Google Chrome or Mozilla Firefox

on WindowsXP machines, if necessary.

Application Logfiles

Since Dealware 4.1.x we are keeping 100 application logfiles, as especially during testing periods the storage of only 6 logfiles was considered not to be enough. All but the last one are stored in a zipped

format (Dealware.log, Dealware.log.001.zip

Dealware.log.100.zip); the location they are stored is e.g.

.. C:\Users\inga\AppData\Roaming\DealWare\Logfiles. Please, keep this is mind also for the description of problematic situations on Help Desk Tickets, sometimes it helps a lot having logfiles available for

analysis.

Working with different Versions

It is frequently complicated for IT to maintain an older version in the Production Environment and to keep more or less updated a newer version on the Test Environment. Different Treasury Release Packages are based on different Dealware Database Structures and different Parametrisation, related to a specific DealwareSQL.exe version. Going from an older Version to a newer Version is easy, there is a prepared

Upgrade File; but going from a newer Version (e.g. the one currently installed in the Test Environment) to an older Version (e.g. the one from a Backup of the Production Environment, to be installed in Test

Environment and updated afterward to the Newer Version), can lead to problems, therefore, let’s go

with an example, and some recommendations:

Use cmd.exe to execute any commands from the shell; Microsoft PS does not work with some Quipu command line tools, especially DWBatch-based tools (as most of the

“maintenance files” are)

Suppose you do have a DealwareSQL V.13.26 used in Test, and a DealwareSQL V. 13.07 used in Production. For an update of the Test Environment (bringing current data from Production) you will need both versions, therefore we recommend you to rename them into DealwareSQL_1307.exe resp. DealwareSQL_1326.exe. The DealwareSQL version is shown when you type “DealwareSQL h”.

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014  You may need to adapt the login

You may need to adapt the login and password for the access of DealwareSQL to the one configured in the quipu login of the SQL Server, via usage of setuppwd.exe

You may need to adapt the database directory to be used by DealwareSQL. Here an example using the directory D:\Dealware\Database:

DealwareSQL setdir:D\Dealware\Database

(please refer also to the Installation Guide). When the command run for the first time, the subdirectories \Export and \Archive are created under this location. All backups should then be extracted into the \Export directory (cleaning up the contents first), when recreating a database. When making a backup, by default, the compressed backup file will be located inside \Archive and the single data files will be located in \Export.

For the given example, DealwareSQL_1307.exe and DealwareSQL_1326.exe need to be located inside the defined directory, in this case in D:\Dealware\Database

Locate the backup from Production Environment (including 1307 in the file name) inside D:\Dealware\Database\Export and extract there.

Drop the V.13.26 database currently existing in the Test Environment:

DealwareSQL_1326 s<YourServerInstance> -d<YourDatabase> -drop

Recreate the V.13.07 database in the Test Environment:

DealwareSQL_1307 -s<YourServerInstance> -d<YourDatabase> -recreate

Upgrade the restored backup to the New Version:

UpgradeForRel421 -s<YourServerInstance> -d<YourDatabase>

Financial Applications

5

|

P

a g e

Upgrade Guide Treasury Package TRP Jan 2014

Part 2 Step by Step Upgrade

Upgrade Guide Treasury Package – TRP Jan 2014 Part 2 – Step by Step Upgrade

Treasury Package

The official announcement of TRP October 2013 was made on November 16 th , 2013, and contained Dealware.exe 4.2.4.4, UpdateForRel424.exe, DealwareSQL.exe 13.44, Mercury 2.0.1 and Treasury Web Application 2.1.7.

The official announcement for TRP January 2014 is being made March 21 st , 2014, containing Dealware.exe 4.3.4, UpdateForRel434.exe, DealwareSQL.exe 14.12, Mercury 2.1.2 and Treasury Web Application 2.2.0.

Dealware

Versions related to TRP October

As part of the official announcement of TRP Oct 2013, Dealware4244.exe (2013-11-08) has been

published at ftp.quipugmbh.com/Quipu Software/Dealware/Releases/TRP2013-October, for the changes done between August 26 and November 08. The corresponding Database maintenance tool is DealwareSQL.exe V.13.44 (2013-11-02). For the upgrade of the version-to-version upgrade, UpgradeForRel424.exe (2013-11-08) was prepared. Version characteristics:

DATAVERSION 4.24 (parametrisation) and DBVERSION (database structure) 13.44.

A major update including database changes was made in relationship to User Login Names containing non-ASCII characters, for Windows 7 and Windows 8 (but no development was made to fix this issue under Windows XP). Dealware V.4.2.5 (2013-11-27), UpgradeForRel425.exe (2013-12-02), and DealwareSQL 13.48 (2013-11-27).

Several bugfixes and features prepared for the TRP January were “down-programmed” for DW series 4.2.x: Accrued interests for Loans and Bonds in “Accounting Balances” (V.4.2.5.3 Jan 28); wrong calculation of the initial balance in “Account Statement”, if checkbox ‘include agreed ones’ marked, and if there entries in status agreed between last closed day and initial balance

date (V.4.2.5.3 Jan 28); several bugs and some features on “Product-specific Exposure” (V.4.2.3.5, V. 4.2.5.1 Dec 05, V.4.2.5.2 Dec 28, V.4.2.5.3 Jan 28, V.4.2.5.6 Feb 28); a bug related to Ticket Printouts for Loan Tickets without principal component (V.4.2.5.3 Jan 28); a problem related to the storage of DealTicket attachments on paths with non-ASCII-7bit characters (V.4.2.5.4 Jan 29); correct calculation of accrued interests for “unadjusted interest” in “Accounting Balances (V.4.2.5.4 Jan 29); generation of MT200 removed, generation of MT300 improved (V.4.2.5.5 Feb 01); accrued interests for MM included in “Accounting Balances” (V.4.2.5.6 Feb 28)

Upgrade Guide Treasury Package TRP Jan 2014

New Version

Upgrade Guide Treasury Package – TRP Jan 2014 New Version In order to install the Dealware

In order to install the Dealware part of the Treasury Release Package January, you need to have your

database upgraded to 4.25 and DealwareSQL 13.48 in used (you may detect the version by using DealwareSQL h). If you do have a different situation, please get in contact with your Regional Office for clarification and support.

Run the Upgrade stopping Twister and Twister Server and running then UpgradeForRel434

s<YourServerInstance> -d<YourDatabase>, replace the DealwareSQL from inside your

\Dealware\Database with the new one from inside DealwareSQLForRel434.zip (Version 14.12, 2014-03-

18), update the Stored Procedures via DealwareSQL -s<YourServerInstance> -spcreate,

update all client machines accessing this database by replacing the Dealware.exe file with the new Dealware434.exe and proceed with the update of Mercury, Twister and Twister Server.

For interested DBAs: Starting with DealwareSQL version 13.52, the Database Maintenance Tool returns a

reliable return code: 0 (no error) or 1 (error). Based on this, instructions like “if errorlevel 1” can be used

by DBAs. For all previous DealwareSQL versions, the usage of the return codes does not make sense at all.

Mercury

The name “Mercury” stands for a standardized and secured way to register data into and to retrieve

data from Dealware database via webservices (XML-RPC over SSL in Python). These web services are being used by specialized Clients (e.g. for the registration of official exchange rates) as well as by other

Quipu applications (Infoware, Bankware, Customware.Net, and several applications used at Group Level). Also the communication between the Treasury Web Application (formerly “Webforms”) and the Dealware Database are based on Mercury Webservices.

FAQ: Stopping Mercury

Mercury is a console application, not an event driven framework or a system service. If Mercury is closed

in some non-standard way (like simply closing the console window or with control-break or kill by task manager), Mercury is immediately suspended by the Operating System, and cannot clean things up. If this happens by mistake, Mercury can be unlocked by using “mercurySrv –u” (unlock). However, everybody should try to terminate Mercury always in the recommended way, opening a second console in the instances directory and using “mercurySrv –x”. If Mercury is operated using some command line options, a batch called e.g. ‘runDwMercury.cmd’ can be created, with the contents “mercurySrv c mercuryRunDw.cfg %*”; then a Mercury instance can be started with “runDwMercury” and can be terminated with “runDwMercury –x”, and can be unlocked with “runDwMercury –u”.

Versions related to TRP October

As part of the official announcement of TRP Oct 2013, MercurySrv.exe V.2.0.1 (2013-11-14) has been published at ftp.quipugmbh.com/Quipu Software/Mercury/MercuryServer.

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014  Based on an exception related to data

Based on an exception related to data consumed by Infoware (getBondContracts), it was necessary to publish a bugfix version Mercury V.2.0.2 (2013-12-02); in the same version 2.0.2, getOutoingPayments(), used for TPFeed purposes, was changed in order to publish two additional attributes needed for UKR (SourcePartyCode and TargetPartyCode).

New Version

As part of the official announcement of TRP Jan 2014, MercurySrv.exe V.2.1.2 (2014-03-20) has been

published at ftp.quipugmbh.com/Quipu Software/Mercury/MercuryServer. Upgrading of MercuryServer from previous version (V2.0.2, last one related to TRP October 2013):

Stop Mercury server Extract Mercury to a new folder; edit mercury.cfg to be reachable from all hosts; configure the DSN according to your setup The update of the configuration file related to the definition of the reachable/usable RPCs must be done manually and can be done in two ways: Updating of the previously used configuration file (add new items); or taking the new default one and re-do what was opened/changed in the previously used one. You may also ask for support/recommendations by Regional Office, or for tests enable all RPCs in the section [RPC.Dealware]. Typically we have only new RPCs in updates, therefore the previously used config file usually work without any problem, unless new RPC must be enabled. Copy/Replace all the other files and restart Mercury Server.

Web Application

The web application is now called Treasury Web App” (previously: “Webforms”) and has been developed for Trades/Contracts agreed outside the usual online Trading Systems - for the registration, maintenance and monitoring of long-term agreements like Interbank Loans (where it may take quite a time to fix all details until the final agreement is signed) and Bonds.

Versions related to TRP October

As part of the official announcement of TRP Oct 2013, TreasuryWebApp-2.1.7 (2013-11-08) has been published at ftp.quipugmbh.com/Quipu Software/TreasuryWebApp/Releases, including changes done between August 27 and November 08 2013. Some bugfix versions, including also some feature improvements planned for TRP January, have been prepared later: Rounding problems on maturity for T-Bills (TWA V.2.1.7); payments rounded to the number of decimals as defined in DW, e.g. 1 for the case of local currency in ARM (TWA 2.1.8); allowing a change of the “Ending Date” for Loans in the case of pre-payments (TWA 2.1.8); problem opening a traded zero bond (TWA 2.1.9); problem for variable BN-Bonds when updating coupon rates (TWA 2.1.10)

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014  Compatibility: The earliest compatible versions necessary for

Compatibility: The earliest compatible versions necessary for TWA 2.1.9 are: Dealware 4.2.5.4 (with DealwareSql 13.47) and Mercury Server 2.0.2 (TRP October)

New Version

As part of the official announcement of TRP Jan 2014, TreasuryWebApp V.2.2.0 (2014-03-21) has been

published at ftp.quipugmbh.com/Quipu Software/TreasuryWebApp/Releases. This version requires MercurySrv -2.1.2 (final) and DW database upgraded to version 4.34/4.12.

Integration

Twister for Customware.Classic

“Twister” is used for the online import of Cashbox Snapshots and Transactions touching Nostros, Loros, and FX Accounts, for Reconciliation (agreed payments vs. confirmed payments) as well as for the general

Liquidity and Position Monitoring (including impacts of Customer Business on top of Interbank Business).

Last versions related to TRP October: Twister V.5.0.6 (2013-09-24) on the Client side, and TwisterUserSrv V.5.0.1 (2013-01-07) at the Server side.

There is no new version available.

Before the Dealware Database can be upgraded, it is necessary to stop Twister and Twister Server (first StopSvc, then RemoveSvc) and make a backup of the current database (export with existing Database Tool). After the upgrade and after the installation of a new Version of Twister Server and/or Twister Client, for the cases there is a new version available TwisterUserSrv should be started first, and afterward Twister.

Twister for Customware.Net

“Twister” is used for the online import of Cashbox Snapshots and Transactions touching Nostros, Loros, and FX Accounts, for Reconciliation (agreed payments vs. confirmed payments) as well as for the general

Liquidity and Position Monitoring (including impacts of Customer Business on top of Interbank Business).

Versions related to TRP October

Officially announced for TRP October: TwisterCWN V.0.6.7 (2013-09-24) on the Client side, and

TwisterUserSrvCWN V.0.6.3 (2013-07-19) at the Server side.

TwisterCWN

V.0.6.8

and TwisterUserSrvCWN V.0.6.4 (2013-11-18): Storage of

CWN.BusinessProcess.BpExhchangeRate into DW; avoid duplicated records in specific inconsistent test situations; extracting IsOffSiteATM(server side) TwisterCWN V.0.6.9 and TwisterUserSrvCWN V.0.6.5 (2013-11-25): Usage of the new IsOffSiteATM Terminal attribute added in CWN (client side), allowing an identification of the Off-

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 Site ATMs, and the possibility to report separately

Site ATMs, and the possibility to report separately inside Dealware. Installation requires a usage of DeleteCashAccounts.exe and subsequent CreateCashInTransitAccounts.exe TwisterCWN V.0.6.10 and TwisterUserSrvCWN V.0.6.6 (2013-12-02): Fixing a problem with resynchronisation

There is no new version available.

Before the Dealware Database can be upgraded, it is necessary to stop TwisterCWN and TwisterUserSrvCWN and make a backup of the current database (export with existing Database Tool). After the upgrade and after the installation of a new Version of Twister Server and/or TwisterCWN Client (decompressing corresponding rar files reach into its own directory), for the cases there is a new version available – start the UserServer with “TwisterUserTwisterUserSrvCWN.exe” and start the Client with the command “TwisterCWN.exe”.

Twister Manager

TwisterManager can be used for setups related to Twister for Customware.Classic as well as for Customware.Net, but is frequently used also to re-configure settings, e.g. after changing the Dealware Server. In problematic cases, the recommendation is to delete the TwisterSrv instance, and then add it again, ad configure it with the proper authentication mechanism (SQL authentication or Windows

authentication); afterwards, the TwisterSrv instance can be tested with the button “Test ODBC connection” (or similarly named).

Versions related to TRP October

Twister_Manager_GUI V.1.1.1 (2013-06-06) for the installation and maintenance.

There is no new version available.

TPFeed

Treasury

Payment

Feed

is

used

for

the

transfer

of

Settlement Instructions from Dealware to

Customware.Net. There are pilot installation in KOS, ARM, and UKR. An installation requires a deep analysis of the existing parametrisation of the Payment Module (CWN) and is usually done by mixed

(regional & development) teams.

Deprecated RPCs

Initially, TPFeed was established to avoid double manual registration for outgoing payments related to Treasury Tickets. The RPC used for this purposes was getOutgoingPayments(). Now, for specific Implementation Projects, we do have also the possibility to transfer information about Incoming Payments. The automatic registration of Incoming Payments in the Payment Module is used, e.g. if no SWIFT messages exist for these payments, but only an information by eMail or from a Portal. Based on this, a more generic RPC called getPayments() is now used. There is a calling parameter which can be

Financial Applications

10 | P a g e

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 used to restrict the payments to the outgoing

used to restrict the payments to the outgoing payments, giving exactly the same functionality as with getOutgoingPayments(). Starting with TRP April, getOutgoingPayments() will not be any more available.

TAFeed

“Treasury Accounting Feed” is used for the automatisation of Bookings, transfering Treasury related Payables/Receivables into the standard “sixpack” format. There is no single pilot installation finished at

the moment (started in ECU and ROU). An installation requires a deep analysis of the existing bookings in

Bankware, and is usually done by mixed (regional & development) teams.

Infoware

Regarding compatibility of versions,

Infoware 4.3 and later is compatible with Mercury 2.0.2.* (part of the Treasury Release Package October 2013). Older Mercury versions are not anymore supported.

Infoware 4.5.6 and later is compatible with Mercury 2.1.2 (part of Treasury Release Package January 2014). Mercury 2.1.2 has several RPCs which are only compatible with Dealware DataVersion 4.33 or higher (they will simply be un-available if this Mercury Version is used in combination with an older Dealware database). Accrued interests for MM/LN/BN/BO and Custody Accounts are supported in Infoware 4.6.

o Infoware_code_4.6.1+build8545_py27.exe (ROU; correct import of flagged parties from DW, if “PCH Party Code” has been defined in DW, BBK Industry and Business Code - missing before)

In order to enable Infoware in Test Environments, to get data from Dealware:

The etl.ini file need to contain under the section [General] the lines SHOW_MERCURY = True and DEALWARE_BRANCH = XX (where XX designates a DimBranch.BranchId that will be used for the DW contracts. In most of the cases this will be the Head Office branch, for example

DEALWARE_BRANCH = 1)

The etl.ini file need to contain under the section [Mercury] the lines PUBLISHES_DEALWARE = True and url = https://your_Mecury_URL (for the Dealware host and port, example:

url = https://sql-bw2005.quipugmbh.com:7233)

The etl.ini file need to contain under the section [Passwords] the lines MercuryPass =

here_should_be_inserted_password

(e.g.

MercuryPass

=

1fb11c6b1b970a602ac6e894447d6458) The password for Mercury is generated with the special tool MercuryPasswdGen (description included under Part 3 Tool Inventory, Setup Tools).

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014  Edit sysatt.ini file, under section [General] please

Edit sysatt.ini file, under section [General] please add the line SHOW_MERCURY = True. This setting will show the exchange rate interface example Mercury YTD Rates by Currency. The current exchange rate service was made specifically for holding group rates. This setting needs to be set to False if the Bank will not use it. If set to True, the Bank needs to provide the local rate “types” they will like to see in Infoware.

After the three steps of parametrising etl.ini are done, a command line window shod be opened under C:\infoware\scripts and the following command executed: etl SysConfig admin (should be finished with status TRUE) and after that (from same location), setpwd and select 0 in order to check connection to Mercury and other sections (should be with status: ok).

Restart Apache

After all these steps, you should see the following Task: “Treasury/Dealware data, Monthly Dealware data load over Mercury”

Upgrade Guide Treasury Package TRP Jan 2014

Part 3 Tool Inventory

Upgrade Guide Treasury Package – TRP Jan 2014 Part 3 – Tool Inventory

Only the “officially published” tools are listed here. There are also few other tools adapted and delivered on demand, and also some tools in a pilot phase in specific Banks.

Production Tools

MercuryRateImport

MercuryRateImport.exe 1.1.0 (2014-02-04). Can be used for cases where the automatic background rate

import is not existing or problematic. Last changes: Technical update.

MercuryPriceImport

MercuryPriceImport.exe 1.1.0 (2014-02-04). Mercury Client importing Prices from text files (very similar to the case of the RateImports). Last changes: Yield can also be imported in addition to the price if

available, when not only price can be imported skipping the yield information. Sample text file with Yield information:

# MercuryPrice.20130710112032.dat # generated by MercuryPriceImport 1.0.0 (2013-07-10) # generated at 2013-07-10 11:20:32

# -------------- # ISIN Prices Yield # --------------

PublishedBy REUTERS PublishedAt 2012-07-30 14:15:00 ValidFor 2012-08-01 RateKind MarketAsk ZZ0NS2D7 98.5689 1.222 DE000A0N37P3 99.28569 0.9999

QuipuRateImport

MercuryRateImport tools with specific in-compiled configuration files, serving concrete purposes, in most of the cases the purpose is the daily automatic background import of official exchanges rates to

the Dealware database, for use inside Dealware and a publication to interested applications and tools.

For TRP January 2014, a database change has been included allowing to keep also the “Unit” for specific

Exchange Rate Codes; this is to reflect official exchange rates published as e.g. “100 HRK = 25.538697

BAM”). Several Rate Import Tools will be adapted, and also the import of official rates published by

Mercury-on-Dealware into CWN will be adapted soon.

QuipuRateImportForALB

QuipuRateImportForALB 1.2.0 (2014-02-12). Exchange Rate Import. Last Changes: Adaptations related Mercury password, possibility to specify clear text password instead MD5 password. For Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool.

Upgrade Guide Treasury Package TRP Jan 2014

QuipuRateImportForARM

Upgrade Guide Treasury Package – TRP Jan 2014 QuipuRateImportForARM QuipuRateImportForARM 1.2.0 (2014-02-13). Exchange Rate Import. Last

QuipuRateImportForARM 1.2.0 (2014-02-13). Exchange Rate Import. Last Changes: Adaptations related Mercury password, possibility to specify clear text password instead MD5 password. For Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool.

QuipuRateImportForBIH

QuipuRateImportForBIH 1.2.0 (2014-02-12). Exchange Rate Import. Last Changes: Adaptations related Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool.

QuipuRateImportForBOL

QuipuRateImportForBOL 1.1.0 (2014-02-27). Exchange Rate Import. Last Changes: Adaptations related Mercury password, possibility to specify clear text password instead MD5 password. Proxy authentication included. For Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered

together with the tool.

QuipuRateImportForBNR

QuipuRateImportForBNR_V1.0.0 (2014-02-24). Value Date is “publishing date + 1”. Possibility to import Exchange rates for the year 2011, 2012, 2013, 2014. Command line option to specify the year (-y or --

year) to import the rates for the specific year. Mercury password, possibility to specify clear text password instead MD5 password. Proxy authentication included. For Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool.

QuipuRateImportForCOL

QuipuRateImportForCOL 1.0.1 (2014-02-26). Exchange Rate Import. Initial version was V.1.0.0 (2014-01- 16). A proxy is used, means that the proxy and the port need to be declared when running the tool, e.g.

QuipuRateImportForCOL proxy 172.0.10.15:8080. There was a problem related to the firewall

setting of the Server, solved locally.

QuipuRateImportForDEU

QuipuRateImportForDEU 2.2.0 (2014-03-03). Exchange, Interest, and Swap Rate Imports. Last changes:

We have now the following set of files published by Bloomberg on daily basis:

DailyEONIA_2000.csv.YYYYMMDD (Published at 20:00) DailyEURIBOR_1130.csv.YYYYMMDD (Published at 11:30) DailyEURSwap_1230.csv.YYYYMMDD (Published at 12:30) DailyLIBOR_1330.csv.YYYYMMDD (Published at 13:30) DailyUSDSwap_2000.csv.YYYYMMDD (Published at 20:00) DailyFX_1415.csv.YYYYMMDD (Published at 14:15)

And the QuipuRateImport Configuration file contains:

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 For FX Rates: RateStream --> Official:PCH-GROUP and GroupFixing:PCH-GROUP

For FX Rates: RateStream --> Official:PCH-GROUP and GroupFixing:PCH-GROUP

(Publihsed_at=14:15)

For Eonia Rates: RateStream --> Eonia:Bloomberg (published_at=20:00:00) For EuriBor Rates: RateStream --> Euribor:Bloomberg (published_at=11:30:00) For Swap Data rates: RateStream --> Isdafix:Bloomberg (published_at=20:00:00)

As Isdafix:Bloomberg RateStream has rate codes from USDSwap (published at 20:00), EURSwap (Publihsed at 12:30) and USDLibor (Published at 13:30), since 3 files are published at different times, we take the last file's (USDSwap) time 20:00 as published at time in the rate import configuration file.

QuipuRateImportForECB QuipuRateImportForECB V1.2.0 (2014-02-15). Value Date is “publishing date”, last 90 days are imported, if rates are missing. Last changes: Technical update.

QuipuRateImportForECU

QuipuRateImportForECU 1.2.1 (2014-02-26). Exchange Rate Import. Last Changes: Correction needed for Monday Rates; configuration option was missing in V.1.2.0 (2014-02-19, prepared due to a changed

location of the import source).

QuipuRateImportForMKD

QuipuRateImportForMKD 1.2.0 (2014-03-03). Exchange Rate Import. Last Changes: Adaptations related Mercury password, possibility to specify clear text password instead MD5 password. For Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool.

QuipuRateImportForNIC

QuipuRateImportForNIC 1.1.0 (2014-03-04). Exchange Rate Import. Last Changes: Technical update

QuipuRateImportForROU

QuipuRateImportForROU 1.2.0 (2014-01-22). Exchange Rate Import. Last Changes: Adaptations related Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool.

QuipuRateImportForUKR QuipuRateImportForUKR 1.0.0 (2013-12-25). Exchange Rate Import. First version. Out of the sample files received, the decision was to take 16:30 as “Published at time”. When the Rate Import tool is running, it takes the system date and the published at time from configuration file which reflected as the Publication Time (2014-01-13 16:30:00) in Dealware Application. The tool checks if there is any rate defined for the ValueDate (E.g. 2014-01-14) and PublishedAtTime (E.g. 2014-01-13 16:30:00) for each currency before importing, and imports only for the case no rates have been registered up to this moment.

Twister (CWC)

For the handling of all Liquidity (Cashbox snapshot, Nostro transactions) and Currency Position related

transactions, transferring them with some format adaptations - from Customware to Dealware.

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 [Client] Twister version 5.0.6 (2013-09-24). Last changes: Technical

[Client] Twister version 5.0.6 (2013-09-24). Last changes: Technical adaptations required because of changes in the database structure for Deal Accounts; handling of Branch IDs with 3 and more digits. Located at: ftp.quipugmbh.com/Quipu Software/Twister/CWC-DW/Twister. [Server] TwisterUserSrv 5.0.1 (2013-01-07). Last changes: Changed default encoding to utf8 (problems with special characters in Congo); added check for admin rights. Located at ftp.quipugmbh.com/Quipu Software/Twister/CWC-DW/TwisterUserServer. In order that a nostro transaction is recognized by Twister as Treasury related, and imported as such, it

is necessary to register the Deal ID in one of the reason fields (“reason1”, “reason2”, “reason3”) in the

dialog in CWC; where the DealID need to have the following format: "^(\w\w)[\s\_\-]?\d\d\d+", means:

2 characters corresponding to a valid DW trade type, then optionally one space or underscore or minus, followed but at least three digits, e.g. FX-1234, MM50000, CH 80033, LN_70003.

Parametrisation notes:

For the case certain transitory accounts are used instead of nostros in Customware.Classic, they need to be added to the table CO_BANK and be linked to the specific Contract Code used in Dealware and Bankware, in order to give the full liquidity picture.

Includes a configuration files which allows e.g. recodification of Currency Codes (e.g. LEK into ALL), excluding/including specifically certain accounts, etc.

Sometimes it is necessary to exclude certain standard cashbox accounts from the processing by Twister, these accounts are then listed in the section “IgnoreAccounts” of the configuration files.

In some other cases, non-standard cash accounts need to be additionally processed, these

accounts are then listed in the section “ExtraCashAccounts” of the config file.

Twister (CWN) Taking care of all Liquidity (Cashbox snapshot, Nostro transactions) and Currency Position related transactions. Entries on Nostros are displayed in Dealware’s “List Account Entries” with status ‘ToBeMatched’ (entries are created related to a CpD account for the case the nostro cannot be identified by Twister).

[Client] TwisterCWN version 0.6.9 (2013-11-25). Changes since TRP Oct announcement (V.0.6.7):

Use new IsOffSiteATM Terminal attribute added in CWN, for an identification of the Off-Site ATMs, and the possibility to report separately inside Dealware. Located at:

ftp.quipugmbh.com/Quipu Software/Twister/CWN-DW/TwisterCWN. For the case CWN and DW are not synchronised anymore (e.g. if the CWN database is switched, Twister can be run in resynchronisation mode, like ‘TwisterCWN m RESYNC‟; Twister will switch automatically into normal mode of operations after the resync.

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 [Server] TwisterUserSrvCWN version 0.6.5 (2013-11-25). Changes since TRP

[Server] TwisterUserSrvCWN version 0.6.5 (2013-11-25). Changes since TRP Oct announcement (V.0.6.3): Use new IsOffSiteATM Terminal attribute added in CWN, for an identification of the Off-Site ATMs, and the possibility to report separately inside Dealware. Located at:

ftp.quipugmbh.com/Quipu Software/Twister/CWN-DW/UserServerCWN

[Manager] Twister_Manager_GUI version 1.1.1 (2013-06-06). Last change: Fixed management of CW/CWN DSNs to always set AutoTranslate=No. The use of TwisterManager is only supported on environments where Twister and TwisterUserSrv are running on the same machine; setups where Twister and TwisterUserSrv are run on separate machines should be configured manually, with support of Quipu Regional Office staff. Latest version: Twister_Manager_GUI-1.1.1- 20130606.tar.bz2 located at: ftp.quipugmbh.com/Quipu Software/Twister/TwisterManagerGUI

Parametrisation notes:

For several installations, finding the match between Nostros in CWN and Nostros in DW was more complicated than expected (matching is made through table BankNostros in CWN, obtaining the external Account Number existing in this table as well as in Dealware). In at least one of the cases, during an Implementation Project phase, the problem was a wrong parametrisation in CWN, difficult to avoid in such early stages.

Problems with Test Environments:

If the Test Environment includes also Twister/TwisterCWN, it is very important to make sure that the Twister is importing consistent information from Customware.Net Twister is not just an interface, it is a full Synchronisaiton Tool, checking also that no entries are missing, and that no entries are imported in a duplicated way.

In order to know from which Entry on to start importing from CWN, TwisterCWN on start looks in DW for the “latest entry” imported from CWN with a Value Date after the last Blocking Date. This “latest imported entry” is then searched in the CWN database in order to identify the

starting point where to continue to import.

If the “latest imported entry” cannot be found – e.g. because of restoring another CWN backup from production or if the “latest imported entry” was corresponding to a test entry made on a

test environment, and this test environment has been reset -, Twister cannot find the starting point for continuing the import and stops.

If even worse – the “latest imported entry” is identifying now another entry, different from the original, this is considered as a bug and will stop Twister. This situation can happen if the CWN part of a test environment is frequently being refreshed from the Production environment, as then every manual entry made in the CWN Test environment will be different to one with the same Id already imported to DW … it’s the same effect as if we would constantly switch between an import from CWN Production Environment and CWN Test Environment.

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014  In a situation like this – hopefully

In a situation like this hopefully never occurring in Production there are three solutions: (a) to go back on the Dealware side to a backup before the inconsistent Twister entries have been registered, (2) to run “DeleteEntries -s<ServerInstanceName> -- twister” for a removal of all imported transactions from DW database, so that Twister is forced to re-import all entries since the last Blocking Date, or (3) perform a TwisterCWN resync process with “TwisterCWN.exe –m RESYNC”, deleting all the last Twister-imported AccountEntries from Dealware that do not match any more with the changed CWN database; both (2) and (3) require that backups are made of the Dealware database before performing the procedure.

As these problems are difficult to avoid, it is recommendable to connect Twister as soon as possible to the CWN Production Environment!

Maintenance Tools

CancConfTicket

This tool is frequently used during late Setup Phases, when users are still experimenting with the possibilities, but having already registered the portfolio. The tool is cancelling Ticket confirmations for the case no payments have been already been done. It can also be used for Loans and Bonds, but only

for the last Deal Ticket confirmed (there is no way to go stepwise back, ticket by ticket). CancConfTicket.exe 1.2.0 (2014-01-20). Last changes: Technical changes related to a database table change. Latest versions located at ftp.quipugmbh.com/Quipu Software/Dealware/Tools/Maintenance.

The basic call is done via "CanConfTicket

s<ServerInstanceName>

-- FX-20390/1". Additional

options which can be used are STATUS, DEALER, COMMENT. If the Dealer is not explicitly mentioned, a prompt will request this information (enter either Party Code or Short Name). The password is always requested via prompt. There is a check if the mentioned Dealer has access rights for the day of the tool run. This tool is frequently used if a Ticket need to be deleted, but has been confirmed by mistake, as

first step before the Delete. Some more details:

option STATUS, e.g. “CancConfTicket s<TestServer> -- FX-20390/1 STATUS=[EXPIRE]”;

if option STATUS is NOT used, the ticket will be in status Pending Confirmation after the run. The mentioned status is the one the ticket should be after the run. CANCEL and STORNO are equivalent. AUTO and PENDING are equivalent and the current default

option COMMENT, e.g. CancConfTicket s<TestServer> -- FX-20390/1 STATUS=[EXPIRE] COMMENT=["Duplicated Ticket registered and confirmed"]. The comment will appear on

the Ticket in the comment part. If the Comment contains empty spaces, like in the given example, it need to be used with "", like in the example

Upgrade Guide Treasury Package TRP Jan 2014

option

DEALER,

e.g.

CancConfTicket

s<TestServer> - FX-20390/1
s<TestServer>
-
FX-20390/1

COMMENT=["Duplicated Ticket registered and confirmed"] DEALER=[PR-2401]. The

DEALER can be specified with the Party Code or with the Short Name. If the Dealer's ShortName

contains empty spaces, like Beatrice Langefors, it needs to

DEALER=["Beatrice Langefors"]

be

used

with

"",

e.g.

.

CsvAccountEntry

A tool allowing imports based on Excel, e.g. for massive corrections in early project phases. If used, the

generation of the corresponding Excels should be automatized as much as possible. See CsvAccountEntryImport.doc, csvAccountEntryTestSheet.csv, CsvAccountEntryTestSheet.xls related to the import formats.

CsvAccountEntryImport.exe 2.0.0 (2013-08-26). Last changes: Case control added, in order to avoid problems when opening the entries after the import. A tool importing entries prepared in xls/csv format. Latest versions located at ftp.quipugmbh.com/Quipu Software/Dealware/Tools/Import.

DeleteOrphanedBundles DeleteOrphanedBundles 1.1.0 (2012-12-14). During setup phases, in some cases, transactions are being removed without removing also a technically needed “Bundle”. The logfile of DealwareSQL will give you a hint about. This tool can be run to remove these remainders; a run or a non-run will not have any impact on other functionality.

MergeSingleFPA

MergeSingleFPA 1.0.0 (2009-08-21). This is a helper tool for merging Financial Parties, for the case they

have been created by mistake as duplicates.

Setup Tools

AllowSingleExposureAceReg

AllowSingleExposureAceReg 2.0.1 (2012-08-27). Allows a change in the parametrisation in order to allow the registration of entries on exposure accounts manually and individually (not only in the background,

related to other “free entries” and calculated automatically). Needed for very specific business case

workarounds, only.

ClearAllTwisterSysLogEntries

ClearAllTwisterSyslogEntries.exe 1.1.2 (2012-08-04). A tool deleting all Twister related entries in the System Logfile, needed in some cases during the setup phase. Needs to be used only in communication

with the Regional Office and extremely carefully!

ClearTwisterNonImportedSysLogEntries

ClearTwisterNonImportedSyslogEntries.exe 1.1.2 (2012-08-04). A tool deleting thoseTwister related entries from the System Logfile which are related/commenting not imported entries, needed in some

Upgrade Guide Treasury Package TRP Jan 2014

Upgrade Guide Treasury Package – TRP Jan 2014 cases during the setup phase. Needs to be

cases during the setup phase. Needs to be used only in communication with the Regional Office and extremely carefully!

Colors

Colors.exe (2007-10-11). Is a helper tool for definition of background and foreground colours, e.g. for Logo and menu at the left side of Dealware screens.

DealwareSpanishHelpForRel4033

DealwareSpanishHelpForRel4033.exe. This tool locates the Spanish Help (chm version) in the directory and creates and icon. Starting with Dealware series 4.1.x, if this Help File is found, an additional menu

option is shown, allowing the access.

DwDeleteQuipuUsers

DwDeleteQuipuUsers.exe V.1.3.0 (2014-03-10). Previously called ‘DeleteQuipuUsers’ (V.1.0.2 2012-12- 12). Last Changes: As this tool exist for Bankware as well as for Dealware, the typo is now identified directly in the Tool Name, in order to avoid wrong usages.

When the option -- DROP” is used, the tool deletes all Quipu users and related entries from the Database. If no option is used, the tool does nothing.

CreateCashInTransitAccounts

CreateCashInTransitAccounts.exe 2.0.0 (2012-08-23). Is creating Cash-in-Transit accounts only for active currencies. Last changes: Internal Cash-in-Transit accounts are created only for “Own Branch”, External Cash-in-Transit accounts are created for “Own Branch”, “Bank”, “Group Company”, but only if Deal Groups CH/CN are enabled; new attribute “Product Type” is now taken into accounts

DeleteCashAccounts

DeleteCashAccounts.exe (2012-08-15). A tool deleting all cash accounts from database, needed for the cases of recodifications at the Customware side, as an example. Needs to be used only in

communication with the Regional Office and extremely carefully!

DeleteEntries

DeleteEntries.exe 1.5.1 (2010-07-27). Not changed. A tool to delete all existing entries from the database. Modes are ALL or TWISTER. Last Changes: bugfix related to an exit of the process with an error code (and thus a log file with an ERROR string appended), even though the script executed its tasks

successfully (happened when running DeleteEntries with the "twister" option). Needs to be used only in communication with the Regional Office and extremely carefully!

DW-SetLocation DW-SetLocation.exe 1.1.0 (2011-10-09). A functionality to identify easier backups made from another server not being the main operative server. If used the first time, it allows a set of a basic Bank code to a format like PCB-AB (e.g. “PCB-DE”) or ABC (e.g. “DEU”). If used subsequently, it allows only to define variants by using an additional suffix “-XYZ”; a backup file looking afterwards like “PCB-DE-021”, or “DEU-021”, depending on the basic format.

Financial Applications

20 | P a g e

Upgrade Guide Treasury Package TRP Jan 2014

EnableLocalSwiftCreateForRel42x

Upgrade Guide Treasury Package – TRP Jan 2014 EnableLocalSwiftCreateForRel42x EnableLocalSwiftCreateForRel42x.exe (2013-08-09). Not changed. This compiled scriptftp.quipugmbh.com/Quipu SoftWare/Dealware/Installation/e-QuipuXWarePasswordUtilityUserGuide.doc MercuryPasswdGen MercuryPasswdGen100.zip 1.0.0 (2011-11-03). Mercury Client configuration files are delivered with empty passwords both in compiled and also in the one sent together with the tool; they need to be installed in a suitable manner by local IT departments. This tool generates password pairs needed. SetPasswordPolicyTo41xStandard SetPasswordPolicyTo41xStandard.exe (2013-04-21). Can be used to reset password complexity to the defaults currently valid at ProCredit Group level (including a forced password renewal after 90 days). The logfile produced during the run should be stored as documentation. Financial Applications 21 | P a g e " id="pdf-obj-20-9" src="pdf-obj-20-9.jpg">

EnableLocalSwiftCreateForRel42x.exe

(2013-08-09). Not changed. This compiled script been prepared

for a fast set/reset during test times. There are three parameter to be set for SWIFT message

generation: ‘CreateLocally’, ‘CreateOnServer’, ‘CreateReport’. In order to create SWIFT messages on the local machine, ‘CreateLocally=All‟ is required, in order to test, ‘CreateReport=All‟ is useful. The settings included in EnableLocalSwiftCreateForRel41x.exe are „CreateLocally=All‟,

„CreateOnServer=None‟, „CreateReport=All‟.

FixDWClientExit

FixDWClientExit (2010-09-08). It was noticed, that when closing the Dealware application in Windows 7, the Dealware process stays in memory and does not properly close by a normal application exist (clicking on x or session > end). In order to avoid this, two registry entries needed to be changed manually for the machine being the Dealware client. This set fixes the keys

HKEY_CURRENT_USER\Software\Quipu\Dealware\forceOSExit (=true) and HKEY_CURRENT_USER\Software\Quipu\Dealware\forceOsExitSleep (=2) for the currently logged-in

user, means: The fix need to be run from the USER ACCOUNT on the USER MACHINE.

SetExpirationDateTo30

SetRateExpirationTo30.exe.

SetupPwd

SetupPwd.exe

(1.1.0,

2007-09-13).

Documentation

available:

SoftWare/Dealware/Installation/e-QuipuXWarePasswordUtilityUserGuide.doc

MercuryPasswdGen

MercuryPasswdGen100.zip 1.0.0 (2011-11-03). Mercury Client configuration files are delivered with empty passwords both in compiled and also in the one sent together with the tool; they need to be

installed in a suitable manner by local IT departments. This tool generates password pairs needed.

SetPasswordPolicyTo41xStandard

SetPasswordPolicyTo41xStandard.exe (2013-04-21). Can be used to reset password complexity to the defaults currently valid at ProCredit Group level (including a forced password renewal after 90 days).

The logfile produced during the run should be stored as documentation.

Upgrade Guide Treasury Package TRP Jan 2014

Change Control

Upgrade Guide Treasury Package – TRP Jan 2014 Change Control Version Date Reviser Changes 0.1 Inga

Version

Date

Reviser

Changes

 
  • 0.1 Inga

2014-03-12

 

Initial draft

 
  • 0.2 Inga

2014-03-12

 

updated

 
  • 0.3 2014-03-16

Sudhakar, Bernard

updated

 
  • 0.4 Inga

2014-03-20

 

updated

 
  • 1.0 Inga

2014-03-22

 

Final version

Upgrade Guide Treasury Package TRP Jan 2014

Related Documents

Upgrade Guide Treasury Package – TRP Jan 2014 Related Documents Version/Date Description Location 2014-03-12 User’s Manualftp.quipugmbh.com/Quipu for DW 4.3.2 Software/Dealware/UserManuals/English 2014-03-12 User’s Manual (Spanish) , updated ftp.quipugmbh.com/Quipu for DW 4.3.2 Software/Dealware/UserManuals/Spanish Webforms User Manual (outdated) ftp.quipugmbh.com/Quipu Software/Webforms/Documentation/UserManual Aug 2013 TMS_FunctionalDescription.pdf ftp.quipugmbh.com/UserManuals/English Oct 2013 MenusOptionsDialogs_TRP2013- ftp.quipugmbh.com/Quipu October.xlsx Software/Dealware/Releases/TRP2013-October Oct 2013 ArchivosAdjuntosEnTicketsDealware ftp.quipugmbh.com/Quipu .docx Software/Dealware/UserManuals/Spanish “Workaround Guide” for Collateral, https://finapps- Equity, Guarantees dev.quipugmbh.com/projects/llx/documents 2013-05-08 “Accounting for Treasury” https://finapps-dev.quipugmbh.com/documents/69 2012-11-28 Access Right Levels and Roles https://finapps-dev.quipugmbh.com/documents/48 2012-11-28 Access Control https://finapps-dev.quipugmbh.com/documents/48 Oct 2010 e- ftp.quipugmbh.com/Quipu InstallationGuide(Dealware&Relate SoftWare/Dealware/Installation dTools). Oct 2013 DW_Guia_Instalacion_SQL2008.doc ftp.quipugmbh.com/Quipu x SoftWare/Dealware/Installation e- ftp.quipugmbh.com/Quipu QuipuXWarePasswordUtilityUserGu SoftWare/Dealware/Installation ide.doc Webforms Installation Guide ftp.quipugmbh.com/Quipu (outdated) Software/Webforms/Documentation/InstallationGuide e- ftp.quipugmbh.com/Quipu QuipuMercuryInstallationGuide_V1 SoftWare/Dealware/Installation 1.docx TRP Oct Mercury_Server_FAQ.docx MercuryRateImport.docx ftp.quipugmbh.com/Quipu Software/Mercury/MercuryClients 2014-01-30 Newsletter_TRP2013_October_Fixe ftp.quipugmbh.com/Quipu s.docx Software/Dealware/Releases/TRP2013-October 2014-02-14 Pre Cancelaciones en TWAPP.docx Financial Applications 23 | P a g e " id="pdf-obj-22-9" src="pdf-obj-22-9.jpg">

Version/Date

Description

Location

2014-03-12

User’s Manual (English), updated

for DW 4.3.2

Software/Dealware/UserManuals/English

2014-03-12

User’s Manual (Spanish), updated

for DW 4.3.2

Software/Dealware/UserManuals/Spanish

 

Webforms User Manual (outdated)

ftp.quipugmbh.com/Quipu

Software/Webforms/Documentation/UserManual

Aug 2013

TMS_FunctionalDescription.pdf

 

Oct 2013

MenusOptionsDialogs_TRP2013-

ftp.quipugmbh.com/Quipu

October.xlsx

Software/Dealware/Releases/TRP2013-October

Oct 2013

ArchivosAdjuntosEnTicketsDealware

.docx

Software/Dealware/UserManuals/Spanish

 

“Workaround Guide” for Collateral,

https://finapps-

Equity, Guarantees

 

dev.quipugmbh.com/projects/llx/documents

2013-05-08

“Accounting for Treasury”

 

https://finapps-dev.quipugmbh.com/documents/69

2012-11-28

Access Right Levels and Roles

 

https://finapps-dev.quipugmbh.com/documents/48

2012-11-28

Access Control

https://finapps-dev.quipugmbh.com/documents/48

Oct 2010

e-

InstallationGuide(Dealware&Relate

SoftWare/Dealware/Installation

dTools).

Oct 2013

DW_Guia_Instalacion_SQL2008.doc

x

SoftWare/Dealware/Installation

 

e-

QuipuXWarePasswordUtilityUserGu

SoftWare/Dealware/Installation

ide.doc

 

Webforms

Installation

Guide

ftp.quipugmbh.com/Quipu

(outdated)

Software/Webforms/Documentation/InstallationGuide

 

e-

ftp.quipugmbh.com/Quipu

QuipuMercuryInstallationGuide_V1

SoftWare/Dealware/Installation

1.docx

TRP Oct

Mercury_Server_FAQ.docx

   
 

MercuryRateImport.docx

 

ftp.quipugmbh.com/Quipu

 

Software/Mercury/MercuryClients

2014-01-30

Newsletter_TRP2013_October_Fixe

ftp.quipugmbh.com/Quipu

s.docx

Software/Dealware/Releases/TRP2013-October

2014-02-14

Pre Cancelaciones en TWAPP.docx