ESB and Enterprise Architecture

Logical and Physical architecture:

The logical architecture is a more detailed structure defines what has to be done to support the user services. It defines the processes that perform functions and the information or data flows that are shared between these processes. Logical architecture do not include physical server names or addresses. They do include any business services, application names and details, and other relevant information for development purposes.



A physical architecture has all major components and entities identified within specific physical servers and locations or specific software services, objects, or solutions. Include all known details such as operating systems, version numbers, and even patches that are relevant. Any physical constraints or limitations should also be identified within the server components, data flows, or connections. This design usually precludes or may be included and extended by the final implementation team into an implementation design.




I like these links, i have tried to compile various links at one place...

http://www.youtube.com/watch?v=Zmp5Pi4CFDw

http://www.youtube.com/watch?v=H72s78so6DM

http://www.youtube.com/watch?v=WI8P4YYubAw&NR=1

http://www.youtube.com/watch?v=1yUvonES0Gk&feature=related

Enterprise Architecture:

Zachman Framework:
https://apps.adcom.uci.edu/EnterpriseArch/Zachman/

NIST EA Model:
http://www.cio.gov/Documents/fedarch1.pdf

Department of Defence Architecture Framework (DoDAF):
http://www.defenselink.mil/cio-nii/docs/DoDAF_v1_Volume_I.pdf

Treasurey Enterprise Architecture Framework (TEAF):
http://www.eaframeworks.com/TEAF/teaf.doc

Federal Enterprise Architecture (FEA) Reference Models:
http://www.gao.gov/bestpractices/bpeaguide.pdf

National Association of State CIO (NASCIO) Enterprise Architecture:
http://www.nascio.org/advocacy/washWatch/documents/whitepaper_07-03EnterpriseArchitecture.pdf

Database configuration on WAS

Configure DB2/Oracle type 4 driver on WEBSPHERE Application SERVER

Assumptions are followings:
i. All below mentioned required jars should be available.

1. classes12.jar
2. db2java.zip
3. db2jcc.jar
4. db2jcc_javax.jar
5. db2jcc_license_cisuz.jar
6. db2jcc_license_cu.jar
ii. All database authentications should be configured.
Login to WAS server:

STEPS -A- Creating JDBC provider
goto resources--> JDBC Providers --> Click on new
select Step 1- DB2
select Step 2- DB2 Universal JDBC Driver provider
select Step 3- XA Data source
click on Next --> new screen will be displayed apply the changes and save it.

STEPS -B -Creating Data sourcegoto resources--> JDBC Providers --> DB2 Universal JDBC Driver provider (XA) --> Data Source
select Step 1--> Enter the data source name (Two data source name can not be the same)
example-- testdatasourcename select Step 2--> Enter the JNDI name
example -- jdbc/testdatasourcename (It can be anything)
select Step 3--> select database authentication name (should be created before this configuration, so it can be selected from the option)
select Step 4--> Enter the DB2 data source properties
a. Database Name --> DB2TestName
b. Driver Type --> 4
c. Server Name --> TestServerName ((It will be the database server name)
d. Port Name --> 12345678 (It will be the port number)
click on Apply--> apply the changes and save it.

STEPS -C - Setting Environment variables
Enter the full path of the jars which can be places any where on the server and accesses by that user id and password
Select Environment --> Websphere variables
selects Step 1--> select DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATHexm: /usr/IBM/WebSphere/AppServer/profiles/profileservername/lib
selects Step 2--> select DB2UNIVERSAL_JDBC_DRIVER_PATH
exm: /usr/IBM/WebSphere/AppServer/profiles/profileservername/lib
selects Step 3--> select DB2_JDBC_DRIVER_PATH
exm: /usr/IBM/WebSphere/AppServer/profiles/profileservername/lib


Apply all changes and save it.

Restart the server and test the applications.

Creating New websphere instance on WAS Server6.1

1. Get the server name from unix team.

2. Login in to the WAS (Websphere Application Server) using unix id and password

3. User id should have full access for this instance

4. It should not have any pre existing directories (lost-found or any other)

5. Let assume profile name is testserver

a. Changes directory to /usr/IBM/WebSphere/AppServer/bin/
Run the command wasprofile.sh with defined parameter.

wasprofile.sh -create -profileName testserver -profilePath /usr/IBM/WebSphere/AppServer/profiles/testserver -templatePath /usr/IBM/WebSphere/AppServer/profileTemplates/default -hostName -nodeName testservernode -cellName testservercell -startingPort <portNumber>

Port number can not be more than 64000.

I have created this blog to put Technical, Project Management and community information. All thoughts about these topics.