Migration/Upgrade to SAP MII 12.x

Transcription

1 Migratin/Upgrade t SAP MII 12.x Applies t: SAP Manufacturing Integratin and Intelligence (MII). Fr mre infrmatin, visit the Manufacturing hmepage. Summary This paper explains the different paths fr upgrading r migrating yur MII envirnment. It prvides a brief verview f the different paths and als explains sme f the prblem areas yu may encunter. It is supplemental t the Upgrade Guides available n Service Marketplace under Installatin Guides. Authr: Erik Schrampf, Kevin Yurasits and Jeremy Gd Cmpany: SAP Created n: 15 May, 2011 SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 1

2 Migratin/Upgrade t SAP MII 12.x Table f Cntents Upgrade/Migratin Paths... 3 General References and Links... 3 Path 1: Migratin Tl... 5 Prerequisites / Assumptins... 5 Prgram Length... 5 Prerequisites... 5 Required Skill Set... 6 Migratin Issue Checklist... 6 Cnfiguratin... 6 Web Cntent... 7 MII Cntent... 8 Migratin Tl Objects t Migrate Imprtant Pints Migratin Check Nn-Standard Themes Default Hmepage Cnsistency Reference Dcuments Nn-Standard SVG Objects Subflders with Prject Name Nn-Standard Animated Objects Nn-Standard Stylesheets Duplicate File Names Flder Naming Cnsistency Special Files Lng Scheduled Jb Names Prjects Accessing and Publishing Files in 12.x File Search and Replace MII Cntent: Web Cntent: Path 2: NW Upgrade Tl Starting the Upgrade Tl s Frntend Upgrade Wizard Adding MII t the Upgrade Path 3: CE Update Manager Path 4: Cnfiguratin and Prject Migratin Pst Migratin and Upgrade Tasks Specific t the Migratin Tl (11.5 t 12.x) General Related Cntent Cpyright SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 2

3 Migratin/Upgrade t SAP MII 12.x Upgrade/Migratin Paths Depending n the MII versin installed, different upgrade paths are available. See the matrix belw t determine what ptins are available fr yur current MII versin. Migrating r Upgrading depends n what versin is already installed and what versin yu want t mve t. If MII 11.5 is installed then the Migratin Tl will be used. It is pssible t use this tl t migrate 11.5 cntent t a new 12.x bx. If yur 11.5 server is capable f running NetWeaver then migratin directly n that server is als pssible. Frm MII 12.0 there are tw paths frward: First, is an in place (n bx) upgrade f MII and NetWeaver using the NetWeaver Upgrade Tl. This upgrades MII frm 12.0 t 12.1 r 12.2 and NetWeaver frm 7.0 t 7.11 EHP1. It is dne n the same server. The ther ptin is creating a new MII 12.1 r 12.2 server and use MII s Prject and Cnfiguratins imprt/exprt features t transfer cntent. Frm MII 12.1 t 12.2 yu have tw ptins Perfrm an upgrade n the same server by just deplying the MII 12.2 SCA files using CE Update Manager. The ther ptin is creating a new MII 12.2 server and use MII s Prject and Cnfiguratins imprt/exprt features. The next few sectins will cver these tls in mre detail. General References and Links Installatin and Upgrade/Migratin Guides: and 12.0 guides are under: SAP xapps -> SAP xapp Manufacturing Integratin and Intelligence 12.1 and 12.2 guides are under: SAP Business Suite Applicatins -> SAP Manufacturing -> SAP Manufacturing Integratin and Intelligence SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 3

4 Migratin/Upgrade t SAP MII 12.x Help Dcumentatin: SAP Business Suite -> SAP Manufacturing -> SAP Manufacturing Integratin and Intelligence Ramp-up Learning Map Cntent: SAP Manufacturing MII 12.0 Sample Prjects and Tls: These Tls and Prjects can be setup n any 12.x release. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 4

5 Migratin/Upgrade t SAP MII 12.x Path 1: Migratin Tl The principal bjective f this upgrade guide is t make the transitin frm SAP MII versin 11.5 t 12.x as seamless as pssible, and help t ensure a successful upgrade prcess. Online materials have been made available fr gaining a better understanding and appreciatin f the new aspects f versin 12.x, as well as specific cntent pertaining t migratin frm versin Prerequisites / Assumptins The MII applicatin cntent can vary substantially in bth size and scpe, and the assciated implementatin styles and practices can impact the migratin prcess in many ways. Versin 11.5 applicatin cntent is available, either n the existing 11.5 web server r a backup lcatin. Versin 12.x server is cnfigured and peratinal with the latest service packs and patches. The latest migratin tl (specific t yur 12.x versin) has been dwnladed and installed n the same machine with the 11.5 cntent. The persn perfrming the applicatin readiness assessment is cmpetent with bth MII versins 11.5 and 12.x. A custmer representative wh is knwledgeable in the applicatin must play an active rle in the upgrade prcess Prgram Length The budgeted time and effrt needed t cmplete the prgram will vary quite heavily n the nature and readiness f the applicatin itself, the remediatin effrts, as well as the time needed t test and cnfirm the functinality f the updated cntent. A mixture f Off-Site and On-Site time can be leveraged t streamline the upgrade effrts The fllwing table attempts t gauge the effrt (days) invlved in the migratin prcess Applicatin Cmplexity Assessment Phase Off-Site / On-Site Migratin Phase Off-Site / On-Site Ttals Very Lw 2 / 0 2 / 0 4 Lw 2 / 0 2 / 2 6 Medium 2 / 2 2 / 4 10 High 4 / 2 4 / Very High 4 / 4 5 / Prerequisites In additin t thse identified in the previus Intrductin sectin, full custmer cperatin and disclsure will be expected in rder t deliver the cmpletin f a successful upgrade SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 5

6 Migratin/Upgrade t SAP MII 12.x The applicatin readiness exercise and Migratin Check (part f the Migratin Tl) can be perfrmed while the NetWeaver team is cnfiguring 12.x n the server. The Migratin Tl cannt be run until the 12.x server is cmpletely peratinal. Required Skill Set SAP MII representatives Knwledge f bth the 11.5 and 12.x versin Trubleshting ability Attentin t detail Custmer representatives Knwledge f the applicatin cntent Access t additinal resurces as necessary Migratin Issue Checklist With versin 12.x mving away frm the cmbinatin f Micrsft s IIS and New Atlanta s ServletExec t NetWeaver. The fllwing list shuld be cnsidered when analyzing the versin 11.5 applicatin prir t perfrming the migratin. SAP WebAS is case sensitive, s all html paths t ther web cntent including items like html/irpt, css, js, xml, images, etc. must be case prper. All web cntent references shuld use relative links and nt have any file:// r fully qualified http references (unless abslutely necessary). LHSecurity user management has been cmpletely replaced by NetWeaver s User Management Engine (UME). Prjects have been added as an rganizatinal, backup, and deplyment mechanism. Assume mirrred cntent flder lcatins in the 11.5 file system (The Definitin f a Prject fr MII 12.x is explained later in the Prjects sectin.) Cnfiguratin and Applicatin cntent n lnger exist n the perating system s file system, but are nw resident in the NW database. Custm Actin blcks will need t be repackaged fr deplyment with 12.x. Cnfiguratin Availability f JDBC driver files (jar / zip) fr uplad int MII versin 12.x. SAP MII 12.x des nt cme pre-packaged with JDBC drivers as Therefre, it is necessary t uplad them int the 12.x system. There are tw ptins: Uplad the drivers yu are currently using in The directry fr the SQL and Oracle Drivers is generally <Drive>:\ServletExecAS\sexMII\webapps\default\Lighthammer\WEB-INF\lib. Using these drivers in 12.x is recmmended as yu will nt have t change yur data surce cnnectin infrmatin. Dwnlad the driver frm the vendr s website and uplad t 12.x. UDS cmpnents and vendr API s installed n the 11.5 server? If there are any UDS cmpnents r Vendr API s n the 11.5 server yu may need t mve them. Virtual Server usage between 11.5 instances? SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 6

7 Migratin/Upgrade t SAP MII 12.x Updating the IP and Prt data (server prperties), will likely be needed in rder t reference the assciated 12.x system. Trusted Servers have been remved, s RemteLginName and RemteLginPasswrd prperties will need t be utilized in place f the inbund server trust between MII servers. LHSecurity cnfiguratin in MII LDAP, xml users, etc LHSecurity is n lnger used. All Security is handled thrugh SAP UME fr cnnecting t LDAP, Databases, lcal users, etc. All 11.5 native xml users and attributes will be migrated as UME Database Data Surce bjects (ptinal cnfiguratin in the Migratin Tl). If a user s passwrd des nt fllw the UME s Security Plicy requirements (length, mixed case, digits, etc.), a default initial passwrd will be generated and nted in the Migratin lg, fr later cmmunicatin t the user. Any unused, empty, backup r temp flders in any f the pertinent cntent lcatins have been remved This is an pprtune time t d sme best practices husekeeping and remve temp flders, backup flders and unused cnfiguratin bjects, etc. 3 rd party custm actin blcks have t be repackaged fr uplad int versin 12.x f MII The classes in 12.x have changed; therefre yu will need t repackage custm actins fr MII transactins. Similar t JDBC drivers, yu will need t uplad and deply yur custm actin jar file(s). Refer t the 12.x help n hw t uplad a Custm Actin. Check t see what attributes fr rles and users are being used All attributes will be migrated int the Custm Attributes Administratin page fr MII. Fr thse attributes that are als fund in the NetWeaver UME they will be updated as well. If an attribute in NetWeaver UME has the same name as a Custm Attribute in MII. The Custm Attribute in MII will take precedence ver the NetWeaver attribute. Cnfirm that all active Schedules are valid and have the prper scheduled frequency When a schedule is migrated t 12.x, by default it is disabled. After the migratin is run, it will be necessary t reinitialize them in MII 12.x. Befre yu reinitialize a schedule, make sure that it runs as expected. Only Enabled Data Servers are migrated Web Cntent The Migratin Tl nly migrates enabled data servers. Therefre, if yu want t migrate a data server that is disabled make sure t enable this server first. This als wrks the ther way arund, if yu have a server that is n lnger being used make sure t disable r remve it in All html web based references shuld use relative, nt fully qualified paths If a fully qualified URL is used, after the cntent is migrated, this URL will nt wrk in 12.x, therefre it is best t use relative paths if pssible. Suggested search terms: lcalhst, http, server name, etc. Refer t Appendix B fr search techniques. All html web based URLs and references shuld fllw case-prper requirements Here are sme examples where prblems f case sensitivity culd ccur. File extensins:.png.png,.css.css,.txt.txt and s n. File Paths: Manufacturing/AssetUtilQuery Manufacturing/assetutilquery SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 7

8 Migratin/Upgrade t SAP MII 12.x URL s: /CmpanyName/Prject/Flder /CmpanyName/prject/flder All f the abve examples wuld have wrked in IIS is nt case sensitive, and therefre mre frgiving than Java in this respect. During the click-thrugh validatin fllwing a migratin, if an image des nt appear (red X placehlder), r yur page is nt cnfrming t the style sheet class, check the case in yur bject path references. Are there any http requests t MII frm external systems? If yu have an external system sending http requests t yur MII machine. The URL path will be different fr 12.x as the server name will have changed and a prt will need t be included. The /Lighthammer web applicatin is nw /XMII D any URL s within a webpage have a Prject Name in their path that already exists? MII Cntent The Migratin Check tab will als alert yu f this scenari in the Subflders with prject name check. The migratin tl will prefix all prject names in URLs with /XMII/CM. Fr example: <img src= /SAP/Cmmn/Lg.jpg height= 100 width= 100 /> exists n a web page fr the prject SAP the migratin tl will mdify this as <img src= /XMII/CM/SAP/Cmmn/Lg.jpg height= 100 width= 100 /> If yu als have a prject named Cmmn the migratin tl with perfrm the prefix twice invalidating the URL <img src= /XMII/CM/SAP/XMII/CM/Cmmn/Lg.jpg height= 100 width= 100 /> Here is a breakdwn f what happens. The path /SAP is replaced by /XMII/CM/SAP. Next, the Migratin Tl sees the /Cmmn flder, and, knwing it is als a Prject, replaces it with /XMII/CM/Cmmn. Thus, when these tw paths are cmbined, they becme /XMII/CM/SAP/XMII/CM/Cmmn/Lg.jpg. This is nly ne such scenari; therefre, it is best t use relative paths whenever pssible t lessen this prblem. Sme areas t watch ut fr this are css files, js files, images, etc. Fllwing gd naming cnventin will help alleviate this issue. Wrkarund: Migrate the prjects separately frm each ther, which will alleviate the abve situatin. Make sure t migrate the prject with the prject name in the path first. In the abve example the SAP prject wuld migrate first and then yu will separately migrate the Cmmn prject. Files ther than transactins, query and display templates will nt be migrated frm the Lighthammer/Xacute/Transactins and Lighthammer/Illuminatr/Templates flder, mdify accrdingly The migratin tl nly lks fr transactins (.trx) and templates (.xml) in thse flders. If there are ther xml r text files in a Transactin r template subflder then these files will nt be migrated t Mst files that are nt migrated will be indicated by a Invalid file ntice in the migratin lg. Suggested search terms:.txt,.dc,.png,.xml (in the transactins r Templates flder), etc. Refer t Appendix B fr search techniques. Check usernames and passwrds in actin blcks r URLs, make sure they are NetWeaver UME cmpliant If an MII username and passwrd are used make sure they adhere t the NetWeaver passwrd plicy. If they d nt the migratin tl will mdify the passwrd t make them SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 8

9 Migratin/Upgrade t SAP MII 12.x UME cmpliant. This will break yur transactins where the username and passwrd are used. Nte the path in a Transactin Call actin is case sensitive. If nested transactin calls are failing, check the case in the actin blck s cnfigured path t the child transactin. In Actin blcks such as the "Transactin Call" blck, make sure that the path specified is in the prper case. 12.x is case sensitive. Fr example, SAP/SCM/Test is nt the same path as Sap/SCM/Test in 12.x althugh this wuld wrk in File system reading/writing shuld be dne thrugh the web rt directry if pssible. If yu are ding writing r reading directly frm the file system ther than the web rt, it is recmmended t cnsider using the web rt if pssible. In 12.x access t the file system may be mre restrictive, if yu are accessing the file system within the <drive>:/lighthammer flder structure this will n lnger be a viable ptin. The web rt is recmmended because during migratin this cntent is mre easily migrated t 12.x and is platfrm independent. Sme URL calls may nw need a username and passwrd supplied. If yu are using lcalhst fr a URL call in 11.5, it will bypass authenticatin because f the Trusted Servers, this is nt the case in 12.x. A username and passwrd must be supplied and the URL must be changed. Fr example: Type=text/xml shuld be mdified t: MII Server Name>:Prt/XMII/Illuminatr?Service=SystemInf&Mde=HstInf& Cntent-Type=text/xml&IllumLginName=Administratr&IllumLginPasswrd=sap123 r if used in a transactin use: server://xmii/illuminatr?service=systeminf&mde=hstinf&cntent-type=text/xml If yu are using a URL in a Transactin r Query it is recmmended t change t server://. Add the username and passwrd t the apprpriate fields in 12.x. Transactin xpath expressins evaluating incrrectly. Many times in an effrt t make an xpath expressin in the link editr easier t read/understand, a carriage return is placed directly at the end f a line. Fr example, in the fllwing expressin a carriage return is placed after the asterisk and : stringtrim(transactin.ordernumber)!= "" and stringtrim(transactin.operatin)!= "" After the migratin is run the statement changes t the fllwing: stringtrim(transactin.ordernumber)!= "" and stringtrim(transactin.operatin)!= "" In rder t alleviate this prblem it is always a best practice t put a space befre yu enter a carriage return. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 9

10 Migratin/Upgrade t SAP MII 12.x Migratin Tl The migratin tl has been designed with flexibility in mind, allwing administratrs t selectively migrate varius aspects f the 11.5 system including Cnfiguratin, Security, Scheduler Jbs, and Prjects. This als allws the migratin tl t be run mre than nce, typically intended fr repeated prject cntent migratin, r migratins t different 12.x systems n the netwrk. The Migratin Tl interface can be brken dwn int the fllwing five categries: 1. The Cnfiguratin categry cntains the URL and MII Administratr lgin credentials fr the 12.x server, as well as the file system lcatins fr the versin 11.5 cnfiguratin and cntent. 2. The Objects t Migrate categry cntains several ptins fr cntrlling the tasks that will be perfrmed by the migratin tl. 3. The Prjects categry cntains the list f the rt cntent flders fund in the directry lcatins prvided in the Cnfiguratin categry. 4. The Lg Output area cntains the display area fr lgging messages during the executin f the migratin prcess. 5. The Migratin Check Tab, reprts MII cntent that requires manual interventin fr a successful migratin. This check shuld be run befre the Migratin f cntent. Refer the Migratin Check sectin fr mre details. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 10

11 Migratin/Upgrade t SAP MII 12.x Objects t Migrate The Cnfiguratin ptin includes the majrity f the server side administratin settings, such as System Prperties, Data Servers, Time Perids and Schedules, User and Rle based Navigatin, Cntent Links, Data Access, System Security, and thers. The Security ptin will migrate native xml based users and rles that were created in MII versin 11.5 int UME and will belng t the UME Database Datasurce. The user t rle relatinships are als preserved inside UME. When the Security ptin is enabled fr a migratin, the migratin lg shuld be reviewed carefully afterwards fr infrmatin abut pre-existing users r rles, and user passwrd related issues. The Scheduler Jbs ptin will migrate all cnfigured scheduler tasks, but will mark them as disabled t avid any ptential cnflicts. The Prjects ptin will create prjects fr the names checked in the Prjects list and migrate cntent such as Query Templates, Display Templates, Animated Objects, Business Lgic Transactins, html pages, images, as well as thers int the 12.x system. The Selected Prjects Only ptin, which is nly relevant when the Prjects ptin is als selected, will nly imprt cntent fr the Prjects selected in the Prjects list. Imprtant Pints Fr specific details n the breakdwn f specific bjects in each f these categries, and prject related dependencies please refer t the help dcumentatin. Please review and cnsult the Cmpnent Upgrade Guide (Under Installatin Guides) fr details specific t the effrts perfrmed by the migratin tl as well as the ptins included in the interface. Server URL - is t the MII 12.x server including prt (i.e.. name>:prt) Username and Passwrd - is fr a NW UME user. This user must have the XMII Administratrs r XMII Super Administratr (fr 12.1 and greater) rle assigned t it. If yu are migrating users the user must have permissin t create users n the UME. Observe the name f the lg file shwn in the utput windw and review this file fr any specific errrs that may have been encuntered during the upgrade prcess Read Nte Nte: When migrating prjects it is best t check Prjects AND Selected Prjects Only rather than just selecting Prjects. The reasn fr checking bth Prjects and Selected Prjects Only is if yu select just the Prjects checkbx, all prjects will get migrated. Prjects that are nt selected will be migrated t the Default prject flder. If yu chse t run the migratin tl again with a prject that has already been migrated. Currently this prject wuld be lcated in the Default prject flder. In rder t create a prject with this name, first delete the prject ut f the Default prject flder. Otherwise it will update the Default Prject and a new prject flder will nt be created. The Migratin Tl first lks in the Default prject flder. If the prject is fund in there, it will update the files in the Default prject. Nte: It is pssible t run the Migratin Tl n anther system instead f the 11.5 system. In rder t d s, the flder structure n the secnd machine needs t mimic the Lighthammer (<Drive>:/Lighthammer) and Web Rt (<Drive>:/Inetpub/wwwrt) flders. The best apprach is t zip up the entire Lighthammer and Web Rt directries. The Migratin Tl can be run as many times as needed. It will d inserts and updates, s cntent already migrated r n the system will nt be deleted. The Migratin Tl is deplyed t the fllwing directry <drive>:\usr\sap\sid\sys\glbal fr a Windws machine. Lk in the deplyment lg file fr the exact path, it is dependant the OS r search fr the migrate.bat file. Depending n the size and extent f yur applicatin, the Migratin Tl may run fr a few minutes t hurs, in rder t publish all f the MII cntent up t the NetWeaver database. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 11

12 Migratin/Upgrade t SAP MII 12.x The Refresh Prjects buttn will reevaluate the Cnfig Directry and Web Directry flder structure fr updated MII cntent (templates, transactins, web cntent). This will prvide an updated list f prjects with their crrespnding pririty. Migratin Check The Migratin Check tab allws a persn respnsible fr migrating MII cntent t evaluate what technical cnflicts there will be befre actually migrating the cntent. The migratin checks will allw a mre seamless and successful upgrade prcess. Belw is sme general infrmatin n the Migratin Check tab: Cnfig and Web directries crrespnd t 11.5 flder paths Can be ran multiple times Generates separate lg file which can be exprted t a spreadsheet (XMIIPreMigratin_yyyymmdd_hhmmss.lg) Lg file cntains ptential issues which shuld be remediated befre cntent migratin is dne. Nte: A prject is a flder structure at least ne f the fllwing levels: wwwrt, Illuminatr\Templates, Xacute\Transactins SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 12

13 Migratin/Upgrade t SAP MII 12.x The Migratin Check tab checks the fllwing 11 areas fr issues: 1. Nn-Standard Themes First, the tl checks wwwrt\illuminatr\themes fr XSL & XML files that are default files that have been mdified r new custm files utside f a prject flder. Then with these results, checks Lighthammer\Cnf subflders where XSL/XML files are used Checks \Illuminatr\Stylesheets flder fr default files that have been mdified r new custm files Check ignres files in wwwrt\illuminatr\themes\src flder 2. Default Hmepage Cnsistency Checks \wwwrt directry and subflders fr Camel case r upper case HTM/HTML files named index r default NetWeaver s web server will have cnflicts with web pages nt in lwer case. 3. Reference Dcuments Checks Lighthammer\Xacute\ReferenceDcuments fr Reference Dcuments (XML files) utside f a prject. If yu are using the Reference Schema Lader actin, yur Reference Dcument must be stred within a prject flder under the mentined path abve, if nt it will nt migrate. 4. Nn-Standard SVG Objects First it checks Lighthammer\Xacute\SVGObjects flder and subflders fr standard MII SVG files that have been mdified r new custm files utside f a prject flder. Then with results frm abve, checks Xacute\AnimatedObjects flder and subflders where SVG bjects are referenced. Frm here a list f Animated Objects (SVA) are displayed fr manual crrectin. Refer t the Nn-Standard Animated Objects sectin 6 fr mre details. 5. Subflders with Prject Name Checks fllwing flder paths fr pssibly duplicated prject names: Lighthammer\Xacute\Transactins Lighthammer\Illuminatr\Templates wwwrt\ Refer t D any URL s within a webpage have a Prject name in their path that already exists? check pint in the Web Cntent sectin abve fr an explanatin. 6. Nn-Standard Animated Objects Changes made t the Default Animated r SVG Objects in 11.5 will nt migrate t 12.x. On the 11.5 system Animated and SVG bjects must be stred within a Prject in rder t Migrate Animated and SVG bjects shuld be stred in the same flder structure as the Transactins they are used in. Fr example if the transactin (LineSpeed.trx) uses an animated bject which is stred in the C:/Lighthammer/Xacute/Transactins/SAP flder, then yu shuld stre yur Animated Object related t that transactin in C:/Lighthammer/Xacute/AnimatedObjects/SAP flder and nt the rt AnimatedObjects( C:/Lighthammer/Xacute/AnimatedObjects ) directry. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 13

14 Migratin/Upgrade t SAP MII 12.x Checks Lighthammer\Xacute\AnimatedObjects flder and subflders fr.sva files that are default files that have been mdified r new custm files utside f a prject flder With results frm previus step, checks Lighthammer\Xacute\Transactins flder and subflders where SVA bjects are referenced. List f transactins are displayed. 7. Nn-Standard Stylesheets Checks wwwrt\illuminatr\stylesheets fr XSL and CSS files that are default files that have been mdified r new custm files utside f a prject flder Stylesheets nt belnging t a prject r part f the defaults will nt migrate. Default files cannt be verwritten in the 12.x envirnment. 8. Duplicate File Names Nte: Migratin is dne based n file names, nt file extensins s duplicated file names will be verwritten in NetWeaver database Checks Lighthammer\Xacute\Transactins flder and subflders fr duplicated file names in Lighthammer\Illuminatr\Templates flder and subflders Example: Xacute\Transactins\Prject1\OEEE.trx and \Illuminatr\Templates\Prject1\OEEE.tqta Check is case insensitive. This prblem will nt ccur with Web cntent as file extensins are used which will differentiate files with the same name. The migratin lg file will als write an errr message, if a duplicate file tries t migrate. The errr message will lk similar t the fllwing: Errr prcessing file <File Path/File> already exists with a different file type <extensin>. 9. Flder Naming Cnsistency Checks wwwrt\ flder names with same name in Lighthammer\Illuminatr\Templates and Lighthammer\Xacute directries Example: wwwrt\my_flder and \Lighthammer\Illuminatr\Templates\MyFlder Check is case insensitive. Als remves spaces and underscres between text befre searching. 10. Special Files Checks wwwrt directry and subflders fr any.asp r.aspx files MII cannt display.asp r.aspx files. NetWeaver supprts ASP pages used in prtal applicatins with SAP PDK fr.net 11. Lng Scheduled Jb Names Checks Lighthammer\Scheduler flder fr jbs with ver 50 characters in file name as these will nt migrate. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 14

15 Migratin/Upgrade t SAP MII 12.x Prjects In MII 12.x, cntent is nw gruped int prjects. A prject is defined as any tp level flder in the fllwing flders: 1. \Lighthammer\Illuminatr\Templates 2. \Lighthammer\Illuminatr\Transactins 3. \wwwrt The prject pririties fr the Migratin Tl are as fllws: HIGH flder name fund in all three lcatins MEDIUM flder name fund in tw ut f the three lcatins LOW flder name fund in ne f the three lcatins A Prject pririty has NO bearing n whether r nt t migrate cntent t 12.x. The pririties are a way t shw hw the cntent will align in MII 12.x, if it were migrated. Nt all prjects will have a High pririty. In this example the first fur prjects have been fund in all three lcatins and have been priritized as HIGH. The Training flder has been fund in the Web rt and Templates flders giving it a MEDIUM pririty level. The Testing flder has nly been fund in the Templates flder and has been priritized as LOW. Nte: Each file name within a prject must have a unique name Nte: Mapped netwrked drives will nt wrk. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 15

16 Migratin/Upgrade t SAP MII 12.x Accessing and Publishing Files in 12.x In MII 12.x there are multiple ways t reference files lcated within the Wrkbench. server:// This reslves t the lcal URL string, server:// is equivalent t It is fr dealing with cntent n the web applicatin. Fr example, yu can use it in a Http Pst actin blck r xml query. The reasn fr using this is it will easily enable the transprt f transactins and queries thrugh yur landscape. If yur prt changes frm ne system t anther, using this Url will slve that prblem during transprt. Used in MII cntent nly i.e. transactins, queries, etc. Will nt reslve if used in a web page. db:// r web:// Used in MII cntent nly i.e. transactins, queries, etc. Will nt reslve if used in a web page. The prefix web:// will autmatically aut-publish cntent t the file system and the database. The db:// will nly insert the cntent int the database. Use Case: A transactin saves 20 image files, fr use n a web page. Best Practice is t use the db:// prefix t initially push the cntent int the database. Once all files are in the database, use the blwut URL t publish cntent t the file system. Make sure t specify the prject flder where the image files are stred. By batching up the files this way, it will save n file I/O time, making the transactin run quicker. If nly a few files need t be published as web cntent, then it is recmmended t use the web:// prefix. Blwut URL: cntaining cntent t publish> All file paths belw pint t the same lcatin: web://prject/flder/file web://prject/web/flder/file db://prject/web/flder/file /XMII/CM/<Prject Name>/ Used in Web cntent nly t reference a.css,.js, image file, etc. n yur webpage, fr example /XMII/CM/OEE/Cmmn/SAP.css SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 16

17 Migratin/Upgrade t SAP MII 12.x File Search and Replace After the Migratin Check Tl is run, sme manual mdificatin f files may be needed. Belw is a way t use the Windws Search feature t help ut with finding these files if they are nt specified. By Default Windws des nt search.irpt r.trx extensins, in rder t enable Windws t search fr all unknwn extensins. Use the fllwing link US;309173&FR=1 and refer t Methd 2. MII Cntent: Transactins that save files directly t the file system. Fr example a search fr C:\Lighthammer\Illuminatr can be changed t save files t the MII DB (Web tab) instead. This may nt be necessary as it depends n hw yur applicatin wrks. The best way t g abut this is t d a search fr a lcal drive path. Find the transactins that save files lcally. Then determine if this can be changed, if s mdify the file in 12.x t pint t a Prject path. Transactins r queries that use will need t be changed t use server:// as this is equivalent t Als yu will need t add MII username and passwrd t the actin blcks. Lcalhst des nt bypass security as it did in Flders mst cmmnly searched. Transactins (.trx) - are stred in <Drive>:/Lighthammer/Xacute/Transactins Query and Display templates (.xml) - are stred in <Drive>:/Lighthammer/Illuminatr/Templates Animated Objects (.sva r.svg) - <Drive>:\Lighthammer\Xacute\AnimatedObjects and <Drive>:\Lighthammer\Xacute\SVGObjects respectively Reference Dcuments (.xml r.xsd) are stred in <Drive>:\Lighthammer\Xacute\ReferenceDcuments Web Cntent: Case-sensitivity (CSS, JSP, images, file extensin, etc.) When nt using relative paths a search fr <Drive>:/<web rt path> r abslute paths is recmmended. Fr example, C:/Inetpub/wwwrt is the standard IIS web rt directry. Yu will mst likely want t d a search fr the fllwing file extensins (*.htm, *.html, *.irpt, *.xsl, *.xslt, *.xml, *.css, *.js, etc) This list is nt all inclusive, just a start - it will depend n yur applicatin. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 17

18 Migratin/Upgrade t SAP MII 12.x The abve example illustrates searching fr a transactin in which a file is saved directly n the server. Nw we want t change the file path t save t the 12.x database (WEB tab). On the 11.5 machine, search the C:/Lighthammer/Xacute/Transactins flder. Transactins are stred with the.trx extensin. If yu were t pen up a transactin, it is just an xml file. A wrd r phrase n which t search culd be the file path where files are being stred lcally. Fr example, C:/Temp. N wildcards are accepted, it is searching fr the phrase yu entered in the dcument. Finally the transactin in 12.x will need t be changed after the Migratin Tl is run. This will prvide a list f all the transactins that need t be changed. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 18

19 Migratin/Upgrade t SAP MII 12.x Path 2: NW Upgrade Tl The Upgrade Tl fr NetWeaver is an independent prgram, run n the same bx as MII It will upgrade yur existing NetWeaver system frm 7.0 t (CE EPH1). During this upgrade prcess it will als upgrade MII 12.0 t 12.1 r Refer t the installatin guides n Service Marketplace fr step by step details. The NetWeaver Upgrade Tl is dwnladed frm Service Marketplace and is lcated under MII (in the Upgrade sectin) and nt NetWeaver. It is a gd practice t backup all f yur MII prjects and cnfiguratins as well as NetWeaver cnfiguratins fr befre upgrading. A caveat is that the upgrade can nly be run nce. Fr mre specifics abut prerequisites refer t the Migratin guide at Befre Upgrading d the fllwing: Backup MII Prjects and Cnfiguratins Read SAP Ntes and (Ntes refer t all MII versins) Obtain NW and make it is accessible n the server. Obtain yur Slutin Manager Key. Read the Cmpnent Upgrade Guide fr SAP MII 12.x. There will be sectin(s) specific t the NW Upgrade Tl. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 19

20 Migratin/Upgrade t SAP MII 12.x Starting the Upgrade Tl s Frntend Once the NetWeaver Upgrade Tl executable has been started navigate t the fllwing URL click n the Start Upgrade Frntend (SDT GUI) link. Once started the upgrade tl can be paused and restarted at a later instance if needed. Fr a simpler startup prcess, make sure that yu start the upgrade GUI frm a machine where Java Webstart is installed. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 20

21 Migratin/Upgrade t SAP MII 12.x Upgrade Wizard The Upgrade Wizard is where yu will spend the majrity f yur time. There are 8 different stages that the upgrade runs thrugh. They are: 1. The Initializatin screen is the starting pint fr the upgrade and des a system analysis. 2. The Extractin screen will begin the extractin f all relevant tls and cntent frm NetWeaver The Cnfiguratin screen is where all the infrmatin required t run the upgrade is entered such as passwrds, upgrade strategy, infrmatin abut cmpnents, add-ns and supprt packages that yu want included in the upgrade. 4. Checks which make sure that all infrmatin was entered and all prerequisites are met. 5,6,7. Preprcessing/Dwntime/PstPrcessing is where upgrade f NetWeaver is dne and will just run in the backgrund. 8. Finalizatin is cnfirmatin that the upgrade was successful and will prvide yu with lgs if errrs ccurred. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 21

22 Migratin/Upgrade t SAP MII 12.x Adding MII t the Upgrade During the Cnfiguratin step, the Java Upgrade tl scans the EPS inbx fr applicable supprt packages such as MII t deply during the upgrade. Use the drp-dwn menu n the right t include r exclude any applicable supprt package fr any given cmpnent. Befre the upgrade is set t run, yu will need t place the MII installatin.sca file in this directry (EPS inbx). When the upgrade is dne running MII will be updated t versin 12.2 alng with all f yur MII cntent. Nte: After the Upgrade Tl is run yu must manually deply the MIIAdmin.sca file using the CE Update Manager tl if upgrading t MII Ignre this step if upgrading t MII Cnfirm the list f cmpnents t be deplyed n the target system during the upgrade. Use the drp-dwn menu n the right t include/exclude selected cmpnents. Make sure the MII 12.2 is selected and included t be deplyed. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 22

23 Migratin/Upgrade t SAP MII 12.x Path 3: CE Update Manager Since MII 12.1 and 12.2 bth use NW CE EHP1, it is pssible t upgrade an existing MII 12.1 system by deplying the MII 12.2 SCA files directly n the system. This will update all MII cntent t 12.2 specificatins upn deplyment. This MII upgrade must be dne using the CE Update Manager. This tl is lcated at \usr\sap\<sid>\sys\exe\uc\ntamd64\ceupdatemanager.exe n a Windws machine. JSPM is nt lnger a valid upgrade ptin fr mving frm MII 12.1 t MII It still an ptin fr deplying patches and service packs n bth versins. Migratin is dne n the same server Migratin f Prjects and Cnfiguratins dne upn deplyment f the MII applicatin Must deply the fllwing tw MII SCA files: MIIADMIN00_0.sca XMII00_0.sca SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 23

24 Migratin/Upgrade t SAP MII 12.x Path 4: Cnfiguratin and Prject Migratin Migrating the Cnfiguratins and Prject files will enable yu t migrate MII Cntent frm a lwer MII versin t a higher MII versin, fr example: MII 12.0 t MII 12.1 r MII 12.2 MII 12.1 t MII 12.2 This is accmplished thrugh the Prjects and Cnfiguratins administrative pages lcated under the System Management categry n the MII Menu. Once all the infrmatin is exprted, all that is needed is t imprt the zip files int the 12.x system. The migratin is dne during the imprt prcedure and will mdify the cntent t lastest MII release. Since nly MII cntent is being migrated, tw servers will be needed, ne fr each NetWeaver/MII versin. Nte it is nt pssible it exprt MII cntent frm a higher release t a lwer ne. It is recmmended t lk at the help, in rder t determine what cntent each Cnfiguratin categry cntains fr imprt/exprt. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 24

25 Migratin/Upgrade t SAP MII 12.x Pst Migratin and Upgrade Tasks Specific t the Migratin Tl (11.5 t 12.x) After the Migratin Tl has run its curse, check the migratin lg file fr errrs. The lg file will be lcated in the same flder as the Migrate.bat file and is stred in the fllwing frmat XMIIMigratin_yyyyMMDD_hhmmss.lg. Check ver the Migratin lg file carefully as t nt miss anything; this is a vital pst migratin task. It shuld be the first step t be dne after a migratin. Check the Migratin lg file fr the fllwing: Migrated user passwrds which did nt adhere t the UME s passwrd plicy. A new passwrd will be created in the lg as demnstrated belw: Generate passwrd fr user Admin is 2XU8hycbS8e&R, riginal passwrd did nt meet the minimum passwrd requirements Files nt migrated t the 12.x system I.E. Invalid file C:\Lighthammer\Xacute\Transactins\SAP\OEE.pdf ignred Duplicate files, an entry will be created in the lg similar t the fllwing: Errr prcessing file <File Path/File> already exists with a different file type <extensin>. General Fllwing a successful applicatin migratin d an exhaustive click thrugh f the applicatin t cnfirm functinality f the upgraded cntent. Test the authenticatin and authrizatin by using user defined accunts and rles, nt just relying n an Administratr lgin. Mnitr and/r Observe the fllwing: Sun Java Cnsle in the brwser fr any client-side applet and JavaScript related issues in the web cntent. Brwser status bar which can indicate script errrs. This can be enhanced by enabling the Internet Explrer Advanced setting fr brwsing: Display a ntificatin abut every script errr. NetWeaver lgs fr errr messages. Reprt any MII 12.x r Migratin Tl bugs/issues thrugh the Custmer Supprt Prtal ( fr attentive reslutin. Reinitialize any Schedules migrated, test fr crrect functinality befre enabling. Step thrugh the applicatin, it wuld be a gd idea t have a Custmer representative wh knws the applicatin well t help. Verify if Custm Actin blcks are used, that they have been upladed, deplyed and recnfigured fr the new 12.x release. Verify the crrect JDBC driver(s) are upladed and deplyed in the MII Administrative screen. NW JDBC r JRA Cnnectin may need t be set up again depending n what path was taken. Refer t the NetWeaver help fr where this setup is dne. NetWeaver cnfiguratin is dne in the Visual Administratr SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 25

26 Migratin/Upgrade t SAP MII 12.x NetWeaver (CE EHP1) Cnfiguratin is dne using NetWeaver Administratr (NWA under Cnfiguratin Management -> Infrastructure -> Destinatins). Verify IDOC and Message Listeners are setup and initialized Depending n yur Upgrade/Migratin path the listeners may nt update. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 26

27 Migratin/Upgrade t SAP MII 12.x Related Cntent Fr mre infrmatin, visit the Manufacturing hmepage. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 27

28 Migratin/Upgrade t SAP MII 12.x Cpyright Cpyright 2011 SAP AG. All rights reserved. N part f this publicatin may be reprduced r transmitted in any frm r fr any purpse withut the express permissin f SAP AG. The infrmatin cntained herein may be changed withut prir ntice. Sme sftware prducts marketed by SAP AG and its distributrs cntain prprietary sftware cmpnents f ther sftware vendrs. Micrsft, Windws, Excel, Outlk, and PwerPint are registered trademarks f Micrsft Crpratin. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PwerVM, Pwer Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPwer, PwerPC, BatchPipes, BladeCenter, System Strage, GPFS, HACMP, RETAIN, DB2 Cnnect, RACF, Redbks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivli and Infrmix are trademarks r registered trademarks f IBM Crpratin. Linux is the registered trademark f Linus Trvalds in the U.S. and ther cuntries. Adbe, the Adbe lg, Acrbat, PstScript, and Reader are either trademarks r registered trademarks f Adbe Systems Incrprated in the United States and/r ther cuntries. Oracle is a registered trademark f Oracle Crpratin. UNIX, X/Open, OSF/1, and Mtif are registered trademarks f the Open Grup. Citrix, ICA, Prgram Neighbrhd, MetaFrame, WinFrame, VideFrame, and MultiWin are trademarks r registered trademarks f Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks r registered trademarks f W3C, Wrld Wide Web Cnsrtium, Massachusetts Institute f Technlgy. Java is a registered trademark f Sun Micrsystems, Inc. JavaScript is a registered trademark f Sun Micrsystems, Inc., used under license fr technlgy invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and ther SAP prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f SAP AG in Germany and ther cuntries. Business Objects and the Business Objects lg, BusinessObjects, Crystal Reprts, Crystal Decisins, Web Intelligence, Xcelsius, and ther Business Objects prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f Business Objects S.A. in the United States and in ther cuntries. Business Objects is an SAP cmpany. All ther prduct and service names mentined are the trademarks f their respective cmpanies. Data cntained in this dcument serves infrmatinal purpses nly. Natinal prduct specificatins may vary. These materials are subject t change withut ntice. These materials are prvided by SAP AG and its affiliated cmpanies ("SAP Grup") fr infrmatinal purpses nly, withut representatin r warranty f any kind, and SAP Grup shall nt be liable fr errrs r missins with respect t the materials. The nly warranties fr SAP Grup prducts and services are thse that are set frth in the express warranty statements accmpanying such prducts and services, if any. Nthing herein shuld be cnstrued as cnstituting an additinal warranty. SDN - sdn.sap.cm BPX - bpx.sap.cm BOC - bc.sap.cm UAC - uac.sap.cm 2011 SAP AG 28