HP standard dark template

mongooseriverSoftware and s/w Development

Jun 7, 2012 (5 years and 4 months ago)

494 views

© 2005 Hewlett
-
Packard Development Company, L.P.

The information contained herein is subject to change without notice

e
-
Business

and

Integration

Update

John Ferguson May 2006

Software Business Manager
Session D217/D218

OpenVMS Systems Group


John.L.Ferguson@hp.com

520
-
432
-
4429

March 13, 2013

2

Agenda


Strategy and Technology


Web Services and Services Oriented
Architectures


Updates


General


Product/component


Partner/ISV

March 13, 2013

3

eBusiness and Integration Strategy

Enhance the OpenVMS operating system

with an infrastructure that allows

application, middleware, and data integration

in a global, multi
-
platform environment



In conjunction with it’s partners, OpenVMS has
the tools and technology:


To create the solution to your enterprise
application integration and evolution problem


While leveraging all the strengths of OpenVMS


And protecting your investment

March 13, 2013

4

eBusiness and Integration
Technology


Web servers and browsers


Secure Web Server (Apache)


Secure Web Browser (Mozilla)


Web Services


Simple Object Access Protocol
(SOAP) Toolkit (Apache Axis)


XML Technology (parsers and
stylesheet processors) (Apache)


UDDI Client Toolkit (UDDI4J)


Development tools


Java™ Standard Edition
Development Kit (JDK)


C/C++, COBOL, Fortran, Basic,
Pascal


NetBeans and 3GL plugins


Distributed NetBeans


Application servers


BEA WebLogic Server


Tomcat


Legacy integration


BridgeWorks


Web Services Integration Toolkit
(WSIT)


TP Connector suite


Attunity Connect


WRQ VeraStream


Ericom Host Publisher suite



Middleware


BEA MessageQ


orb2 by 2AB


IBM WebSphere MQ


BEA WebLogic Integration


SpiritSoft


COM


Reliable Transaction Router
(RTR)


Directory services


Enterprise Directory (LDAP,
JNDI)

March 13, 2013

5


Service Oreinted Architecture
and Web Services

March 13, 2013

6

Is an architectural style that provides
a framework through which
organizations describe services and
their behaviour

Is the change from an
object
-
oriented system

to a
service
-
oriented

one;


is an evolutionary idea stemming
from the Internet and Web system

It can be applied equally when
modeling business
, designing the
software to
support the business
,
or describing the
run
-
time
deployment

of the
services

and
associated resources

Service
-
Oriented Architecture


Is the evolution of [Web]

applications into service
-

oriented components with

Web Services.


Is creating convergence between

the business and IT perspective

March 13, 2013

7

SOA: A Business Point of View

Why should I care?


Service Orientation can:


Speed business change


Facilitates business connections


Enhance business control


because SOA creates:


Rapid, flexible business change


Rich, deep business connections


Business and IT feedback and management



SOA Themes


Service Composition/Integration


Service Lifecycle Management


SOA Governance

* Forrester
-

Your Strategic
SOA Platform Vision

March 13, 2013

8

SOA: A Development Point of View

Software Development Trends

Service
Oriented

Reuse Potential

Platform Dependent

No Metadata

Distributed

Platform Dependent

Platform Metadata

Distributed

Platform Independent

Standardized Metadata

Distributed

Object
Oriented

Component
Oriented

March 13, 2013

9

SOA: A Development Point of View

Applications Today


Applications are monolithic


Integration is an after
-
thought


Presentation

Business Logic

Persistence

Integration Interface

(Adapter)

Multi
-
tiered Application

Component

Objects

Legend

Inflexible, not built for integration

March 13, 2013

10

SOA: A Development Point of View

Application as a Service


Large granularity
-

meaningful to consumer


Standards based interface and communication

Presentation

Façade

Business Logic

Façade

Persistence

Cleanly separated and abstracted, ready for integration

March 13, 2013

11

SOA: A Development Point of View


Service Providers


J2EE, .Net, legacy or proprietary can all communicate


WS
-
* interoperability standards (invocation, security, reliability, etc.)

App Server Platform

Component

Execution

Environment

Service

enablement

Tools

Web Service interface layer shields underlying technologies

March 13, 2013

12

Service

Process

SOA: A Development Point of View

Service Consumers

Service A

Service B

Service D

Service C

Application

Applications and Processes are compositions of services


Composed from loosely coupled services and, recursively, itself a service


Interface agreement is dictated, negotiated or
mediated

March 13, 2013

13



OpenVMS and Web Services


Available today:


XML Technology (based on Apache Xerces and Xalan)


XML parsers and XSLT stylesheet processors


SOAP Toolkit (based on Apache Axis)


UDDI Client Toolkit (based on UDDI4J)


Web Services Integration Toolkit (WSIT)


BridgeWorks (Alpha only)

March 13, 2013

14

Web Services Integration Toolkit
(WSIT)


Wraps an OpenVMS 3GL application as a
JavaBean object as part of implementing an
integration solution


Facilitates calling OpenVMS applications from
other technologies such as Microsoft .NET, Java
SE, Java EE, and Web Services


Set of easy to use tools


100% OpenVMS
-
based


Lightweight, separate, reusable, and extensible


Use individually or in combination


Leverage open source technology and standards
including XML, Java, and Apache Velocity

March 13, 2013

15

WSIT V1.0


Available in September 2005


Features:


Supports Integrity and Alpha


Supports C, BASIC, COBOL, ACMS


Creates XML
-
based IDL for the OpenVMS application


Extraction of API definitions from 3GL code


Generates JavaBean object by default


Uses Apache Velocity template for code generation


Customized client generation with modified template


Supports deployment time process management


Choose in
-
process or out
-
process runtime execution

March 13, 2013

16

WSIT V1.1


Available in February 2006


Incremental features:


Focus on ease of use:


Ant scripts to automate development tasks


Sample code (math.c)


Limited integration with Distributed NetBeans via Ant scripts


For wrapper API(s) for legacy application


Generate POJO (plain old Java object) client


Generate JSP client to use with browser



Checkout OpenVMS Technical Journal article
http://h71000.www7.hp.com/openvms/journal/index.html#reusing


March 13, 2013

17

HP Web Services Integration Toolkit


Succeeds HP BridgeWorks on Alpha and Integrity


Is a set of integration tools based on Open Source tools
and standards


Is focused on integrating at the API
-
level


Calls routines written in 3GL languages, e.g.,


‘C’, COBOL, BASIC, FORTRAN, PASCAL, … or


ACMS Tasks

From


Java, Microsoft .NET, Web Services


Deployment descriptor specifies where 3GL routine to be
run:


In
-
process, i.e., in the same process as Web application container


Out
-
of
-
process, i.e., in a separate OpenVMS process managed by
the HP WSIT runtime

March 13, 2013

18

Web Services Integration Toolkit

Steps to follow to expose 3GL interfaces:


Prepare 3GL module using WSIT toolkit, e.g.,


Remove terminal I/O; ensure can be linked as a shareable image


May be necessary to write a wrapper for the old code


Write a client to test the new interface


Determine whether in
-
process or out
-
of
-
process

March 13, 2013

19

Web Services Integration Toolkit

1.
Create XML IDL file (on Integrity) using OBJ2IDL for 3GL or
STDL2IDL for ACMS

2.
Validate XML IDL file using VALIDATE

3.
Generate components using IDL2CODE

4.
Call generated JavaBean using technology of choice, e.g., Apache
Axis, Apache Tomcat, BEA WebLogic Server, ‘P’ language, etc.

March 13, 2013

20

WSIT


Integration beyond VMS

March 13, 2013

21

WSIT Development Steps

March 13, 2013

22

Development Steps

1) Create XML IDL file

Create an XML file that describes the interface to be exposed.



2) Validate XML IDL file

Verify that the XML IDL file correctly describes the interface being exposed. If it
does not, manually update the XML IDL file until the interface definition is
correct.



3) Generate components

Tell WSIT to generate components to expose the IDL interface as java. Create
one javabean component and one server component


4) Use the generated

code

Call the generated WSIT JavaBean from the technology of your choice.

( including BEA WLS, Apache Axis, JMS, Java RMI, J2EE or another JavaBean )


March 13, 2013

23

Overview of Tools

math.c

math.obj

math.xml

OBJ2IDL

VALIDATE

IDL2CODE

generated

server stub

generated

javabean

reads

compile

reads

creates

reads

creates

1

2

3

March 13, 2013

24

WSIT Tools

Tools to create IDL from different sources


OBJ2IDL.EXE (on I64)


ACMS2IDL.JAR


BWX2IDL.JAR


Tool to help catch errors/omissions in IDL


VALIDATE.JAR


Tool to generate Server and Javabean from IDL


IDL2CODE.JAR

March 13, 2013

25

OBJ2IDL

How to use tool:

$ obj2idl = "$WSI$ROOT:[tools]obj2idl.exe“

$ obj2idl
-
f
appname
.obj


This tool produced an IDL file named
appname
.xml which describes your
application interface. It also creates a file named
appname
.log which lists any
errors or warning that the tool found.


For example:

$cc/debug/noopt math.c

$obj2idl

f math.obj

March 13, 2013

26

VALIDATE

How to use tool:

$java
-
jar wsi$root:[tools]validate.jar
-
x
appname
.xml
-
s wsi$root:[tools]openvms
-
integration.xsd



For example:

$java
-
jar wsi$root:[tools]validate.jar
-
x math.xml
-
s wsi$root:[tools]openvms
-
integration.xsd


March 13, 2013

27

IDL2CODE (1)

How to use tool:

$@WSI$ROOT:[tools]wsi
-
setenv
-

wsi$dev

$java "com.hp.wsi.Generator"
-
i
appname
.xml
-
a
appname

-
o [.generated]


Required arguments are:


-
i <IDL filespec>
-

XML IDL file describing the application to wrap


-
a <Application Name>
-

Name to be given to the WSIT generated application


Optional arguments are: (other options not documented here)


-
o <Output Directory>
-

Directory in which to generate the wrapper files


For example:

$java "com.hp.wsi.Generator"
-
i math.xml
-
a math
-
o [.generated]


March 13, 2013

28

IDL2CODE (2)

Key Files for “appname” application


javabean
-
side files generated:

[.generated.
appname
]build
-
appname
-
jb.com

[.generated.
appname
]Iappname.java

[.generated.
appname
]appnameImpl.java


Output of build
-
appname
-
jb.com

[.generated.
appname
]appname.jar
-

this is the jar file that clients will use to call the legacy application.



Server
-
side files generated:

[.generated.
appname
Server]build
-
appname
-
server.com


Output of build
-
appname
-
server.com

[.generated.
appname
Server]
appname
.exe

[.generated.
appname
Server]
appname
.wsi

March 13, 2013

29

Web Services Integration Toolkit

Two types of deployment:

1.
In
-
process

deployment occurs when the application and the client
are called from the same process


Pros
: Fastest return time for client calls to application. No overhead
added by the WSIT runtime


Cons
: A crash will bring down all components in the process (client and
application server together with all other threads)

March 13, 2013

30

Web Services Integration Toolkit

Two types of deployment:

2.
Out
-
of
-
process

deployment occurs when the client and application
are run in different processes


Pros
: Typically scales better than in
-
process deployments.
Allows the use of the WSIT runtime deployment properties


Cons
: Adds complexity and overhead to every call

March 13, 2013

36

Services Oriented Architecture
(SOA) and Web Services


SOA is a design
-
style for creating shared, reusable,
distributed services


SOA is emerging as the premier integration and
architecture framework in today's complex and
heterogeneous computing environment


Web Services is the preferred, standards
-
based, and
vendor independent way to implement SOA


Promotes loose coupling between independent and well
-
defined
software components


Facilitates reuse, particularly the reuse of existing application
systems


Provides interoperability between heterogeneous applications and
technologies


Provides dynamic discovery of services


Facilitates implementation of composite services from other
services


Consider moving to an SOA framework using Web
Services

March 13, 2013

37


E
-
business Update

March 13, 2013

38

General Updates


Performance improvements in the OpenVMS kernel, file system, and
CRTL benefiting Java and UNIX portability


Security enhancements in Web Services, SSL ,CDSA, SSH, GnuPG,
Stunnel, LDAP authentication, and Kerberos



Open source


Continue tracking open source projects


Identify additional open source technology that needs to be included with our
infrastructure


Port selected versions of Apache, Tomcat, Perl, PHP, Mozilla, XML, Axis,
UDDI4J, and NetBeans


Working with universities in Bangalore to stimulate open source projects



Ship updates to e
-
Business and Integration components via:


e
-
Business CDs on OpenVMS Alpha


FOE on OpenVMS I64 and quarterly Delta disk


Web downloads

March 13, 2013

39

OpenVMS eBusiness and

Integration Technologies

2006

2007

2008

2009

2009

SWS and SWB updates on Alpha and Integrity
tracking the associated open source project

Secure Web Server V2.1 (Apache
2.0.x based) on OpenVMS Alpha
and Integrity

Tomcat (JSP) 5.5.9

PHP 4.3.10

mod_perl 2.0 and Perl 5.8.6

Secure Web Browser V1.7
-
11 on
OpenVMS Alpha and Integrity

BridgeWorks V3.0A on
OpenVMS Alpha

COM V1.4 on
OpenVMS Alpha

OPC Transport for
OpenVMS Integrity

DCE V3.2 for OpenVMS Alpha and Integrity

Subject to change without notice

March 13, 2013

40

Secure Web Server (SWS) and
Scripting


Current versions:


SWS 2.1 (Apache 2.0.52)


Removes stream
-
LF file restriction


CSWS_PHP 1.3 (PHP 4.3.10)


CSWS_Perl 2.1 (mod_Perl 2.0.1)


Perl 5.8.6


CSWS_Java 3.0 (Tomcat 5.5.9)


Future directions:


SWS 2.1 is the functional replacement for SWS 1.3
-
x
and SWS 2.0


Future enhancements and new features will be in SWS
2.1 and later

March 13, 2013

41

Secure Web Server Version Support


OpenVMS Alpha 7.3
-
2 and OpenVMS 8.2 (Alpha and I64)
are the last releases on which SWS 1.3
-
* is supported.


OpenVMS Alpha 7.3
-
2 is the last release on which SWS
2.0 is supported.


The functional replacement for SWS 1.3
-
* and SWS 2.0 is
SWS 2.1, which is available
now
. All future new features
and enhancements to SWS will be provided with SWS 2.1
or later, which is based on the Apache 2.0.*.


SWS 1.3
-
* and SWS 2.0 will be supported while
OpenVMS Alpha 7.3
-
2 and 8.2 are supported, either
standard support or Prior Version Support (PVS).


Support for these SWS versions will include remedial fixes and
security fixes as deemed appropriate.

March 13, 2013

42

Secure Web Browser (SWB)


Current version:


SWB 1.7
-
11 (Mozilla 1.7.11) Alpha and Integrity


ChatZilla 0.9.69



Future releases:


SWB based on FireFox


Mail client based on Thunderbird

March 13, 2013

43

BridgeWorks


Current version:


3.0A (Alpha only)


Not ported to OpenVMS Integrity


Support for BridgeWorks 3.0A through 2006 on
OpenVMS 7.3
-
2 and 8.2
-
x



Replacement capability is Web Services
Integration Toolkit (WSIT)


WSIT includes migration tools for BridgeWorks


Migration information, including whitepaper, at
http://h71000.www7.hp.com/commercial/bridgeworks/migrate.html

March 13, 2013

44

COM


Current version:


1.4 (Alpha only)


Not ported to OpenVMS Integrity


Investigating subset of COM on Integrity to support
OPC (Open Process Control)


Support for COM 1.4 through 2006 on OpenVMS
Alpha 7.3
-
2 and 8.2
-
x



Use Web Services as the replacement
technology

March 13, 2013

45

Web Services Tools

(XML, SOAP, WSDL, UDDI)

OpenVMS eBusiness and

Integration Technologies

Native JDBC/ODBC

(via Attunity Connect)

Java


Platform, Standard Edition,

v 1.4.2, for OpenVMS Alpha and Integrity

Java SE 5.0 on OpenVMS Alpha

UDDI Client Toolkit (UDDI4J)
on Alpha and Integrity

Web Services Tools updates

on OpenVMS Alpha and Integrity

SOAP Toolkit on
OpenVMS Integrity

Web Services Integration Toolkit (WSIT)
1.1 for OpenVMS Alpha and Integrity

2006

2007

2008

2009

2010

Java SE 5.x updates on Alpha

XML Technology on
OpenVMS Integrity

Java SE 5.0 on OpenVMS Integrity

Java SE 6.0 on OpenVMS Integrity

Java SE updates on Integrity

Subject to change without notice

March 13, 2013

46

Java™ Platform, Standard Edition
(Java SE)


Current version:


Alpha


JDK 5.0
-
1 on Alpha


Integrity


SDK v 1.4.2
-
3



Future releases:


Alpha


JDK 5.x will continue to be supported


Integrity


JDK 5.0


Release target is September 29, 2006, beta test on June 30, 2006


Integrity


JDK 6.0


Release target in late 2007



Management APIs and JMX


Alpha


Q1 2007


Integrity


September 2006 with initial JDK 5.0 release



Many new features in Java 5.0, checkout
http://java.sun.com/j2se/1.5.0/docs/relnotes/features.html

March 13, 2013

47

Web Services


Current releases:


XML 2.0 (Apache Xerces and Xalan)


SOAP Toolkit 2.0 (Apache Axis 1.1)


UDDI 1.0 (UDDI4J 2.0.2)


Web Services Integration Toolkit (WSIT) 1.1


BridgeWorks 3.0A (Alpha only)



Future releases:


Updates based on more recent open source releases

March 13, 2013

48

Application Development and
Deployment
-

Tools

2006

2007

2008

2009

2010

NetBeans 3.6 on OpenVMS
Alpha and Integrity

Distributed NetBeans V2.0
on Alpha and Integrity

(based on NetBeans 5.x)

Ongoing Tool Releases

Distributed NetBeans V1.1
-
1
on Alpha and Integrity
(based on NetBeans 3.6)

DECset V12.7 on
Alpha, Integrity, VAX

DECset V12.8 on
Alpha and Integrity

Subject to change without notice

March 13, 2013

49

OpenVMS Application Development
Tools Strategy


NetBeans is the
native
OpenVMS Integrated
Development Environment (IDE)


For Java development:


Develop on platform of choice, using tool(s) of choice


Deploy on OpenVMS


For 3GL development:


Develop and deploy on OpenVMS using current DCL
-
based tools
(compilers and DECset)

and/or


Develop and deploy on OpenVMS using NetBeans plus plugins

and/or


Develop on platform of choice using Distributed NetBeans plus
plugins and deploy on OpenVMS

March 13, 2013

50

Software Development


On OpenVMS:


Used to have Enterprise Toolkit for Visual Studio (V6)


Now replaced by NetBeans


DECset is still available for pure 3GL environments


Including Integrity



On other platforms:


Develop on
platform of choice
, e.g.,


Windows or Linux, test and deploy on OpenVMS using:


Distributed NetBeans with remote code management and debugging


BEA WebLogic Workshop


jDeveloper


jBuilder


Eclipse




March 13, 2013

51

Software Development

NetBeans?


Sun
-
Sponsored Open
-
Source Integrated
Development Environment


100% Java


runs anywhere there’s a JVM


Feature
-
rich, drag
-
n
-
drop GUI creation, JSPs,
Servlets, JSF, Web Services


Extensible using plug
-
in modules


Supports other languages (C/C++, XML, HTML,
FORTRAN, COBOL, Pascal*)


Support for CMS


CVS client


Ant (multiple platform builds from one build definition
file)


March 13, 2013

52

Software Development

Distributed NetBeans
?


Allows any desktop (Windows, Linux, HP
-
UX,
etc.) to be used to do remote OpenVMS
development


NetBeans runs on the desktop


Provides remote compilation (Java, C/C++,
COBOL, BASIC, Pascal), error navigation,
remote execution, and eventually debugging


Provides remote Ant for multiple platform builds


Remote CMS operations


can combine other
source code libraries such as CVS in one
session

March 13, 2013

53

Software Development


Distributed NetBeans

DCL Commands

DCL Command Output

Advanced Server,
SAMBA, FTP

OpenVMS Alpha

HP Desktop
Computer

www.netbeans.org

March 13, 2013

54

Software Development

Distributed NetBeans


Directory from an
OpenVMS
system


Same directory
viewed in
NetBeans

March 13, 2013

55

Software Development

Distributed NetBeans

Edit source locally

Compile and

execute remotely

March 13, 2013

56

Software Development

Distributed NetBeans

Execute the
program remotely
on OpenVMS

March 13, 2013

57

Software Development


Distributed NetBeans

U*X, Windows or Linux
for the server

Source Code

Control System:

CVS

All

source code and build

procedures maintained in

one

place for
all

platforms

and
languages
.

Windows

OpenVMS

with CMS library

Linux/U*X

HP
-
UX

March 13, 2013

58

OpenVMS eBusiness and

Integration Technologies

BEA WebLogic 8.1 sp3

on OpenVMS Alpha and Integrity

BEA MessageQ 5.01

on OpenVMS Alpha and Integrity

BEA WebLogic Integrate
8.1 sp3 on OpenVMS Alpha

2006

2007

2008

2009

2010

Compuware: Uniface
-

a component
based development environment

WRQ Reflections and VeraStream
for OpenVMS Alpha and Integrity

IBM WebSphere MQ V5.3 on
OpenVMS Alpha and Integrity

2AB Orb2 (CORBA) on
OpenVMS Alpha and Integrity

Attunity Integration Suite on
OpenVMS Alpha and Integrity

Subject to change without notice

March 13, 2013

59

Partner and ISV Updates


Now Available!


BEA WebLogic Server 8.1 Sp3 on Alpha
and
Integrity


Checkout the
WebLogic Web Shelf at
http://h71000.www7.hp.com/ebusiness/bea_webshelf.htm

March 13, 2013

60

Questions and Answers


John Ferguson


John.L.Ferguson@hp.com


520
-
432
-
4429

March 13, 2013

61