PackageFeeInquiryService

ESD Interface Control Document

 

Service Version 2.0

Document Version 1.2

Updated 05/03/2013

 

 

U.S. Bank Internal

This document may not be shared with third parties without approval from the Enterprise Service Development (ESD) department. Please contact the ESD Documentation Shared Mailbox for further information.

 
 



Document Revision History

See the Service Change Log for more details about service version changes.

Date

Version

Overview of Update

Author

04/25/2012

1.0

Initial creation

Minal Satpute

04/25/2012

1.1

PackageDetailByCycle four new elements added

PackageMMSIndicator

CreditProductIndicator

BusinessGoldCheckingIndicator

BusinessPlatinumCheckingIndicator

Minal Satpute

05/03/2013

1.2

Converted to new ICD template.

Lisa De Luney

 

 

 

 

 

 

 

 

 

 

 

 

 


Table of Contents

Service Description................................................................................................................ 5

Limitations................................................................................................................................. 5

Special Considerations.............................................................................................................. 5

Assumptions.............................................................................................................................. 5

References................................................................................................................................ 5

High-Level Web Service Interface Specifications.............................................................. 6

System Interface Diagram.......................................................................................................... 6

System Interaction Diagrams...................................................................................................... 7

Security Specifications............................................................................................................... 7

Tier 2 Consumer Authorization.............................................................................................. 7

Tier 3 Consumer Authorization.............................................................................................. 7

Processing Specifications.......................................................................................................... 8

Exception Processing................................................................................................................ 8

Service Time-Out Specifications................................................................................................. 9

Detailed Interface/Message Specifications by Service Operation................................... 9

GetPackageFeeDetail................................................................................................................ 9

Operation Description............................................................................................................ 9

Processing Specifications...................................................................................................... 9

Functional Scenarios........................................................................................................... 10

Pagination or Scrolling for Results Using the GetList Aggregate.......................................... 10

Operation to Data Source Reference Table......................................................................... 10

Field/Element Specifications................................................................................................ 10

Exception Processing.......................................................................................................... 16

HeartBeat................................................................................................................................ 18

Operation Description.......................................................................................................... 18

Processing Specifications.................................................................................................... 18

Functional Scenarios........................................................................................................... 18

Pagination or Scrolling for Results Using the GetList Aggregate.......................................... 18

Operation to Data Source Reference Table......................................................................... 18

Field/Element Specifications................................................................................................ 18

Exception Processing.......................................................................................................... 20

Connection Information..................................................................................................... 22

Tier 2 Environment Configuration............................................................................................. 22

Tier 3 Environment Configuration............................................................................................. 22

Disaster Recovery (DR) Testing................................................................................................ 22

Service Change Log............................................................................................................ 23

PackageFeeInquiryService 2.0 – PRJ0000####...................................................................... 23

Operation Name.................................................................................................................. 23

Refactored Service and Operation Cross-Reference Table........................................... 24

Operation Name...................................................................................................................... 24

Appendix A     Definitions, Acronyms and Abbreviations............................................... 25


Service Description

Packages are a combination of U.S. Bank qualifying accounts that offer consumer and business customers’ benefits and/or features which may include product discounts and rewards. The PackageFeeInquiryService 2.0 is used to retrieve package fee-related elements/attributes to determine whether fees can be waived or not.

Limitations

Consider the following limitations before consuming this service:

·       The service will support XML SOAP 1.2 messages over HTTP 1.1.

·       Refer to the WSDL and XSD files for the technical details.

·       This service is accessed from Tier 2/Tier 3.

Special Considerations

Consider the following special considerations when consuming this service:

Assumptions

The audience has knowledge of and understands the following technologies:

·       XML

·       XSD

·       SOAP

Note: ESD designed PackageFeeInquiryService 2.0 as an enterprise Web service with the assumption that any application could be a consumer of this service.

References

ESD referenced the following documents or artifacts while creating or updating this ICD:

·       PackageFeeInquiryService_V_1_0.wsdl

·       MessagePackageFeeInquiryService_V_1_0.xsd

·       USBSOATypeLibrary_V_3_0.xsd

·       USBSOACoreComponentsLibrary_V_3_0.xsd

·       USBSOAAccountComponentsLibrary_V_2_0.xsd

 


High-Level Web Service Interface Specifications

This topic illustrates both the system interface and interactions and covers specifications related to service security, processing, exception processing and time-outs.

System Interface Diagram

The following diagram (Figure 1) gives a high-level view of the pieces involved in the PackageFeeInquiryService 2.0 service, which is an enterprise Web service that could be used by any application. The diagram shows the process of how consumers connect to enterprise services through the Oracle Service Bus (OSB), which hosts virtualized services, instead of connecting directly to them.

Figure 1   PackageFeeInquiryService_V_2_0


System Interaction Diagrams

PackageFeeInquiryService 2.0 presents multiple scenarios for processing requests. The following interaction and sequence diagrams illustrate each scenario and provide better insight about how the components interact.

The following diagram (Figure 2) shows how the system routes all requests between consumers and services through OSB. This is true for both internal and external Web services. The following diagram illustrates the role OSB plays in the sequence following a consumer call to a service operation.

Note: This diagram is a brief overview of this interaction and not a complete picture of how OSB and other involved software components work together in the service environment.

Figure 2   Sequence Diagram

Note: A proxy pattern is used and the proxy gateway is used as a policy enforcement point for authentication.

Security Specifications

The following topics describe the U.S. Bank security specifications this service interface must implement.

Tier 2 Consumer Authorization

Mutual authentication, or two-way authentication (which is sometimes written as 2WAY authentication), refers to two parties authenticating each other suitably. In technology terms, this refers to clients or users authenticating themselves to servers and those servers authenticating themselves to the clients or users in such a way that both parties are assured of the others' identities. Trusted third parties that use shared secrets, as in Kerberos v5, or cryptographic means, as with a public key infrastructure, can also validate identities.

Tier 3 Consumer Authorization

ESD uses WS-Security 1.0 to handle service authentication. ESD expects all clients to provide a WS-Security Username Token in the WS-Security header in all service calls. SSL-mutual authentication provides the payload authentication between OSB and the TIBCO service layer. See the Oracle Service Bus (OSB) WS-Security Mechanism document on the ESD SharePoint site for more information.


Processing Specifications

This topic describes the most common processing pattern used by the service operations. If this pattern does not apply to an operation, that operation will contain a description of its unique processing pattern.

·       Processing starts with the client application sending the SOAP request message to the service URL over HTTPS.

·       The BW Process Engine (engine) monitors the specified JMS-based request queue for messages. When the engine detects a message on the HTTPS port, it initiates the BW Process associated with that service operation.

·       The system logs the request, then validates and transforms it into the host-specific format. In this case, the XML message is converted into a COBOL Copy Book (CCB) format, which is also called a Flat File Definition (FFD) format.

·       The message is sent to the MQ queue after transformation. The MQ CICS adapter, which runs on the mainframe, processes the message and starts the CICS transaction associated with the application name provided in the message.

·       Hogan/PAS sends a reply to the MQ CICS adapter. The MQ adapter places this reply message in the MQ reply queue.

·       The BW process Engine (engine) waits for a reply from MQ adapter. When the engine detects the message, it converts the message from the FFD format into XML. The BW process uses Contivo as a mapping engine during the transformation.

·       The system sends a reply to another JMS-based response queue, which OSB monitors. When OSB detects a reply, it pulls the response and passes it to the client.

·       There is a time-out limit related to messaging on both the client and host sides. When a time-out occurs, the system sends the USBSOAPFault in the response.

Exception Processing

Consumers access all services through the OSB gateway layer. Consumers must handle the following two types of faults, generated by either the gateway or implementation layers, when calling any of the ESD-hosted services:

·       W3 Standard Fault (gateway-generated fault)

·       USBSOAPFault (implementation-generated fault)

Refer to the technical implementation service guide for directions on implementing enterprise error codes for replies and fault messages. (This topic was called Error Codes in earlier ICD versions.)

Note: Each operation includes documentation on the specific error messages impacting that operation.


Service Time-Out Specifications

When time-outs occur, consumers should receive an USBSOAPFault in the following places:

·       OSB Gateway, or

·       TIBCO Service layer.

Important:

·       Consumers need to set the time-out value higher than the OSB Gateway time-out value.

·       Individual operations can have different time-out values, which are documented in the specific operation topics.

·       The highest operation time-out values are set during the overall TIBCO service implementation. For example, a service has three operations. If the first and second operations need 10 seconds to process, but the third operation needs 20 seconds, then the TIBCO service time-out value is set at 20 seconds.)

At the TIBCO Service implementation for PackageFeeInquiryService 2.0, ESD determined that a 10-second time-out value is appropriate.

The following diagram shows the end-to-end time-out intervals for the various system components involved in the PackageFeeInquiryService 2.0 service.

Figure 3   End-To-End Timeout Intervals

Detailed Interface/Message Specifications by Service Operation

This topic provides detailed processing specifications that are common to all the operations for this service.

GetPackageFeeDetail

The following topics describe this operation.

Operation Description

The GetPackageFeeDetail operation is used to retrieve package elements from Package History for certain elements used by package in determining whether fees can be waived or not. Package elements would be returned through this operation and it is up to the consumer to decide whether to waive a fee or not by using the returned elements.

Processing Specifications

This topic describes the most common processing pattern used by the service operations. If this pattern does not apply to an operation, that operation will contain a description of its unique processing pattern.

·       See Processing Specifications for service-level processing specifications.

·       This service call would be applicable only for sub products PR, PI and GS on DDA accounts and/or applicable on PKG accounts. Please refer the common processing specification in section 2.4 for additional details. If one has the PKG key data this should be entered instead of the CORE, as it is much more efficient.


Functional Scenarios

The following scenarios demonstrate how to set up the operation for functional testing and usage.

NA

Pagination or Scrolling for Results Using the GetList Aggregate

ESD enterprise services use the GetList aggregate type in both requests and replies for services that require scrolling. The usage is slightly different for both requests and replies between service implementation and consumption.

NA

Operation to Data Source Reference Table

This table shows the operation and the provider system of record (SOR).

Source System Name

Source System Transaction/Message Name

HOGAN PAS

EBDRFIP3

Field/Element Specifications

This section explains all of the field-level elements for the request and response aggregates.

 


GetPackageFeeDetailRequest

Schema Field Name

Type

Width

Req?

Description

Host Field Name

GetPackageFeeDetailRequest

  CoreAccount (Choice)

    AccountKeyIdentifier

 

 

Y

 

 

      OperatingCompany

      Identifier

Integer

0 to 5

Y

DDA Operating Company
Number

X77806-CORE-ACCT-COID-N

      ProductCode

String

0 to 3

Y

DDA Product Code

X77806-CORE-ACCT-PROD

      PrimaryIdentifier

String

0 to 23

Y

DDA Account Number

X77806-CORE-ACCT-NBR

  SubProductCode

String

0 to 2

Y

SubProductCode

PI, PR, GS are the only allowed sub product codes

 

   PackageAccount (Choice)

 

 

 

 

    PackageKeyIdentifier

 

 

Y

 

 

      OperatingCompany

      Identifier

Integer

0 to 5

Y

Package Company Number

X78075-INP-PKG-COID-N

      ProductCode

String

0 to 3

Y

Package Product Code

X78075-INP-PKG-PROD

      PrimaryIdentifier

String

0 to 23

Y

Package Account Number

X78075-INP-PKG-NO-X

 

 

 

 

 

 

    ChannelCode

String

0 to 3

Y

Channel Code

X77113-CHANNEL-ID

GetPackageFeeDetailReply

Name

Type

Width

Req?

Description

Host Field Name

GetPackageFeeDetailReply

    Status

 

 

Y

 

 

      StatusCode

Integer

0 to *

Y

Service Status Code

Using PAS-RESULT-CODE & BTCB-USER-CC and with matching  IFX CODE

      ServerStatusCode

String

0 to 20

N

Host System Status Code

BTCB-USER-CC

      Severity

String

0 to 80

Y

Service Severity Level

Using PAS-RESULT-CODE & BTCB-USER-CC and with matching  IFX SEVERITY

      StatusDesc

String

0 to 255

N

Host System Status Description

BTCB-USER-DESCRIPTION

    PackageFeeDetail

      FeeWaiveDetail

 

 

N

 

 

        WaiveCode

String

0 to 2

Y

Waive Code

X112-WAIVE-CD

        WaiveCodeDescription

String

0 to 40

N

Waive Code Description

X112-WAIVE-CD-DESC

        WaiveDuration

 

 

N

 

 

          StartDate

Date

 

N

Waive Duration Start Date

X112-WAIVE-START-DATE

          EndDate

Date

 

N

Waive Duration End Date

X112-WAIVE-END-DATE

      PackageKeyIdentifier

 

 

N

 

 

        OperatingCompany

        Identifier

Integer

0 to 5

N

Package Account Company Number

X112-PKG-COID

        ProductCode

String

0 to 3

N

Package Account Product

X112-PKG-PROD-CODE

        PrimaryIdentifier

String

0 to 23

Y

Package Account Number

X112-PKG-NUMBER

      DemandDeposit

 

 

N

 

 

AccountKeyIdentifier

 

 

N

 

 

OperatingCompanyIdentifier

Integer

0 to 5

N

DD Account Company Number

X112-CORE-DDA-COID

ProductCode

String

0 to 3

N

DD Account Product

X112-CORE-DDA-PROD-CODE

PrimaryIdentifier

String

0 to 23

Y

DD Account Number

X112-CORE-DDA-ACCT-NUM

SubProductCode

String

0 to 2

N

DDA SubProductCode

X112-CORE-DDA-SUB-PROD-CODE

      PackageDetailByCycle (Array 0 to 3)

 

 

N

 

 

        AverageLedgerBalance

        Code

String

0 to 1

N

Average Ledger Balance
The average ledger balance as of three cycles ago.  This field is updated when the statement is cycled.

X112-C1-ALB-IND
THROUGH
X112-C3-ALB-IND

        AverageLedgerAmount

Decimal

15.2

N

Average Ledger Amount

X112-C1-AVG-LEDG-BAL
THROUGH
X112-C3-AVG-LEDG-BAL

        TotalCombinedBalance

        Code

String

0 to 1

N

Total Combined Balance Code

X112-C1-TOT-COMB-BAL-IND
THROUGH
X112-C3-TOT-COMB-BAL-IND

        TotalCombinedAmount

Decimal

15.2

N

Total Combined Amount

X112-C1-TOT-COMB-BAL
THROUGH
X112-C3-TOT-COMB-BAL

        MonthlyMaintenance

        FeeAmount

Decimal

15.2

N

Monthly Maintenance Fee

The amount owed by a customer for a specific settlement period

X112-C1-MONTH-MAINT-FEE
THROUGH
X112-C3-MONTH-MAINT-FEE

        CustomerSegmentCode

String

0 to 7

N

Customer Segment Code

X112-C1-CSI
THROUGH
X112-C3-CSI

        WaiveCode

String

0 to 2

N

Waive Code

X112-C1-WAIVE-CD
THROUGH
X112-C3-WAIVE-CD

        WaiveCodeDescription

String

0 to 40

N

Waive Description

X112-C1-WAIVE-CD-DESC
THROUGH
X112-C3-WAIVE-CD-DESC

        DirectDepositCode

String

0 to 1

N

Direct Deposit Code

X112-C1-DIR-DEP-IND
THROUGH
X112-C3-DIR-DEP-IND

        D25ATACode

String

0 to 1

N

D25 ATA Code

X112-C1-D25-ATA-IND
THROUGH
X112-C3-D25-ATA-IND

        AutoPayLoanCode

String

0 to 1

N

Auto Pay Loan Code

X112-C1-AUTO-PAY-LOAN-IND
THROUGH
X112-C3-AUTO-PAY-LOAN-IND

        AutoTransferINVCode

String

0 to 1

N

Auto Transfer Inv Indicator

X112-C1-AUTO-TRANS-INV-IND
THROUGH
X112-C3-AUTO-TRANS-INV-IND

        TrustRelationshipCode

String

0 to 1

N

Trust Relationship Code

X112-C1-TST-REL-IND
THROUGH
X112-C3-TST-REL-IND

        PackageMoneyMarket

        SavingsCondition

        MetCode

String

0 to 1

N

PackageMoneyMarketSavingsConditionMetCode

PR=New indicator

PI=’X’

GS=’X’

X112-C1-MMS-COND-MET-AND

THROUGH

X112-C3-MMS-COND-MET-AND

       CreditProductIndicator

String

0 to 1

N

Credit Product Indicator

Credit Product (Exclude reserve line) indicator

PR=’X’

PI=New indicator

GS=’X’

X112-C1-CR-PROD-XCLUD-RSV-LIN

THROUGH

X112-C3-CR-PROD-XCLUD-RSV-LIN

       BusinessGoldChecking

        Indicator

String

0 to 1

N

BusinessGoldCheckingIndicator

PR=’X’

PI=New indicator

GS=’X’

X112-C1-BUSINESS-GOLD-CHK

THROUGH

X112-C3-BUSINESS-GOLD-CHK

       BusinessPlatinum

      CheckingIndicator

String

0 to 1

N

BusinessPlatinumCheckingIndicator

PR=’X’

PI=’X’

GS=New indicator

X112-C1-BUSINESS-PLATINUM-CHK

THROUGH

X112-C3-BUSINESS-PLATINUM-CHK

      AdditionalPackageData (Array 0 to 13)

 

 

N

 

 

        AverageLedger

        BalanceAmount

Decimal

15.2

N

Cycle Average Ledger Balance Amount

X112-C1-AVG-LEDG-BALANCE
THROUGH
X112-CD-AVG-LEDG-BALANCE

        AverageCollected

        BalanceAmount

Decimal

15.2

N

Cycle Average Collected Balance Amount

X112-C1-AVG-COLL-BALANCE
THROUGH
X112-CD-AVG-COLL-BALANCE

        CycleDaysCount

Integer

0 to 3

N

Cycle Days

X112-C1-NUM-DAYS
THROUGH
X112-CD-NUM-DAYS

 


Exception Processing

This topic describes the service specifications for SOAP faults and status aggregate error codes. See Exception Processing for additional details about the USBSOAPFault and W3 standards.

·       Consumer will either receive the SOAP fault or the ESD standard status aggregate in the response, which tracks the execution status of the service operation.

·       When a service does not execute successfully, the consumer receives the SOAP fault, which the USBSOAPFaultoperation produces.

·       When a service executes successfully, the consumer receives the ESD standard status aggregate.

Service layer returns a SuccessCode of 0 in the status aggregate, but if the host returns any conditional error codes, consumers use the StatusCode table to determine the cause of the issue.

·       ESD maps all undocumented error code/condition to StatusCode 100, which is General Error.

Additional Statuses

Please refer the ESD Status Aggregate Usage Standards Document in the Customer Portal of the ESD USBnet site for more information about additional statuses.

 


StatusCode

Status Code

Severity

Status Description

Server Status Code

Server Status Description

Additional details

0

Info

Success

<Host Condition Code>

Success

 

1120

Error

No Records Match Selection Criteria

37814

NO CUSTOMER FOUND

 

100

Error

General Error - <Host Condition Description>

<Host Condition Code>

All undocumented condition codes will be treated as GENERAL ERROR at the service layer

 

1140

Warning

Some Selection Criteria Not Supported

 

 

 

1120

Info

No Records Match Selection Criteria

00006

Package not found  - Package application

 

2350

Error

AccountClosed

00223

Package is closed – Package application

 

2421

Error

Account not eligible for this transaction

60236

Account not in package – PAS application

 

TBD

TBD

TBD

60480

PKG SPC Not a BDR SPC – PCD 77113 (the old “Fatal Processing” error) – PAS application

 

 


HeartBeat

The following topics describe this operation.

Operation Description

The HeartBeat operation provides the capability for an external monitoring system or for the consuming application to check that the service is active and responding.

Processing Specifications

The processing specifications for the HeartBeat operation do not follow this service’s most common processing pattern.

This processing pattern for this operation is:

·       The service consumer, or consuming application, sends a request.

·       The service consumer, or consuming application, receives a reply.

o   The HeartBeat operation sends a reply with a status aggregate, indicating success.

o   If the service consumer, or consuming application, receives a reply, the assumption is that all other operations contained within the service are operational.

Note: It is not recommended to check the HeartBeat operation too frequently (more than once or twice a minute), because this could increase traffic and cause other issues.

Functional Scenarios

NA

Pagination or Scrolling for Results Using the GetList Aggregate

NA

Operation to Data Source Reference Table

This table shows the operation and the provider system of record (SOR).

Source System Name

Source System Transaction/Message Name

NA

NA

Field/Element Specifications

This section explains all of the field-level elements for the request and response aggregates.

 


HeartBeatRequest

Name

Type

Width

Req?

Description

Host Field Name

HeartBeatRequest

 

 

 

Empty aggregate.

 

HeartBeatReply

Name

Type

Width

Req?

Description

Host Field Name

HeartBeatReply

 

 

 

 

 

Status

 

 

Y

 

 

      StatusCode

Integer                 

0 to 10

Y

Status Code
This list provides the complete set of valid Response Status codes defined for the response Status Aggregate Status Code along with conditions that may cause the Response Status to be sent 

 

      Severity

String

0 to 80

Y

Severity
The severity is assigned once a Status Code is selected for the specific source systems code

 

      StatusDescription

String

0 to 255

N

Status Description
Status text is provided in the Status Desc field

 

      ServerStatusCode

String

0 to 20

N

Server Status Code
This status code will be the source systems status code

 

      ServerStatusDescription

String

0 to 255

N

Server Status Description
This status description will be the source systems status description

 


Exception Processing

This topic describes the service specifications for SOAP faults and status aggregate error codes. See Exception Processing for additional details about the USBSOAPFault and W3 standards.

·       Consumer will either receive the SOAP fault or the ESD standard status aggregate in the response, which tracks the execution status of the service operation.

·       When a service does not execute successfully, the consumer receives the SOAP fault, which the USBSOAPFaultoperation produces.

·       When a service executes successfully, the consumer receives the ESD standard status aggregate.

Service layer returns a SuccessCode of 0 in the status aggregate, but if the host returns any conditional error codes, consumers use the StatusCode table to determine the cause of the issue.

·       ESD maps all undocumented error code/condition to StatusCode 100, which is General Error.

 


StatusCode

Status Code

Severity

Status Description

Server Status Code

Server Status Description

Additional details

0

Info

Success

 

 

Service is active.


Connection Information

The end points for ESD enterprise Web services are documented in the following table(s):

Note: The data centers are Olathe Business Center (OBC) and Energy Park Operations Center (EPOC).

Tier 2 Environment Configuration

NA

Tier 3 Environment Configuration

Use the URLs associated with the data center in which your consuming application is deployed.

Environment

Service URL

DEV: OBC

https://dev-internalservice.us.bank-dns.com:8002/PackageFeeInquiryService_V_2_0

IT: OBC

https://it-internalservice.us.bank-dns.com/PackageFeeInquiryService_V_2_0

UAT: EPOC

https://uat-internalserviceep.us.bank-dns.com/PackageFeeInquiryService_V_2_0

UAT: OBC

https://uat-internalserviceobc.us.bank-dns.com/PackageFeeInquiryService_V_2_0

PROD: EPOC

https://internalserviceep.us.bank-dns.com/PackageFeeInquiryService_V_2_0

PROD: OBC

https://internalserviceobc.us.bank-dns.com/PackageFeeInquiryService_V_2_0

Disaster Recovery (DR) Testing

ESD designed its enterprise Web service infrastructure (the Oracle Service Bus or OSB) to use both data centers actively all the time for UAT and PROD environments. This configuration, called Active/Active, is different from the Active/Passive architecture, which is also referred to as Disaster Recovery (DR).

Because ESD does not have or provide a DR environment, ESD instead supports DR testing during quarterly Enterprise Readiness Services Group weekends under the following conditions:

·       ESD will provide a DR URL for OSB consumers to use during their DR testing.

·       Consumers are responsible for configuring their own applications for DR testing.

Please visit the Customer Portal on the ESD USBnet site for more information about how ESD supports DR testing.

Note: External vendor DR testing is not part of the Active/Active Enterprise Service Bus (ESB) testing. Please be aware that this type of testing is rarely possible in most cases.


Service Change Log

This topic covers the functionality that ESD has removed or added in relation to PackageFeeInquiryService.

PackageFeeInquiryService 2.0 – PRJ0000####

Operation Name

Request Message

Date

Change Type

Description or Fields Added/Removed/Modified

 

 

 

 

 

 

 

 

 

Reply Message

Date

Change Type

Description or Fields Added/Removed/Modified

 

 

 

 

 

 

 

 

 


Refactored Service and Operation Cross-Reference Table

This table documents the previous service operations, aggregates and fields for the corresponding PackageFeeInquiryService 2.0 operations as follows:

·        

Operation Name

OLD Schema (Service.Operation)

 

NEW Schema (Service.Operation)

 

Comments

Aggregate Name

Element Name

Aggregate Name

Element Name

 

[Insert Name Here]Request

[Insert Name Here]Request

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[Insert Name Here]Reply

[Insert Name Here]Reply

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Appendix A              Definitions, Acronyms and Abbreviations

The following table defines the acronyms or terms specific to ESD and/or this service’s interface.

Acronym/Term

Definition

CCB

COBOL Copybook. A section of high-level code that defines the layout of program data.

CICS

Customer Information Control System. A transaction server that runs on the mainframe.

CIM

Common Information Model. The common repository for the Enterprise Business Objects/Canonicals’ (EBO/EBC), Enterprise Business Message's (EBM), Enterprise Business Message Components (EBMC) and Enterprise Business Message Types (EBMT).

DEV

Development. A testing environment.

EPOC

Energy Park Operations Center. A U.S. Bank data center.

EMS

Enterprise Messaging System. Part of the TIBCO products.

ESD

Enterprise Service Development. The U.S. Bank department that creates and manages enterprise Web services.

FFD

Flat File Definition. A plain text file format. Sometimes referred to COBOL Copybook (CCB).

PAS

Platform Automation System. PAS is designed to be a general gateway between non-3270 device and host applications. PAS is the Application Processing Interface (API) for all devices into Hogan applications for all non-financial transaction activity.

HTTPS

HyperText Transport Protocol Secure. Websites use this protocol to transmit and receive data securely through a secure socket layer (SSL).

IT

Integration Testing. A testing environment.

MQ

Messaging software that is part of the IBM WebSphere product.

OBC

Olathe Business Center. A U.S. Bank data center.

OSB

Oracle Service Bus. An enterprise service bus (ESB) that connects, mediates and manages interactions between services and applications.

PROD

Production. The production environment.

SOAP

Simple Object Access Protocol (SOAP) version 1.2 is the W3C specification for a simplified messaging framework based on XML.

SOR

System of Record. The authoritative data source for a piece of information, for example Hogan.

TIBCO

The Information Bus Company. Real-time, event-enabled infrastructure software that provides an interface to date on the mainframe. U.S. Bank currently uses Business Works (BW), BusinessConnect (BC), EMS, Rendezvous, Active Database Adapter, Hawk and Administrator.

UAT

User Acceptance Testing. A testing environment.

WSDL

Web service Definition Language (WSDL). Version 1.1 is the W3C specification for WSDL files.

XML

Extensible Markup Language. An open standard for describing data from the W3C.

XSD

XML Schema Definition. XML-based language that describes and controls the structure of XML documents.