Top Banner
WHITEPAPER ON| OSS APPLICATION SERVER (ASP.NET) 1 Version: ASP.NET (3), vg Updated: 3Q/200 Reference: Middleware 0100/88 OSS © APPLICATION SERVER (ASP.NET/3.0), R3 MIDDLEWARE APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS & DESCRIPTIONS
19

APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

Jul 25, 2020

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

1

Version ASPNET (3) vg Updated 3Q200

Reference Middleware 010088

OSS copy

APPLICATION SERVER (ASPNET30) R3 MIDDLEWARE

APPLICATION SPECIFICATIONS FEATURES

SCREEN SHOTS amp DESCRIPTIONS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

2

CONTENT DESCRIPTION 1 APPLICATION MIDDLEWARE INTRODUCTION amp BUSINESS APPLICATIONS

11 INTRODUCTION 12 BUSINESS APPLICATIONS

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING CODES 22 DATABASE 23 APPLICATION MIDDLEWARE ARCHITECTURE 24 HARDWARE ARCHITECTURE 25 OPERATING SYSTEM (OS)

3 APPLICATION INTRODUCTION ARCHITECTURAL TOPOLOGY SPECIFICATIONS

FEATURES AND SCREEN SHOTS DESCRIPTION

31 ALICATION SOLUTIONrsquoS ARCHITECTURE amp TOPOLOGY 32 HARDWARE DEPLOYMENT BASED ON BASE HIGH AVAILABILITY 33 HARDWARE DEPLOYMENT FOR VOLUMINOUS LOADS 34 OVERALL DIAGRAM CO-HABITATION BETWEEN HARDWARE AND APPLICATION

SOLUTION

4 APP-MIDDLEWARErsquoS FEATURE DESCRIPTION SCREEN SHOT ILLUSTRATION amp WEB SERVICES EXAMPLES

41 FEATURE amp SPECIFICATION DESCRIPTIONS 42 SCREEN SHOT ILLUSTRATIONS

43 WEB SERVICES (SOAP) EXAMPLES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

3

1 APP-SERVERrsquoS INTRODUCTION amp BACKGROUND INFORMATION 11 INTRODUCTION

The Application middleware OSS copy APPLICATION SERVERS (ASPNET) is written in Microsoft Visual StudioNET (30 2005) whose architectural platforms are adhered to N-Tier and SOArsquos In this article we use the terms App-Server or Application Middleware inter-exchange ably as they meant the same The Application Middleware is essentially a middleware host which provides diverse services thru a central SOA Enclosure These services can be deployed either as a stand-alone or integrated Component Services The Component Services whose services can be rendered thru dedicated Web Services thru SOAPWSDL Some of these Component Services are A Single Sign-In B Access Right Allocation C Audit Trace amp Track D Encryption Service E Alert Gateway Services (SMSEmail) F Quantitative Control for Global Setting Services G System Security H Identity Management I Web Services amp Others For details please refer to Section 3 later As the name implies the Application Serverrsquos core functions are to provide the centralized re-usable services (such as Single Sign-In Identity Management and Access File Right Allocation) to its primary clients Application like ERP Accounting HR CRM and others where all the later can be hosted at cluster-server environment How do the two (the Application Middleware and third-partyrsquos Application Solutions) interface with each other As long the third-party App Solutions are adhered to web services (SOAP Schema) they can send request query and receive request via the prevailing text-based messaging using XML and http To understand this please refer to [Section 43]

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

4

12 BUSINESS APPLICATIONS

As the Application Middlewarersquos Service Components are diverse in terms of functionalities and feature-rich it is recommended for enterprise-clients whose business requirements share one or more the following conditions A DISTRIBUTED AND HETEROGENEOUS IT SYSTEM

The App-Server is best suited for enterprises whose IT resources support thousands of users heterogeneous system (multiple technology platforms OS and databases) and are running on Cluster-Server environment The App-Server provides a meaningful cost saving and ease of central management for System Administrators for tasks like to administrate the single sign-in enforce corporate security administrate access-control audit trace all logon users and others

B REGULATORY COMPLIANCE AND FULFILLMENTS

For certain industries such as financial services security-broker fund-management trust and military with national-security concerned sectors the effort of protecting the end-usersrsquo identities as well as virtual defending from malicious thefts are required under various national regulatory frameworks

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

5

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING TOOLS The Application Middlewarersquos source codes were written in A Microsoft Visual StudioNET (ASPNET amp VBNET) B IIS (NET Framework 35) and C AJAX

22 RELATIONSHIP DATABASE MANAGEMENT SYSTEM (DATABASE)

The App-Server has a built-in a middleware OSS copy Data Access Layer which it supports clients to deploy any RDMS database (Oracle 10 11g MS SQL 20002005 IBM DB2 or My SQL) to the underlying Applications Here are the some examples how it can be connected to various databases

a Connecting to Oracle 10g11g thru Oracle Data ProviderNET (ODPNET) b Connect to MS SQL 20002005 thru SQL Data ProviderNET c Connecting to My SQL thru MYSQL_Provider and d Connecting to IBM DB2 thru IBMrsquos OLE DB Provider

23 APPLICATION MIDDLEWARErsquoS ARCHITECTURE

The App Middlewarersquos architectural platforms are adhered to A N-TIER

The App Middlewarersquos codes are designed in N-Tier and thus it can be logically spread across different types of servers under the clustering environment Due to this capability it inherently provides the robust features of Failover High Availability (HA) and Scalability to the third-party Applications when being deployed together

B SOA (Services Orient Architecture)

The Application Middleware contains many stand-alone Service Components whose services can be extracted thru a SOA concept Its framework enables Application Developers to extract the specific Service Components to be integrated with their underlying features for quick and speed deployment purposes

For the non-intrusive method App Developers can extract such ready-made services thru Web Services via SOAP (xmlhttp) from the SOA Enclosure

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

6

24 HARDWARE ARCHITECTURE

As Application Middleware supports N-tier clients can deploy it at either a simple stand-alone or clustering environment For various options please refer to Section 33 and 34 below

25 SERVER (OS) OPERATING SYSTEM

A Microsoft Windows Server 200320052008 (Enterprise Edition) for OSS copy

Application Server (ASPNET) or

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 2: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

2

CONTENT DESCRIPTION 1 APPLICATION MIDDLEWARE INTRODUCTION amp BUSINESS APPLICATIONS

11 INTRODUCTION 12 BUSINESS APPLICATIONS

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING CODES 22 DATABASE 23 APPLICATION MIDDLEWARE ARCHITECTURE 24 HARDWARE ARCHITECTURE 25 OPERATING SYSTEM (OS)

3 APPLICATION INTRODUCTION ARCHITECTURAL TOPOLOGY SPECIFICATIONS

FEATURES AND SCREEN SHOTS DESCRIPTION

31 ALICATION SOLUTIONrsquoS ARCHITECTURE amp TOPOLOGY 32 HARDWARE DEPLOYMENT BASED ON BASE HIGH AVAILABILITY 33 HARDWARE DEPLOYMENT FOR VOLUMINOUS LOADS 34 OVERALL DIAGRAM CO-HABITATION BETWEEN HARDWARE AND APPLICATION

SOLUTION

4 APP-MIDDLEWARErsquoS FEATURE DESCRIPTION SCREEN SHOT ILLUSTRATION amp WEB SERVICES EXAMPLES

41 FEATURE amp SPECIFICATION DESCRIPTIONS 42 SCREEN SHOT ILLUSTRATIONS

43 WEB SERVICES (SOAP) EXAMPLES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

3

1 APP-SERVERrsquoS INTRODUCTION amp BACKGROUND INFORMATION 11 INTRODUCTION

The Application middleware OSS copy APPLICATION SERVERS (ASPNET) is written in Microsoft Visual StudioNET (30 2005) whose architectural platforms are adhered to N-Tier and SOArsquos In this article we use the terms App-Server or Application Middleware inter-exchange ably as they meant the same The Application Middleware is essentially a middleware host which provides diverse services thru a central SOA Enclosure These services can be deployed either as a stand-alone or integrated Component Services The Component Services whose services can be rendered thru dedicated Web Services thru SOAPWSDL Some of these Component Services are A Single Sign-In B Access Right Allocation C Audit Trace amp Track D Encryption Service E Alert Gateway Services (SMSEmail) F Quantitative Control for Global Setting Services G System Security H Identity Management I Web Services amp Others For details please refer to Section 3 later As the name implies the Application Serverrsquos core functions are to provide the centralized re-usable services (such as Single Sign-In Identity Management and Access File Right Allocation) to its primary clients Application like ERP Accounting HR CRM and others where all the later can be hosted at cluster-server environment How do the two (the Application Middleware and third-partyrsquos Application Solutions) interface with each other As long the third-party App Solutions are adhered to web services (SOAP Schema) they can send request query and receive request via the prevailing text-based messaging using XML and http To understand this please refer to [Section 43]

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

4

12 BUSINESS APPLICATIONS

As the Application Middlewarersquos Service Components are diverse in terms of functionalities and feature-rich it is recommended for enterprise-clients whose business requirements share one or more the following conditions A DISTRIBUTED AND HETEROGENEOUS IT SYSTEM

The App-Server is best suited for enterprises whose IT resources support thousands of users heterogeneous system (multiple technology platforms OS and databases) and are running on Cluster-Server environment The App-Server provides a meaningful cost saving and ease of central management for System Administrators for tasks like to administrate the single sign-in enforce corporate security administrate access-control audit trace all logon users and others

B REGULATORY COMPLIANCE AND FULFILLMENTS

For certain industries such as financial services security-broker fund-management trust and military with national-security concerned sectors the effort of protecting the end-usersrsquo identities as well as virtual defending from malicious thefts are required under various national regulatory frameworks

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

5

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING TOOLS The Application Middlewarersquos source codes were written in A Microsoft Visual StudioNET (ASPNET amp VBNET) B IIS (NET Framework 35) and C AJAX

22 RELATIONSHIP DATABASE MANAGEMENT SYSTEM (DATABASE)

The App-Server has a built-in a middleware OSS copy Data Access Layer which it supports clients to deploy any RDMS database (Oracle 10 11g MS SQL 20002005 IBM DB2 or My SQL) to the underlying Applications Here are the some examples how it can be connected to various databases

a Connecting to Oracle 10g11g thru Oracle Data ProviderNET (ODPNET) b Connect to MS SQL 20002005 thru SQL Data ProviderNET c Connecting to My SQL thru MYSQL_Provider and d Connecting to IBM DB2 thru IBMrsquos OLE DB Provider

23 APPLICATION MIDDLEWARErsquoS ARCHITECTURE

The App Middlewarersquos architectural platforms are adhered to A N-TIER

The App Middlewarersquos codes are designed in N-Tier and thus it can be logically spread across different types of servers under the clustering environment Due to this capability it inherently provides the robust features of Failover High Availability (HA) and Scalability to the third-party Applications when being deployed together

B SOA (Services Orient Architecture)

The Application Middleware contains many stand-alone Service Components whose services can be extracted thru a SOA concept Its framework enables Application Developers to extract the specific Service Components to be integrated with their underlying features for quick and speed deployment purposes

For the non-intrusive method App Developers can extract such ready-made services thru Web Services via SOAP (xmlhttp) from the SOA Enclosure

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

6

24 HARDWARE ARCHITECTURE

As Application Middleware supports N-tier clients can deploy it at either a simple stand-alone or clustering environment For various options please refer to Section 33 and 34 below

25 SERVER (OS) OPERATING SYSTEM

A Microsoft Windows Server 200320052008 (Enterprise Edition) for OSS copy

Application Server (ASPNET) or

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 3: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

3

1 APP-SERVERrsquoS INTRODUCTION amp BACKGROUND INFORMATION 11 INTRODUCTION

The Application middleware OSS copy APPLICATION SERVERS (ASPNET) is written in Microsoft Visual StudioNET (30 2005) whose architectural platforms are adhered to N-Tier and SOArsquos In this article we use the terms App-Server or Application Middleware inter-exchange ably as they meant the same The Application Middleware is essentially a middleware host which provides diverse services thru a central SOA Enclosure These services can be deployed either as a stand-alone or integrated Component Services The Component Services whose services can be rendered thru dedicated Web Services thru SOAPWSDL Some of these Component Services are A Single Sign-In B Access Right Allocation C Audit Trace amp Track D Encryption Service E Alert Gateway Services (SMSEmail) F Quantitative Control for Global Setting Services G System Security H Identity Management I Web Services amp Others For details please refer to Section 3 later As the name implies the Application Serverrsquos core functions are to provide the centralized re-usable services (such as Single Sign-In Identity Management and Access File Right Allocation) to its primary clients Application like ERP Accounting HR CRM and others where all the later can be hosted at cluster-server environment How do the two (the Application Middleware and third-partyrsquos Application Solutions) interface with each other As long the third-party App Solutions are adhered to web services (SOAP Schema) they can send request query and receive request via the prevailing text-based messaging using XML and http To understand this please refer to [Section 43]

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

4

12 BUSINESS APPLICATIONS

As the Application Middlewarersquos Service Components are diverse in terms of functionalities and feature-rich it is recommended for enterprise-clients whose business requirements share one or more the following conditions A DISTRIBUTED AND HETEROGENEOUS IT SYSTEM

The App-Server is best suited for enterprises whose IT resources support thousands of users heterogeneous system (multiple technology platforms OS and databases) and are running on Cluster-Server environment The App-Server provides a meaningful cost saving and ease of central management for System Administrators for tasks like to administrate the single sign-in enforce corporate security administrate access-control audit trace all logon users and others

B REGULATORY COMPLIANCE AND FULFILLMENTS

For certain industries such as financial services security-broker fund-management trust and military with national-security concerned sectors the effort of protecting the end-usersrsquo identities as well as virtual defending from malicious thefts are required under various national regulatory frameworks

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

5

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING TOOLS The Application Middlewarersquos source codes were written in A Microsoft Visual StudioNET (ASPNET amp VBNET) B IIS (NET Framework 35) and C AJAX

22 RELATIONSHIP DATABASE MANAGEMENT SYSTEM (DATABASE)

The App-Server has a built-in a middleware OSS copy Data Access Layer which it supports clients to deploy any RDMS database (Oracle 10 11g MS SQL 20002005 IBM DB2 or My SQL) to the underlying Applications Here are the some examples how it can be connected to various databases

a Connecting to Oracle 10g11g thru Oracle Data ProviderNET (ODPNET) b Connect to MS SQL 20002005 thru SQL Data ProviderNET c Connecting to My SQL thru MYSQL_Provider and d Connecting to IBM DB2 thru IBMrsquos OLE DB Provider

23 APPLICATION MIDDLEWARErsquoS ARCHITECTURE

The App Middlewarersquos architectural platforms are adhered to A N-TIER

The App Middlewarersquos codes are designed in N-Tier and thus it can be logically spread across different types of servers under the clustering environment Due to this capability it inherently provides the robust features of Failover High Availability (HA) and Scalability to the third-party Applications when being deployed together

B SOA (Services Orient Architecture)

The Application Middleware contains many stand-alone Service Components whose services can be extracted thru a SOA concept Its framework enables Application Developers to extract the specific Service Components to be integrated with their underlying features for quick and speed deployment purposes

For the non-intrusive method App Developers can extract such ready-made services thru Web Services via SOAP (xmlhttp) from the SOA Enclosure

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

6

24 HARDWARE ARCHITECTURE

As Application Middleware supports N-tier clients can deploy it at either a simple stand-alone or clustering environment For various options please refer to Section 33 and 34 below

25 SERVER (OS) OPERATING SYSTEM

A Microsoft Windows Server 200320052008 (Enterprise Edition) for OSS copy

Application Server (ASPNET) or

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 4: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

4

12 BUSINESS APPLICATIONS

As the Application Middlewarersquos Service Components are diverse in terms of functionalities and feature-rich it is recommended for enterprise-clients whose business requirements share one or more the following conditions A DISTRIBUTED AND HETEROGENEOUS IT SYSTEM

The App-Server is best suited for enterprises whose IT resources support thousands of users heterogeneous system (multiple technology platforms OS and databases) and are running on Cluster-Server environment The App-Server provides a meaningful cost saving and ease of central management for System Administrators for tasks like to administrate the single sign-in enforce corporate security administrate access-control audit trace all logon users and others

B REGULATORY COMPLIANCE AND FULFILLMENTS

For certain industries such as financial services security-broker fund-management trust and military with national-security concerned sectors the effort of protecting the end-usersrsquo identities as well as virtual defending from malicious thefts are required under various national regulatory frameworks

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

5

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING TOOLS The Application Middlewarersquos source codes were written in A Microsoft Visual StudioNET (ASPNET amp VBNET) B IIS (NET Framework 35) and C AJAX

22 RELATIONSHIP DATABASE MANAGEMENT SYSTEM (DATABASE)

The App-Server has a built-in a middleware OSS copy Data Access Layer which it supports clients to deploy any RDMS database (Oracle 10 11g MS SQL 20002005 IBM DB2 or My SQL) to the underlying Applications Here are the some examples how it can be connected to various databases

a Connecting to Oracle 10g11g thru Oracle Data ProviderNET (ODPNET) b Connect to MS SQL 20002005 thru SQL Data ProviderNET c Connecting to My SQL thru MYSQL_Provider and d Connecting to IBM DB2 thru IBMrsquos OLE DB Provider

23 APPLICATION MIDDLEWARErsquoS ARCHITECTURE

The App Middlewarersquos architectural platforms are adhered to A N-TIER

The App Middlewarersquos codes are designed in N-Tier and thus it can be logically spread across different types of servers under the clustering environment Due to this capability it inherently provides the robust features of Failover High Availability (HA) and Scalability to the third-party Applications when being deployed together

B SOA (Services Orient Architecture)

The Application Middleware contains many stand-alone Service Components whose services can be extracted thru a SOA concept Its framework enables Application Developers to extract the specific Service Components to be integrated with their underlying features for quick and speed deployment purposes

For the non-intrusive method App Developers can extract such ready-made services thru Web Services via SOAP (xmlhttp) from the SOA Enclosure

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

6

24 HARDWARE ARCHITECTURE

As Application Middleware supports N-tier clients can deploy it at either a simple stand-alone or clustering environment For various options please refer to Section 33 and 34 below

25 SERVER (OS) OPERATING SYSTEM

A Microsoft Windows Server 200320052008 (Enterprise Edition) for OSS copy

Application Server (ASPNET) or

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 5: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

5

2 TECHNICAL SPECIFICATIONS

21 PROGRAMMING TOOLS The Application Middlewarersquos source codes were written in A Microsoft Visual StudioNET (ASPNET amp VBNET) B IIS (NET Framework 35) and C AJAX

22 RELATIONSHIP DATABASE MANAGEMENT SYSTEM (DATABASE)

The App-Server has a built-in a middleware OSS copy Data Access Layer which it supports clients to deploy any RDMS database (Oracle 10 11g MS SQL 20002005 IBM DB2 or My SQL) to the underlying Applications Here are the some examples how it can be connected to various databases

a Connecting to Oracle 10g11g thru Oracle Data ProviderNET (ODPNET) b Connect to MS SQL 20002005 thru SQL Data ProviderNET c Connecting to My SQL thru MYSQL_Provider and d Connecting to IBM DB2 thru IBMrsquos OLE DB Provider

23 APPLICATION MIDDLEWARErsquoS ARCHITECTURE

The App Middlewarersquos architectural platforms are adhered to A N-TIER

The App Middlewarersquos codes are designed in N-Tier and thus it can be logically spread across different types of servers under the clustering environment Due to this capability it inherently provides the robust features of Failover High Availability (HA) and Scalability to the third-party Applications when being deployed together

B SOA (Services Orient Architecture)

The Application Middleware contains many stand-alone Service Components whose services can be extracted thru a SOA concept Its framework enables Application Developers to extract the specific Service Components to be integrated with their underlying features for quick and speed deployment purposes

For the non-intrusive method App Developers can extract such ready-made services thru Web Services via SOAP (xmlhttp) from the SOA Enclosure

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

6

24 HARDWARE ARCHITECTURE

As Application Middleware supports N-tier clients can deploy it at either a simple stand-alone or clustering environment For various options please refer to Section 33 and 34 below

25 SERVER (OS) OPERATING SYSTEM

A Microsoft Windows Server 200320052008 (Enterprise Edition) for OSS copy

Application Server (ASPNET) or

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 6: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

6

24 HARDWARE ARCHITECTURE

As Application Middleware supports N-tier clients can deploy it at either a simple stand-alone or clustering environment For various options please refer to Section 33 and 34 below

25 SERVER (OS) OPERATING SYSTEM

A Microsoft Windows Server 200320052008 (Enterprise Edition) for OSS copy

Application Server (ASPNET) or

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 7: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

7

3 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE amp TOPOLOGY 31 APPLICATION SERVERrsquoS SYSTEM ARCHITECTURE

As explained above the App Middlewarelsquos architectural platforms are designed and adhered to N-Tier and SOA The following diagram depicts the said capabilities where

A N-Tier Its source codes can be logically spread over different layers of servers when

deployed in clustering environment The diagram below depicts the codes can be hosted in 3 layers namely web application and databasersquos and

B SOA The App Serverrsquos service components are all hosted centrally where most are logically at Application Server Some of the depicted Service Components are Single Sign-In Encryption Audit Trace Alert Gateway Services LDAP and others

Web Tier

OSS Enterprise Service Portal or Client Existing Fixed IP Webpage

System Security OSS Access Control Manager amp Session Manager

LDAP

Optional ndash Archival

ndash Alert Management

ndash Work Flow ndash Business Intelligence

API

Audit Trail

RSA Encryption Authentication

Authorization

Service Components

OSS Data Access Layer (DAL)

Application Components

Application-1 Application-2 Application-3

Other RDBMS IBM DB2 Oracle Microsoft SQL

20055

Back-up Software

External Data Storage Device [SAN NSATape]

Optional Second Data Centre For Back-Up + Recovery

OSS Administration

Module [Dictionary]

Application

Tier

Database Tier

Internal Users External Users

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 8: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

8

32 HARDWARE DEPLOYMENT BASED ON HA (High Availability)

As the Application Middleware is architected in N-tier it supports clients to deploy it in layered based (or tier-based) hardware deployment (or Cluster-Server environment) which in turn supports High Availability (HA) and Scalability The following 3 sections (from Section 32 to 34) are to illustrate how it can be deployed if clients configure it in Cluster-Server Environment The diagram below (FIGURE 32) depicts the typically clear cut of tier separation among Web Server Application Server and Database Servers At this configuration it is capable to support approximate 100 concurrent (users) load provided certain hardware specification

FIGURE 32

Database Server (Active Node)

HARDWARE TOPOLOGY BASIC HIGH AVAILABILITY AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

Database ServerSwitch

Internet Service

Provider (2 Mbp x

2)

Disaster Recovery Centre (DRC) OPTIONAL

Web-cum-

Application

Servers

Load

Balancer

Application

Servers

Web Servers with

built-in Network

Load Balancer

33 HARDWARE DEPLOYMENT FOR VOLUMINOUS CONCURRENT LOG-INS

The diagram below (FIGURE 33) depicts the higher scalability from the base in FIGURE 32rsquos

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 9: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

9

At the current prevailing technology based on Windows Server 20052008rsquos the hardware configuration can be scaled up to form a 32 units of Web servers b 12 Application Servers c 2 Database Servers and d 2 redundant Gigabyte Switches The higher scaled-up design is capable to support up to 15000 concurrent users at any given time

FIGURE 33

Database Server (Active Node)

HARDWARE TOPOLOGY AND OVERVIEW MAXIMUM SCALE-UP AT SINGLE-NODE LOCATION

Database Server (Passive Node)

Primary Data Storage SAN NAS

Remote-Backup SANNAS Server

`

1

2

3

4

5

6

7

8

9

10

11

12

Redundant Gigabit

Switch (1)

Redundant Gigabit

Switch (2)

Optional

Hardware

Based Load

Balancer

Switch for redundancy-1

Switch for redundancy-2

Primary Data Centre Single Logical DNS

1

2

3

4

5

6

Database ServerSwitch

Internet Service

Provider (2 Mbp x 2)Disaster Recovery Centre (DRC)

Web-cum-Application

ServersLoad

Balancer

Up to 12 Application

Servers

Up to 32 Web Servers

with built-in Network

Load Balancer

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 10: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

10

34 OVERALL DIAGRAM OF COHABITATION BETWEEN APPLICATION SOFTWARE AND HARDWARE

The following diagram depicts the logical locations when the said clustered hardware

and N-Tier based App software are deployed

TOPOLOGY ON HARDWARE AND APPLICATION SOFTWARE DEPLOYMENT amp CONFIGURATION

`

Application

Server

Web

Servers

Switch-1 Switch-2

Database

Server

Active Node Passive Node

End-Users

SANNAS

BACK-UP

System Security Access Control

Manager amp Session Control

Application

Software-1

Application

Software-2

Application

Software-3

Application Infrastructure Building Block Access Control

Encryption Audit Track Single-Sign_In SMS Report

Portal amp Others

Data Access

Layer (DAL)

Database

END-USERS

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 11: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

11

4 OSS APPLICATION SERVER APP FEATURE DESCRIPTION AND SCREEN SHOT EXAMPLES

41 APP- SERVERrsquoS FEATURE amp SPECIFICATIONSrsquo DESCRIPTIONS

The following paragraphs provide the base description of the generally available services that clients shall expect from App-Server As OSS continuously adds new feature components on the existing one for the latest updates it is best for the readers to contact OSS or authorized resellers directly A SYSTEM SECURITY amp IDENTITY MANAGEMENT

A1 Value-based Policies A2 State-based Policies A3 RSA Encryption A4 Watermark security A5 Restriction of re-print

B CORPORATE GOVERNANCE

B1 Authentication B2 Authorization B3 Audit Trail amp Track

B4 Access Control Module- File Access Right to Application Components B5 LDAP (Lightweight Directory Access Protocol) and Active Directory

B6 Revocation of User Account Module C APPLICATION PORTABILITY MANAGEMENT

C1 Report Portal C2 Business Intelligence (BI) and C3 Digital Right Management

D REMOTE SERVER MONITORING AGENTS via (SNMP) SERVICES This service is to allow clientsrsquo appointed system administrators Facility

Manager (FM) third party Service Provider as well as Management to remotely monitor the cluster server thru a single dashboard management tool which is based on SNMP (Simple Network Management Protocol)

The service supports the remote monitoring as well as provision of data insight

on each hardware in the cluster environments ndash routers switches servers (web application and database servers) SANNAS firewall and others ndash at any given time and date

E WEB SERVICES

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 12: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

12

This service is to provide comprehensive data interchange capabilities to

Application Developers who intend to integrate data among various system via a SOAPWSDL technology At the [Section 43] below there are few examples to showcase hot they are being use to achieve such purpose

42 APPLICATION SERVERrsquoS SCREEEN SHOT EXAMPLES

421 SYSTEM SECURITY amp CORPORATE GOVERNANCE This screen shot illustrates the policy enforcementrsquos capabilities the System Administrator can deploy to streamline and dashboard manage all the logon users remotely via a web browser and internet connection

Some of the common System Security features are

01 Value-based Policies ndash such as minimum lengths and the presence of a

minimum number f special characters and 02 State-based Policies ndash such as expiration and maximum number of re-

tries before being block out from access

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 13: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

13

422 AUDIT TRACE This screen shot depicts the Application Server provides comprehensive audit tracking on each logon userrsquos behavior The tracing can be detailed up to date time and actions (create delete amend save update print and export)

423 LDAP (Lightweight Directory Application Protocol) This screen shot illustrates that the Application Server support clients to deploy it in compliance with the HQ LDAP control This feature eliminates the need to re-keying in the usersrsquo particulars to each new Application Solution

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 14: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

14

424 ASSIGNING USER RIGHT TO RESOURCES This screen shot illustrates how the System Administrators to assign a particular user to access the designated Application Solutions and their respective files by drag-and-drop function (from left to right)

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 15: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

15

425 SYSTEM ACCESS CONTROL This feature supports System Administrator to administrate manage and allocate Access Right amp Restriction to the logon users in accordance to their designated roles and responsibilities

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 16: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

16

43 WEB SERVICES EXAMPLES

The following explains and depict how the Web Service (SAOP schema) can be deployed thru the App Middleware We use a real life application for the illustration Here are the back-ground information on enterprises which deploys the web services thru the App Server The case involved a sea port operator where it provides various port anchoring services to cargo-ships for import export transit and trans-ship cargo services The main end-users of the App Middleware are the port declaring Agents who are mandated by the relevant authority to provide their services paperless The services that the Agents provide are among other to help their cargo ship-customers to declare importexport shipment online (good name destination ports etc) and pay port-anchoring fees via a web browser and internet connection to the portrsquos secure portal The following are to show the web services rendered for the declaring Agents and the Portrsquos Server The examples of the Web Services showed these two incidents 1 Upon the Agents filed the Import Declaration Form thru the web and paid the

port anchoring fees the App Middleware will send these information (or portrsquos supposed received revenue details) to the respective authority via web services The authority will use these records and check the actual revenue (in 2 below) received all thru seamless web service

2 Once the above (1) transactions have been effected from the declaring agents

the App Middleware will also send the transaction details to the registered financial institutions (which maintain the declaring agentsrsquo account balance) to request the later to debitcredit the port anchoring fee from the declaring agentsrsquo to the portrsquos account

1 REQUEST SOAP MESSAGE The screen illustrated how Portrsquos parent company to send its

request to our Application for extracting certain specific data from date-to-date range with regard to the Portrsquos total collected fees (or total payments received from the declaring agents)

POST OSS_ShipShipDeclarationWebServiceasmx HTTP11

Host localhost Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 17: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

17

ltShipDeclarationForm xmlns=httptempuriorggt ltFromDategtdateTimeltFromDategt ltToDategtdateTimeltToDategt ltShipDeclarationFormgt ltsoap12Bodygt

ltsoap12Envelopegt

2 RPC (REMOTE PROCEDURE CALL) RESPONSE This screen shot illustrates upon receiving the RPC Request our App Middleware sent the following response back to it

HTTP11 200 OK

Content-Type applicationsoap+xml charset=utf-8 Content-Length length ltxml version=10 encoding=utf-8gt ltsoap12Envelope xmlnsxsi=httpwwww3org2001XMLSchema-instance xmlnsxsd=httpwwww3org2001XMLSchema xmlnssoap12=httpwwww3org200305soap-envelopegt ltsoap12Bodygt ltShipDeclarationFormResponse xmlns=httptempuriorggt ltShipDeclarationFormResultgt ltstrAgentgtstringltstrAgentgt ltstrLicensegtstringltstrLicensegt ltstrContactgtstringltstrContactgt ltstrAcct_NumbergtstringltstrAcct_Numbergt ltstrShip_NamegtstringltstrShip_Namegt ltstrShip_Registration_CountrygtstringltstrShip_Registration_Countrygt ltdblShip_TonnagegtdoubleltdblShip_Tonnagegt ltdtEDAgtdateTimeltdtEDAgt ltdtEDDgtdateTimeltdtEDDgt ltstrCurrencyCodegtstringltstrCurrencyCodegt ltdblPort_FeegtdoubleltdblPort_Feegt ltstrPurposegtstringltstrPurposegt ltstrCargo_DescriptiongtstringltstrCargo_Descriptiongt ltintQtygtintltintQtygt ltstrDestonation_CountrygtstringltstrDestonation_Countrygt ltstrDestination_CompanygtstringltstrDestination_Companygt ltShipDeclarationFormResultgt ltShipDeclarationFormResponsegt ltsoap12Bodygt

ltsoap12Envelopegt

1 SOAP MESSAGE FOR DATA EXCHANGE The following example illustrates the SOAP message contents (or responsersquos content) which the App Server relayed back to Portrsquos Authority via Web Services with regard to detailing the RPC content message The contents displayed were in text format

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 18: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

18

The contents contained various information with related to the calling ship at the port for instances

A The Agent name amp contact numbers B The Agentrsquos registered license number with Muara Port C The incoming shiprsquos name country of registration EDA (Estimated Time of

Arrival) and ETD (Estimated Time of Departure) D The payable fee ndash amount and currency denomination E The uploading cargorsquos details ndash part name part quantity and shipment

destination (country and receiving company name)

ltxml version=10 encoding=utf-8 gt - ltShipDeclaration xmlnsxsi=httpwwww3org2001XMLSchema-instance

xmlnsxsd=httpwwww3org2001XMLSchema xmlns=httptempuriorggt ltstrAgentgtXView Transport Agent LtdltstrAgentgt ltstrLicensegtBT-30074-2007ltstrLicensegt ltstrContactgt+65-6845-3400ltstrContactgt ltstrAcct_NumbergtPSA-407456ltstrAcct_Numbergt ltstrShip_NamegtCosco Global IltstrShip_Namegt ltstrShip_Registration_CountrygtChina PRCltstrShip_Registration_Countrygt ltdblShip_Tonnagegt0ltdblShip_Tonnagegt ltdtEDAgt2003-01-03T000000ltdtEDAgt ltdtEDDgt2003-01-05T000000ltdtEDDgt ltstrCurrencyCodegtUSDltstrCurrencyCodegt ltdblPort_Feegt47325ltdblPort_Feegt ltstrPurposegtTo Upload Cargo From SingaporeltstrPurposegt ltstrCargo_DescriptiongtElectronic Goods-PX 4570-07ltstrCargo_Descriptiongt ltintQtygt15750ltintQtygt ltstrDestonation_CountrygtUSAltstrDestonation_Countrygt ltstrDestination_CompanygtSolectron LtdltstrDestination_Companygt

ltShipDeclarationgt

END----

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom

Page 19: APPLICATION SPECIFICATIONS, FEATURES SCREEN SHOTS ... (c... · 4.2 SCREEN SHOT ILLUSTRATIONS 4.3 WEB SERVICES (SOAP) EXAMPLES . ... Application like ERP, Accounting, HR, CRM and others

WHITEPAPER ON| OSS APPLICATION SERVER (ASPNET)

19

[OPEN SPECTRUM SOLUTION]

1 The above information is correct at the time of this article went to print and release on the OSS website OSS reserves the absolute right to alter and change any of them at any given time without notifying the installed clienteles

2 For most updated information on the said application please contract your nearest OSS authorized resellers or logon to wwwopen-speccom for contact and

3 For reporting of error and mistakes at the above articlersquos please send your message to Documentationopen-speccom