Sie sind auf Seite 1von 5

highlevel view of splitmigration: ================================ application tier migration: here we are migrating the applications from solaris to linux

============================== I>>PREPARE THE TARGET SYSTEM. ============================== > first we need to install oel 5.1 > to run the 11.5.10cu2 on linux we need to apply the required packages,set all the configuration settings LIKE: rpm packages set the open file descriptors /etc/security/limits.conf (increase the open file descriptors) set the port range /etc/sysctl.conf (increase the tcp/ip ntwking port range) entry in /etc/hosts validate linux netwking settings (/etc/sysconfig/network) apply the pre-reuired patches >create the APPLMGR user and DBA Group >create the file system i.e create the directory structure at the target side based on source server <APPL_TOP> #mkdir /oracle/apps/visappl <COMMON_TOP> #mkdir /oracle/apps/viscomn <COMMON_TOP>/util #mkdir /oracle/apps/vicomn/util <COMMON_TOP>/pages #mkdir /oracle/apps/viscomn/_pages <OA_JAVA> #mkdir /oracle/apps/viscomn/java <OA_HTML> $mkdir /oracle/apps/viscomn/html change the directories ownership to applmgr user (chown -R applmgr:dba /oracl e) > target linux server system has prepared ===================================== II>>PREPARE SOURCE EBS FOR MIGRATION ===================================== 1> prepare the source ebs application tier by applying the latest AD.I patch to source system (AD.I 5 must be higher) version of AD can be determmined by runnin g the adadmin or adutconf.sql to run adutconf.sql login as applmgr user and source the application env file. t hen run $SQLPLUS apps/apps @AD_TOP/sql/adutconf.sql this generates the adutconf.lst file which gives the product level details. 2> then implement latest autconfig on source ebs tier(solaris) by applying the late st TXK AUTOCONFIG TEMPLATE ROLL-UP patches. TXK patches will update the autoconf ig template files

3> apply the latest rapid clone patch 4> Create a current snapshot of application env. . .APPSTIER.env $adadmin 2. maintain application files menu. 5. maintain snapshot information. 2.update current view snapshot. ================================================= III>> MIGRATE THE EBS SOFTWARE COMPONENTS TO LINUX =================================================== 1> build the source system manifest and generate the migration patch. the first step to generate your customer specific patch is to build the manifest file of ebs application files from the source solaris system. then upload to th e migration website. then oracle website analyzes the contents of the source sys tem manifest and generate the new customer specific patch which is then appied t o the taeger system at the alter stage. to generate the site specific manifest file on source sloaris system,run the adg perl script while logged in solaris system as APPLMGR user. $ . APPSTIER_ENV_FILE $ perl $AD_TOP/bin/ the above script will create the maifest file and store the output file located at $APPL_TOP/admin/$TWO_TASK/out/adgenpsf.txt the contents are like: #APPLICATION SYSTEM NAME : VIS #REALEASE NAME : #APPL_TOP_NAME : srcsrvr ad ad ad ....... once the manifesst file created upload it to the oracle paltform migration websi te as they will build the customer specific applications patch for target linux system. after submitting the manifest file to website,the patch will be generated and ma de available to email is sent when patch is acessible and email incl ude the password that used during the download of your customer specific patch. 2>create the target system APPL_TOP files. as some components of ebs application are platform independent these entities ar e directly copied from soure to targer linux server. classes and ja r files,oracle forms,pl/sql code and html and other technologies. to start populating the linux systems APPL_TOPS selected files from source solar is system are copied to target linux server.


adadmin.o 115.82 adadmin_main.o 115.7 adapps.o 115.1

the specific directories that should be copied using SCP or tar or ftp or rcp $APPL_TOP,$OA_HTML,$OA_JAVA,$COMMON_TOP/util,$COMMON_TOP/_pages 3>>Construct an Autoconfig XML context file on target linux server. autoconfig has all the configuration of EBS instances. the naming convention is <EBS_INSTANCE>_hostname.xml and is located at $APPL_TOP/admin directory on each node in the EBS instance. as target system is a whole new node it is necessary to build a fresh XML contex t file that represents the new configuration to be used at the server. To generate the new context file the script is used. login into linux systems as applmgr user and source the new env. then go to AD_T OP/bin and run the $ perl migrate java=JDK_HOME contextfile=CONTEXT_FILE where JDK_HOME is the location of JVM installed on linux target server. and CONTEXT_FILE is the location of original source system context file in then cloned into a version suitable for use at the target system. as the scripts createa the new context_file and it is placed at $A PPL_TOP/admin/ directory. 4>>>INSTALL THE MIDDLE TIER TECH_STACK and CUSTOMER SPECIFIC EBS application tie r patch. at this stage we have to install the tech stack software that is specific to the linux server. installing the technology stack on the linux server involves runing the Rapid in stall wizard (RapidWhiz) with the -techstack option. when installing the rapidwhiz- techstack option @@@ choose the 9iAS as the tech stack to install. @@@ when prompted for the context file choose the option to use an existing file and supply the location of context file which is created by using the adclonect @@@ enter the location for 8.0.6 and IAS oracle homes. note: most of the times the tech stack components at the solaris(source) are the ar higher/upgraded levels as we will patch the tech stack at the target side we have to apply the patches to the newly installed tech stac k on the linux server(target server) so that the tech stack components are at sa me level both at target and source side. 5>>> update the platform specific EBS application components. before runnning the customer specific patch, it is necessary to patially ru n the autoconfig utility so that some of the env files are in the place so that adpatch will operate properly. RUN the AUTOCONFIG INSTE_SETUP phase on target linux system:

to allow the adpatch to tun properly, execute the INSTE8_SETUP phase of autoconfig using the context file that was created by this is done by logging in the system and then running the wit h the run=INSTE8_SETUP flag: $CD $AD_TOP/bin $ ./ run=INSTE8_SETUP contextfile=<target system contextfile> where AD_TOP is set to the ad/11.5.10 directory unser the EB S visappl directory <target system contextfile> is the full pathname of th e context file that was created using the after the command has completed, check the autoconfig log file for errors or war nings. 6>>> APPLY THE CUSTOMER SPECIFIC EBS APPPLICATIONS PATCH. to apply login in the ebs as appplmgr user source the .env file $cd <custom-patch-xtraction-directoty> $ . APPSTIER_ENV_FILE $ ./adpatch options=noprereq as a part of patch application process,relinking of ebs appli cation binaries will occur so that the newly patched libraries are used to rebui ld the linux specific binaries. 7>>>>UPDATE THE TECHSTACK TO MATCH THE SOURCE SYSTEM LEVEL 8>>> APPLY THE TECHSTACK INTEROPERBILITY PATCH. 9>> REGENERATE THE FILE SYSTEM OBJECTS. as all the application's EBS components now in place on linux system, it is know possible to generate many of the EBS application objects(FORMS,REPORTS,MESS AGES and so on) from their source. first regenerate the forms objects on target llinux system. to generate the form s objects via the source the env file login as applmgr user $ . APPSTIER_ENV_FILE $ $AD_TOP/patch/115/bin/ apps/apps once the form related object generation is done. use adadmin to generate the re maining Messages,FORMS, REPORTS, GRAPHICS and JAR files. $adadmin 1. Generate application files menu 10.Complete the full AUTOCONFIG configration on target linux system. here we need to compare the xml file at target with source xml file is there is any difference we have to try resolve them. Run autoconfig by loggin in as APPLMGR user ....then source the env file ...

go to $AD_TOP/bin $ ./ contextfile=CONTEXT_FILE 11>> update the third party xtensions. 12>>> review the site specific customizations from the source system. 13>> update the font information if the UTF8 character set was in use. 14>> Migrate the complimentary oracle software 15>> update the printer settings 16>> update the workflow configuration settings 17>> update the additional database table based configuration settings 18>> update the CLASSPATH settings 19>> Execute the final autoconfig session for the migration. 20>> Test the new environment using the OAM DASHBOARD.