You are here

NEFSS與CAP的功能比較

CAP是日本IBM第三代連線核心銀行系統代表性產品(DSE),NEFSS則是繼承CAP(DSE)經驗以Websphere技術為平台之新一代產品.兩者都是核心銀行連線控制程式,功能(NFR)大致相同,差別是在兩者開發技術完全不同,CAP是IMS/Assembly而NEFSS則是Websphere/J2EE/EJB,前者呈現OLTP環境下的成熟作品,後者則是MCS(Mission Critical System)環境下應用CBM開發技術的先鋒.....

項目

編號

內容

CAP

NEFSS

1

Continuous operation

1.1

Set point of continues operation

24*365

24*365

1.2

Implement of system continues operation

On-line change

On-line change, cluster configuration

1.3

Requirement of system breakdown

Statutory check, H/W maintenance, S/W maintenance

Statutory check, H/W maintenance, S/W maintenance

1.4

Transaction lock function

Service stop function

Operation check function

1.5

Terminal lock function

Logical unit lock by VTAM

Control by WLM/restricted by channel

1.6

DB reconfiguration in running

HSR,unload/reload IMS online change, DB dynamic reconfig

Rebuild index, reorganize index, reorganize table space, unload/load

1.7

DB backup in running

Flash copy of concurrent image COPY/DISK

Flash copy of concurrent image COPY/DISK

1.8

On-line change

Application module change by IMS

Module change by WAS, DB reorganization by manager, configuration information change by NEFSS/WAS

2

Performance

2.1

Response time

1 sec

1 sec

2.2

throughput

1000 TRX/sec around

As is 100 TRX/sec, implementation plan 1000 TRX/sec

2.3

Batch processing time

BMP, multiple transaction in one synpoint

Concurrent processing,check-point restart,multi-transaction in one synpoint

3

Maintainability

3.1

Application maintenance

TSO

PC/WASD

3.2

S/W maintenance(base product)

PMR APAR/PTF

PMR APAR/PTF service pack

3.3

S/W maintenance(middleware)

PMR APAR/PTF

Provide modified module

3.4

S/W version up(base product)

Pre-test by IBM, Pre-investigation by APAR

Pre-test by IBM, Pre-investigation by APAR/service pack

3.6

S/W version up(middleware)

Pre-test by IBM

Pre-test by IBM

3.7

Version control

SMP

Service pack

4

Recovery and restart

4.1

Recovery and restart policy

XRF for local site (?)

N+1 by cluster configuration, disk recovery for contingency

4.2

Set point of recovery time

Set point by severity

Set point by severity

4.3

Application fault recovery

Analysis with WTO message, Netview log, dump etc.

Analysis with log service, (NEFSS),NetView log, dump etc.

4.4

OS fault recovery

Analysis with SYSLOG, NetView, dump etc.

Analysis with log service, (NEFSS), NetView log, dump etc.

4.5

S/W fault recovery

Analysis with SYSLOG, NetView, dump etc.

Analysis with log service, (NEFSS), NetView log, dump etc.

4.6

H/W fault recovery

Analysis by IBM engineer

Analysis by IBM engineer

4.7

Single node fault recovery

Running at normal single node

N/A

4.8

PD team

Team consists of mainly PS/HATC and development division

Team consists of mainly PS/ common team and development division

4.9

Trace function

SYSDUMP, SDUMP, standalone DUMP

SYSDUMP, SDUMP, standalone DUMP, JVM core dump, trace service(NEFSS)

4.10

Lost data management

Customer control (matching transaction log and journal)

Customer control (matching transaction log and journal)

4.11

Peripheral/related system fault recovery

Customer input for transaction cancellation

Customer input for transaction cancellation

4.11

Direct modification function to DB

Implementation by customer

Implementation by customer or tool

5

Operation and fault monitoring

5.1

Implementation way and fault monitoring

Automation by Tivoli SA or operation/monitoring by NetView CMC host

Automation by Tivoli SA or operation/monitoring by NetView CMC host

5.2

Performance analysis function

RMF, SMF , DC monitor, OMEGAMON

RMF,SMF,WSAM,DB2PE,DB2QM,transaction monitor(NEFSS)

5.3

TRX processed number grasping

Reconcile counter in DB

Reconcile counter in DB

5.3

TRX response static acquisition

Tool development by customer

Transaction monitor(NEFSS)

5.4

Centralized monitor function

NetView

NetView

5.5

Anomaly detection

NetView

NetView

5.6

Batch job management

NetView/OPC

TWS( Tivoli Workload Scheduler(

5.7

DB dual configuration

MADS (IMS function)

Dual configuration by DISK(Hyper swap)

6

Flexibility and extensibility

6.1

Addition of new application programs

Add by command of middleware(CAP)

Module change function provided by WAS

6.2

Processing capacity improvement

CPU, memory and box can be change dynamically

CPU, memory and box can be change dynamically

6.3

On-line bulk processing

Capacity planning

Capacity planning

6.4

Batch bulk processing

One synchronized point in multiple transaction of BMP

One synchronized point in multiple transaction of batch on WebSphere

6.5

Distribution parallel processing function by processing was/amount

Distribution by HUB/branch server

Distribution by WLM plug-in of WAS

6.6

Flexibility of naming convention

Some limitation

No restriction as application name, 8 digits alphanumeric for DB2

6.7

System constraint to be considered in extension

Number of CPU, DASD, memory and channel

Number of node, WLM, DASD

6.8

Sub-system connection

Point-to-point

Connection by HUB

6.9

External system connection

Direct connection

Connection via external connection I/F

6.10

New branch client/ATM connection

Direct connection

Channel integration by HUB/MCT

6.11

New channel system connection

Direct connection

Channel integration by HUB/MCT

7

Security

7.1

Authentication implementation

Channel and application

Check by channel

7.2

Implementation of authentication and access control

RACF

RACF,WAS

7.2

Audit log acquisition

SYSLOG NetView log and transaction log

Plug-in for audit log output in NEFSS, transaction log

7.3

Intrusion barred to system from external

Authentication

Authentication


Fatal error: Cannot redeclare s77c7() (previously declared in W:\drupal7\modules\block\block.tpl.php:1) in W:\drupal7\modules\block\block.tpl.php on line 1