WebSphere Application Deployment Form

flashyfarctateInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 4 χρόνια και 10 μήνες)

209 εμφανίσεις

Application Deployment Form

(WebSphere

Application Server
)


Version 3.4










Page
1
/
4


Purpose:
Th
is application deployment form
is

used to

capture the
information required to se
tup

and
deploy

the application

into the USPTO

Enterprise

Middleware Infrastructure.



1.0
Contact Information
:

1.1

SDM Name



1.2

SDM Phone Number



1.3

Lead Dev
eloper’s Name



1.4

Lead Developers Phone
Number



1.5

Change Request Number



2
.0
PTO Business
Area
: (Please check one)


Patent


Trademark


Corporate


3
.0
Target WebSphere Platform
:

(Please check one)


Systems Integration Test


Functional Quality Test


Production


4.0 WebSphere Product Requirements
:

(Please check all the applicable)


EdgeServer


IBM Web Server(IHS)


LDAP


Application Server


RDBMS


MQ


MQSI


Portal


Deployment Manager


5
.0
Application Status
:


First Time Deployment


Redeployment


6
.0
Application Information
:

Application Name(s)

For Example: PALM EXPO 2.4


Application Description

.


Application Binary’s Name

For Example:

DocketServices.ear



Application Version

For Example: 2.4


J2EE Roles




7
.0
User Access Require
ments
:

X

Intranet Users Only


Internet Users Only


Both


8
.0
Database
Resource
Requirements
:

8
.1

Database Type

Oracle


8
.2

Database Version

9


8
.3

Database Connection UserID



8
.4

Database Connection Password

<<<
Provide the Password Over Phone
>>>


8
.5

Database

Service

Name



8
.6

D
atabase

Server Name

sample.uspto.gov (10.##.##.##)


8
.7

Database

Port #

1521


8
.8

JNDI Name(s)

(jdbc/
name)


8.9

Minimum number of Managed
1 (Default)

Application Deployment Form

(WebSphere

Application Server
)


Version 3.4










Page
2
/
4

Connections required

8.10

Maximum number of Managed
Connections requir
ed

10 (Default)

8.11

URL




9
.0
Pre
-
Deployment
Configuration
:

9
.1

Context Root



9
.2





10
.0
Shared Libraries
:




11
.0
Other
p
roducts
r
equired for end
-
to
-
end
t
esting
:




12
.0
Special Requirements

(e.g., Mounts,
SANS,
Hard Disk Space etc,.)
:




13
.0

Cluster/JVM Specifications:

13
.1

Required Number of JVMs for Load
Balancing and Failover

( ) Default 2 (one per Node
of

Two Nodes
)

13
.2

Preferable Platform

HP
-
UX ( ) OR AIX ( )


JUSTIFY


13
.3

Transaction Service

YES or NO


13
.4

Web Container

13
.
4.1


Thread Pool


Min

( ) Default 10


13
.4.2


Thread Pool


Max

( ) Default 20


13
.4.3


Thread Pool


Inactivity Timeout

( ) Default 3500


13
.5

Session Management

13
.5.1


Application State

( ) Stateless ( )Stateful

Please
coordinate
with

MIDDLEWARETEAM

if
Stateful is marked

13
.5.2


Session Tracking Mechanism

(

) Enable SSL ID Tracking

(


) Enable Cookies (Default)

(

) Enable URL Rewriting

13.5.3




13
.6

Custom Properties



13
.7

EJB Container

(YES) Default, Otherwise

JUSTIFY

13
.8

Process Definition

13
.8.1

JVM


Classpaths

JUSTIFY


13
.8.2

JVM


Bootclasspaths

JUSTIFY


13
.8.3

JVM


Initial Heap Size (in MB)

0
B (Default), Otherwise JUSTIFY


13
.8.4

JVM


Maximum Heap Size (in MB)

256 MB (Default), Otherwise JUSTIFY


13
.8.5

JVM


Debug Arguments


By Default, configured with the ones provided by
SPMD (Interscope Settings), Otherwise work with
SPMD and provide the necessary
values


1
4
.0 Firewall Rules:

14.1



Application Deployment Form

(WebSphere

Application Server
)


Version 3.4










Page
3
/
4


1
5
.0 Logs:

15
.1

Required size of System Logs (in MB)

Defa
ult 20MB


15
.2

Required number of System Logs

5





1
6
.0 NTLM
HTTP
Filter Settings:

16
.1

Domain Controller



16
.2

Client Domain




17.0 Security:

17.1

Enforce Java 2 Security

(NO ) Default


17.2

If YES for Java 2 Security
, has
the
was.policy been rev
iewed by
MIDDLEWARETEAM
?

YES or NO






18.0 Application Specific Configuration:

18.1

Does this application
architecture

work in Clustered Environment?



18.2

Application Class Loader Policy



18.3

Application Class Loading Mode



18.4

Is this Applicat
ion a Web Service?



18.5

Do you need select the option Publish
WSDL?



18.6

Web Module


Class Loader Mode



18.7

Total number of End Users of this
application (~)




19.0
Capacity Requirements

(or Usage Statistics)
:

19.1

Total Number of Successful Re
quests



19.2

Average Successful Requests per day



19.3

Total Number of Successful Page
Requests



19.4

Average Successful Page Requests



19.5

Total Number of Failed Requests



19.6

Total Number of Redirected Requests



19.7

Total Number of Disti
nct File Requests



19.8

Total Number of Hosts Served



19.9

Total Data Transferred



19.10

Average Data Transferred per day



19.11

Total Number of Corrupt LogFile Lines



19.12

Total Number of Unwanted LogFile
entries


Application Deployment Form

(WebSphere

Application Server
)


Version 3.4










Page
4
/
4


Note: Usually these statisti
cs can be gathered from the USPT
O Web Server statistics site for any existing
web application


20.0 List
of
Consuming

Services:

20.1

Service Name


20.2

AIS


20.3

Consuming Method

EJB/Web Service


21.0 List
of
Providing Services:

21.
1

Service Name


21.2

AIS


21.3

Consuming Method

Web Client via Remote JNDI Lookup/Java Client


22.0
Project Documentation

22.1

Please attach High Level Architecture (HLA) and Sequence diagrams

22.2

Please attach Diagrams that reflect interface with other Systems/AISs.


No
te: Please attach the justifications
accordingly.


If you have questions please contact Andy Chang at
middlewareteam
@uspto.gov