This is the main title which is set in blue

decorumgroveInternet and Web Development

Aug 7, 2012 (5 years and 1 month ago)

1,100 views

IBM
Websphere


© Copyright IBM Corporation 2010


WebLogic to WebSphere Migration Process

차의중

WebSphere Field Technical Professional

2010.MAR

IBM WebSphere

© Copyright IBM Corporation 2010

1

Typical Migration Effort and Tasks

9%
4%
34%
10%
13%
13%
17%
마이그레이션

계획

수립
설치



환경설정
마이그레이션

수행
최적화
시스템분석및준비
테스트
교육및기술이전
IBM WebSphere

© Copyright IBM Corporation 2010

2

Typical Migration process

*
기획

(1

)


-

시스템

현황



성능

분석


-

일정

계획


-

마이그레이션

목표

설정


-

마이그레이션

방안

마련



-

마이그레이션

과정



-

인력

운용

방안



-

테스트

방안



-

비상시

대처

방안


*
교육



-

관리자



투입

인원

대상


*
시스템

도입
,
설치
,
업그레이드
(1~3

)


-

머신



각종

드라이버

설치



업그레이드


WAS


개발



설치
(1

)


*
어플리케이션

마이그레이션

(1~2

)


-

어플리케이션

코드

수정
(Optional)


-

설정파일

수정


-

어플리케이션

설치


-

Unit
-
Test


*
통합

기능

테스트

*
성능

테스트

*
테스트

결과에

따라

추가적인

코드



설정

변경

*
튜닝

*
오픈



모니터링

오픈
/
안정화

테스트
/
최적화




장애시

-

원복



임시

운영

수행
(1~2

)

준비
(1~2

)

Application Migration Tool

IBM WebSphere

© Copyright IBM Corporation 2010

3

Typical Migration
Challenges

Challenges / Risks

Migration Plans

새로운

제품에

대한

기술

습득

필요


기술지원



교육

제공

시스템

환경의

변화
(
기존

사용

중인

H/W, OS, DB, 3rd
party
제품

등이

최신

J2EE
스펙이나

최신

WAS


맞지

않을

경우
)


J2EE


WAS


스펙을

낮은

버전으로

하거나
,
관련

시스템

환경을

높은

버전으로

Upgrade
필요

개발



관리

환경의

변화


교육

등을

통해

WAS


관리
,
개발

환경에

적합한

개발



관리

기술

습득


빌드



관리용

스크립트

수정


스크립트

변환

유틸리티



가이드를

이용하여

신속히

수행

가능


개발

환경

마이그레이션


수작업으로

수행

필요

J2EE
버전

변화에

따른

어플리케이션

업그레이드

(
최신

WAS
에서도

기존

J2EE
버전의

어플리케이션을

운영





있으나
,
최신

J2EE
스펙의

장점을

활용

하고자



경우
,
새로운

스펙으로의

어플리케이션

업그레이드

필요
)


업그레이드


,
다소의

코드나

설정

변경이

있을



있으나
,
기본적으로

코드



설정의

하향

호환성이

보장되므로

작업량은

많지

않음
.

J2EE
표준이

아닌
,
비표준

확장

기능이나
,
기존

제품에

특화된

설정



코드의

마이그레이션


기본적으로
,
수작업에

의한

수정

필요



일반적으로

매우

소량임


Application Migration Tool
등의

자동화

툴을

활용함으로써

신속
,
정확하며

안정성

있게

수행

가능

서비스

품질

보장


현업

사용자들과

테스트



등을

통한

기능



성능의

사전

테스트


기존

시스템의

성능을

측정


,
이에

대비한

목표치

설정


목표치

달성

시까지

성능

튜닝

IBM
Websphere


© Copyright IBM Corporation 2010


Application Migration Toolkit (AMT)

IBM WebSphere

© Copyright IBM Corporation 2010

5

What is Application Migration Tool (AMT)?


WebLogic

Application Server
에서

W敢印桥牥 A灰汩l慴楯a 卥牶敲
로의

A灰汩l慴楯a M楧牡瑩潮


도와주는

도구


Eclipse Plugin
으로

제공


Based on Rational Software Analyzer Technology

지원

플랫폼

요구

내역

비고

Source Application

J2EE 1.4
이하

WebLogic 9
이하에서

개발된

어플리케이션

Target

WAS

WebSphere Application Server v7.0

실행

환경

Eclipse for JEE
또는

IBM RAD(Rational
Application Developer)

eClipse 3.4.2
이상

필요


제품

가격


무료


http://www.ibm.com/developerworks/websphere/downloads/migration_toolkit.html


기술

지원

:



WebSphere Application Server


대한

기술

지원

계약

고객에

한하여

䥂I
측에서

기술

지원
.


기타

고객은

AM吠䙯牵洠
게시판을

통하여

기술

지원
.


http://www.ibm.com/developerworks/forums/forum.jspa?forumID=2106

IBM WebSphere

© Copyright IBM Corporation 2010

6

Fix Points

Classpath setup

Convert Enterprise Archive (EAR) classpaths to J2EE specifications

WebLogic Server Startup Classes

Detect and convert T3StartupDef and T3ShutdownDef classes

Non
-
Portable JNDI lookups

Detect and refactor JNDI lookups to use the parameter
-
less InitialContext

JSPs

Enforce case sensitivity of JSP tag/attribute names against the TLD file

Deployment Descriptors

Detect and convert WebLogic specific deployment descriptor elements to
industry standard deployment descriptor elements

WebLogic proprietary java package
references

Detect and convert proprietary package references to standards based
package references

Web Services

Generate ANT script, Service Endpoint Interface, WSDL, Deployment
Descriptors, Mapping Files and other JAXRPC Webservice artifacts

*
상세



C潮癥牳楯渠R畬u


문서

후반부

참조

IBM WebSphere

© Copyright IBM Corporation 2010

7

설치



활용

절차

1.
이클립스

또는

RAD
설치


2.
이클립스

또는

剁䐠
위에

A灰汩pa瑩潮tM楧牡瑩潮tT潯汫楴i
설치


소스

어플리케이션

반입

⡁灰汩pa瑩潮t䥭灯牴I


어플리케이션

빌드를

위한

설정

추가


코드

분석

설정



열기


코드

분석에

필요한옵션

선택

> ‘
분석


버튼

클릭


분석

결과

리뷰



필요



코드

수정


⡏灴楯湡氩l
추가적인

코드

개선

필요



코드

분석

기능을

이용하여

재분석

/
리뷰
/
수정


수정이

완료된

어플리케이션을

반출
⡁灰汩pa瑩潮tEx灯牴⤬)
디플로이
⡄e灬潹러


테스트

IBM WebSphere

© Copyright IBM Corporation 2010

8

이클립스

또는

剁䐠
다운로드



설치

1.
eclipse SDK
또는

剁䐠
다운로드



설치


eclipse :
http://www.eclipse.org


RAD :
http://www.ibm.com/developerworks/downloads/r/rad/?amp;S_TACT=105AGX10&S_CMP=LP



2.
ecipse


경우

필수

플러그인

추가


Ganimede : Charting and Reporting , Web and Java EE Development


update site :
http://download.eclipse.org/releases/ganymede



Galileo :
Business Intelligence, Reporting and Charting , Web, XML and Java EE Development


update site :
http://download.eclipse.org/releases/galileo



필수

플러그인

설치

⡇(湩浥摥)

필수

플러그인

설치

(䝡汩l敯e

IBM WebSphere

© Copyright IBM Corporation 2010

9

Application Migration Toolkit
다운로드



설치

1. migration toolkit Download (


㄰MB)

http://www.ibm.com/developerworks/websphere/downloads/migration_toolkit.html


2. Eclipse


P汵杩渠楮i瑡汬
툴을

이용하여

AM吠
설치

(
통상의

Ec汩灳e P汵杩渠
설치

방식과

동일
)


다운로드

받은

파일의

위치

지정

乥N琠…⁆ 湩nh

IBM WebSphere

© Copyright IBM Corporation 2010

10

소스

어플리케이션

반입

1.
Eclipse


반입

⡉浰潲(러
기능을

이용하여

소스

어플리케이션

반입

⡅(刬RWA刬REJB
-
JA刬

유틸리티

Ja爠



IBM WebSphere

© Copyright IBM Corporation 2010

11

어플리케이션

빌드를

위한

설정

추가

1.
(Optional) Build


Packa杩湧g
형태

변경

필요


ⰠM潤畬o

䑥灥湤敮ny
설정


J2EE 創湴業i⁌楢 a特
설정


⡏灴楯湡氩l
기타

빌드에

필요한

설정

J2EE
모듈



종속성

설정

J2EE
런타임

라이브러리

설정

IBM WebSphere

© Copyright IBM Corporation 2010

12

코드

분석

옵션

선택



분석

실행

1.
툴바

>⁓潦瑷a牥 A湡汹穥爠䍯湦楧畲i瑩潮t


분석



필요한

옵션

선택



분석

실행

버튼

클릭



분석
¶
실행

버튼

분석

설정



실행



분석

설정



열기

IBM WebSphere

© Copyright IBM Corporation 2010

13


AMT
설치



활용

절차


분석

결과

리뷰



수정

1.
분석

결과

확인




수정


Quick fix


활용하여

자동

수정


일부

Quick fix
미제공

항목은

수동

수정

필요

IBM WebSphere

© Copyright IBM Corporation 2010

14

Conversion Rules

Rules and Quick fixes (Java Source Code)

Rule name

Quick
fix

Action

Do not use WebLogic
RMI API calls

Yes

This rule detects the use of references to the proprietary weblogic.rmi packages.

The quick fix changes weblogic.rmi to java.rmi to use the Java provided classes.

Do not use WebLogic
-
specific JNDI name
values



Yes

Scans Java files detecting the usage of the JNDI name values:

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory

java.naming.provider.url= t3://localhost:7001


If found, users are given the option to change the JNDI names to default portable
JNDI Name values:

java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory

java.naming.provider.url=corbaloc:iiop:localhost:2809


Note: the JNDI Name values must be in the same java source file where the
context is initialized with the javax.naming.InitialContext(Hashtable) constructor.


Do not use WebLogic
startup or shutdown
classes

Yes

This rule looks for classes that implement the WebLogic startup and shutdown
interfaces.

The quick fix converts these classes to use the
javax.servlet.ServletContextListener interface and registers it in the application's
web.xml file.



IBM WebSphere

© Copyright IBM Corporation 2010

15

Conversion Rules

Rules and Quick fixes (Java Source Code)

Rule name

Quick
fix

Action

Use compliant
UserTransaction
lookup name

Yes

This rule looks for references to ctx.lookup(“javax.transaction.UserTransaction”).

Within bean managed transaction (BMT) beans, the quick fix converts the
flagged line to ctx.getUserTransaction().

Within servlets, Web applications and client code, the flagged line is converted
to the JNDI lookup:

ctx.lookup(“java:comp/UserTransaction”)



Use matching throws
clause in EJB bean
class

Yes

This rule looks for mismatches between the enterprise bean implementation
and the method definitions in the home and remote interfaces.

The quick fix adds any missing exceptions and removes any extra exceptions.
The interfaces are not changed.



Do not use
weblogic.apache
packages

Yes

This rule flags import and code references to classes where the class package
starts with weblogic.apache and the class maps directly to an org.apache class.

The quick fix changes the code to org.apache

Download the appropriate Apache open source .jar file, and include it with your
application.


Do not use
UserTransaction
interface from CMT
beans

No

This rule detects references to ctx.lookup(“javax.transaction.UserTransaction”)
within container managed transaction enterprise beans. References to the
UserTransaction object are not allowed from CMT beans.

These references are flagged so that you can remove this Java EE violation.

IBM WebSphere

© Copyright IBM Corporation 2010

16

Conversion Rules

Rules and Quick fixes (Java Source Code)

Rule name

Quick
fix

Action

Use portable JNDI
Names


No

Detects the usage of the constructor: javax.naming.InitialContext(Hashtable),
informing not to put any proprietary WebLogic JNDI name values into the
Hashtable.



Do not use non
-
mapping
weblogic.apache
packages

No

This rule flags import and code references to classes where the class package
starts with weblogic.apache and the class does not map to an open source
Apache class.

You must modify the code to use different classes. See the rule help for more
information.



Do not use WebLogic
-
specific packages

No

This rule flags imported classes that begin with weblogic but not including the
weblogic.apache classes. The flagged server specific APIs must be migrated.

IBM WebSphere

© Copyright IBM Corporation 2010

17

Conversion Rules

Rules and Quick fixes (JSP)

Rule name

Quick
fix

Action

Avoid using a .jsp
extension for JSP
fragments

Yes

This rule looks for JSP fragments included in another JSP. If the JSP fragment
file has the .jsp extension rather than .jspf extension, it is flagged.

The quick fix takes you to the refactor dialog to change the file name and all of
its references.


Use correct case for
tag attribute names

Yes

JSP taglib attributes are case
-
sensitive in WebSphere Application Server. This
rule flags any taglib attribute that is not case correct.

The quick fix changes the case as it is defined in the tag library.



IBM WebSphere

© Copyright IBM Corporation 2010

18

Conversion Rules

Rules and Quick fixes (XML


DD, WebServices, etc


standard


방식으로

기술

가능한

것들
)

Rule name

Quick
fix

Action

Use standard
deployment
descriptors for EJB
reference names

Yes

WebLogic
-
specific deployment descriptors (weblogic.xml or weblogic
-
ejb
-
jar.xml)
might contain EJB references. These references map the EJB reference to the
JNDI name. For the references to work on WebSphere Application Server, they
must be moved to the standard Java EE deployment descriptors (web.xml or
ejb
-
jar.xml).

The quick fix provided moves all EJB references defined in WebLogic
-
specific
deployment descriptors to standard deployment descriptors.


Use standard
deployment
descriptors for
resource reference
names

Yes

WebLogic
-
specific deployment descriptors (weblogic.xml or weblogic
-
ejb
-
jar.xml)
might contain resource references. These references map the EJB reference to
the JNDI name. For the references to work on WebSphere Application Server,
they must be moved to the standard Java EE deployment descriptors (web.xml
or ejb
-
jar.xml).

The quick fix provided moves all resource references defined in WebLogic
-
specific deployment descriptors to standard deployment descriptors.

IBM WebSphere

© Copyright IBM Corporation 2010

19

Conversion Rules

Rules and Quick fixes (XML


DD, WebServices, etc
-

standard


방식으로

기술

가능한

것들

)

Rule name

Quick
fix

Action

Do not use local JNDI
names

No

Select the rule and press F1 for manual conversion instructions.




Use WebSphere
bindings to define
JNDI names

No

Select the rule and press F1 for manual conversion instructions.



Use WebSphere
bindings to define
message driven
descriptor


No

Select the rule and press F1 for manual conversion instructions.


Use WebSphere
extensions to define
concurrency strategy

No

Select the rule and press F1 for manual conversion instructions.


Use WebSphere
extensions to define
transaction timeout
seconds

No

Select the rule and press F1 for manual conversion instructions.


IBM WebSphere

© Copyright IBM Corporation 2010

20

Conversion Rules

Rules and Quick fixes (XML


WebLogic unhandled or partially handled
-
웹로직에서만

적용가능한

파일들
)

Rule name

Quick
fix

Action

Do not use
weblogic.xml file

No

Select the rule and press F1 for manual conversion instructions.




Do not use weblogic
-
application.xml file

No

Select the rule and press F1 for manual conversion instructions.



Do not use weblogic
-
cmp
-
jar.xml file

No

Select the rule and press F1 for manual conversion instructions.


Do not use weblogic
-
cmp
-
rdbms
-
jar.xml file

No

Select the rule and press F1 for manual conversion instructions.


Do not use weblogic
-
diagnostics.xml file

No

Select the rule and press F1 for manual conversion instructions.


Do not use weblogic
-
ejb
-
jar.xml file

No

Select the rule and press F1 for manual conversion instructions.


Do not use weblogic
-
ra.xml file

No

Select the rule and press F1 for manual conversion instructions.


IBM WebSphere

© Copyright IBM Corporation 2010

21

Conversion Rules

Rules and Quick fixes (XML


웹로직

웹서비스

관련
)

Rule name

Quick
fix

Action

Do not use WebLogic
Web services
deployment descriptor



Yes



This rule looks for the Web services deployment descriptor as follows:

The presence of web
-
services.xml or

The presence of weblogic
-
webservices.xml and the Java EE deployment descriptor
(webservices.xml) in the same folder.

The quick fix generates an ANT script that uses IBM WebSphere ANT tasks, which
generates the appropriate artifacts for the list of Web services based on the
information collected from the deployment descriptors. Depending on the deployment
descriptor, the fix might also generate the Service Endpoint Interface (SEI) for the
service and add it to the project class path. The user can then run the ANT script, copy
the generated artifacts to the project, and possibly add additional targets such as the
endpoint enabler, for example.

IBM WebSphere

© Copyright IBM Corporation 2010

22

Conversion Rules

Rules and Quick fixes (
ClassPath
)

Rule name

Quick
fix

Action

Use MANIFEST.MF
for application class
path

Yes

This rule looks for any classes or libraries contained within an APP
-
INF
directory of an EAR file.

The quick fix adds an entry to the class path of each affected Web module by
updating the Class
-
Path entry of the module's MANIFEST.MF file.


IBM WebSphere

© Copyright IBM Corporation 2010

23

참고자료

Applictaion Migration Tool Introduction and Download

http://www.ibm.com/developerworks/websphere/downloads/migration_toolkit.html


Application Migration Tool Users guide

http://freeman98.hosting.paran.com/xe/?document_srl=2002


Application Migration Tool Forum

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=2106


Eclipse

http://www.eclipse.org


Rational Application Developer (RAD) Product

http://www.ibm.com/developerworks/downloads/r/rad/?amp;S_TACT=105AGX10&S_CMP=LP




Rational Software Analyzer product

http://www.ibm.com/developerworks/rational/products/rsar/