Skip to content

rconnelly/ach.fulfillment

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Application and service deployment

What will you need for deployment

  1. Installed MSSQL server. You can use SQLEXPRESS.
  2. Microsoft .Net 3.5 Service Pack 1
  3. .NET Framework 4.5
  4. Your server must have IIS for hosting
  5. Web-Deploy this installs Web Deploy (and its underlying executable, MSDeploy.exe) on your server. Also it installs the Web Deploy Handler and integrates it with the Web Management Service. You can find how to configure and install it here Installing and Configuring Web Deploy
  6. Wix Toolset (http://wixtoolset.org/)

Deployment

  1. Download sources from github repository.
  2. Create new Database on your Database Server. We are using name "Ach" for database by default, if you want another name do not forget change it for your one in scripts.
  3. Go to \Build\ folder and run Build.Local.cmd
  4. Change connection string in such places: \Build\Assembly\Packages\Ach.Fulfillment.Web.SetParameters.xml, \Build\Assembly\Service\Ach.Fulfillment.Scheduler.install.
  5. Go to \Build\Assembly\setup.cmd change connection string to proper one and if you are deploying from one machine to another then set DeploymentServer also.
  6. Run RunSetup.cmd
  7. PPS Partner with default user will be created in database tables. Put real company payment information for this partne into PartnerDetails table.
  8. Go to the Scheduler service and open quartz_jobs.config, here find UploadAchFilesJob and put ftphos, UserId, Password into "job-data-map" entities

Job configuration

  1. Go to quartz_jobs.config file
  2. For each job there is "job-data-map" section where additional data for job should be added.
  3. Open "trigger" section - there you can configure when your job will be run. Change cron-expression for your one. For more information look at http://en.wikipedia.org/wiki/Cron

API

CREATE TRANSACTION

http://servicehost/api/transaction

Creates new transaction in database based on data in request. Transaction will have status Created and will be put in queue. After that job will add it to next batch.

POST

Accept: application/json

Content-Type: application/json

Request:

{
  "individualIdNumber" : "123456789012345",
  "receiverName" : "ReceiverName",
  "entryDescription":"PAYROLL",
  "entryDate":"01.01.2012",
  "transactionCode":"22", 
  "transitRoutingNumber":"123456789",
  "dfiAccountId":"12345678901234567", 
  "amount":"123,00", 
  "entryClassCode":"PPD", 
  "callbackUrl":"http://send.callback.com",
  "paymentRelatedInfo":"",
  "serviceClassCode":"200"
}

Response: { "transactionId":123456789012345 }

GET TRANSACTION

http://servicehost/api/transaction/id

Returns the transaction based on an id. This transaction id is generated by the server when the transaction is first created. It is returned in the repsonse

GET

Accept: application/json

Content-Type: application/json

Response:

{
  "transactionId":123456789012345,
  "status":"Created",
  "individualIdNumber" : "123456789012345",
  "receiverName" : "ReceiverName",
  "entryDescription":"PAYROLL",
  "entryDate":"01.01.2012",
  "transactionCode":"22", 
  "transitRoutingNumber":"123456789",
  "dfiAccountId":"12345678901234567", 
  "amount":"123,00", 
  "entryClassCode":"PPD", 
  "callbackUrl":"http://send.callback.com",
  "paymentRelatedInfo":"",
  "serviceClassCode":"200"
}