Migration Strategies Mii Sdn

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Migration/Upgrade to SAP MII 12.x

Applies to:

SAP Manufacturing Integration and Intelligence (MII). For more information, visit the Manufacturing homepage.

Summary

This paper explains the different paths for upgrading or migrating your MII environment. It provides a brief overview of the different paths and also explains some of the problem areas you may encounter. It is supplemental to the Upgrade Guides available on Service Marketplace under Installation Guides.

Author: Erik Schrampf, Kevin Yurasits and Jeremy Good

Company: SAP

Created on: 15 May, 2011



© 2011 SAP AG 2

Table of Contents

Upgrade/Migration Paths .................................................................................................................................... 3

General References and Links ....................................................................................................................... 3

Path 1: Migration Tool ......................................................................................................................................... 5

Prerequisites / Assumptions ........................................................................................................................... 5

Program Length .............................................................................................................................................. 5

Prerequisites ................................................................................................................................................... 5

Required Skill Set ............................................................................................................................................ 6

Migration Issue Checklist ................................................................................................................................ 6

Configuration ................................................................................................................................................................ 6

Web Content ................................................................................................................................................................ 7

MII Content .................................................................................................................................................................. 8

Migration Tool ............................................................................................................................................... 10

Objects to Migrate ...................................................................................................................................................... 11

Important Points ......................................................................................................................................................... 11

Migration Check ............................................................................................................................................ 12

1. Non-Standard Themes ........................................................................................................................................ 13

2. Default Homepage Consistency .......................................................................................................................... 13

3. Reference Documents ......................................................................................................................................... 13

4. Non-Standard SVG Objects ................................................................................................................................. 13

5. Subfolders with Project Name ............................................................................................................................. 13

6. Non-Standard Animated Objects ......................................................................................................................... 13

7. Non-Standard Stylesheets ................................................................................................................................... 14

8. Duplicate File Names ........................................................................................................................................... 14

9. Folder Naming Consistency ................................................................................................................................. 14

10. Special Files ........................................................................................................................................................ 14

11. Long Scheduled Job Names ................................................................................................................................ 14

Projects ......................................................................................................................................................... 15

Accessing and Publishing Files in 12.x ......................................................................................................... 16

File Search and Replace ............................................................................................................................... 17

MII Content: ............................................................................................................................................................... 17

Web Content: ............................................................................................................................................................. 17

Path 2: NW Upgrade Tool ................................................................................................................................. 19

Starting the Upgrade Tool’s Frontend ........................................................................................................... 20

Upgrade Wizard ............................................................................................................................................ 21

Adding MII to the Upgrade ............................................................................................................................ 22

Path 3: CE Update Manager............................................................................................................................. 23

Path 4: Configuration and Project Migration ..................................................................................................... 24

Post Migration and Upgrade Tasks .................................................................................................................. 25

Specific to the Migration Tool (11.5 to 12.x) ................................................................................................. 25

General.......................................................................................................................................................... 25

Related Content ................................................................................................................................................ 27

Copyright........................................................................................................................................................... 28



© 2011 SAP AG 3

Upgrade/Migration Paths

Depending on the MII version installed, different upgrade paths are available. See the matrix below to determine what options are available for your current MII version.

Migrating or Upgrading depends on what version is already installed and what version you want to move to.

• If MII 11.5 is installed then the Migration Tool will be used. It is possible to use this tool to migrate 11.5 content to a new 12.x box. If your 11.5 server is capable of running NetWeaver then migration directly on that server is also possible.

• From MII 12.0 there are two paths forward:

• First, is an in place (on box) upgrade of MII and NetWeaver using the NetWeaver Upgrade Tool. This upgrades MII from 12.0 to 12.1 or 12.2 and NetWeaver from 7.0 to 7.11 EHP1. It is done on the same server.

• The other option is creating a new MII 12.1 or 12.2 server and use MII’s Project and Configurations import/export features to transfer content.

• From MII 12.1 to 12.2 you have two options

• Perform an upgrade on the same server by just deploying the MII 12.2 SCA files using CE Update Manager.

• The other option is creating a new MII 12.2 server and use MII’s Project and Configurations import/export features.

The next few sections will cover these tools in more detail.

General References and Links

� Installation and Upgrade/Migration Guides: http://service.sap.com/instguides

� 11.5 and 12.0 guides are under: SAP xApps -> SAP xApp Manufacturing Integration and Intelligence

� 12.1 and 12.2 guides are under: SAP Business Suite Applications -> SAP Manufacturing -> SAP Manufacturing Integration and Intelligence



© 2011 SAP AG 4

� Help Documentation: http://help.sap.com

� SAP Business Suite -> SAP Manufacturing -> SAP Manufacturing Integration and Intelligence

� Ramp-up Learning Map Content: http://service.sap.com/rkt

� SAP Manufacturing

� MII 12.0 Sample Projects and Tools: https://www.sdn.sap.com/irj/sdn/manufacturing-tools

� These Tools and Projects can be setup on any 12.x release.



© 2011 SAP AG 5

Path 1: Migration Tool

The principal objective of this upgrade guide is to make the transition from SAP MII version 11.5 to 12.x as seamless as possible, and help to ensure a successful upgrade process.

Online materials have been made available for gaining a better understanding and appreciation of the new aspects of version 12.x, as well as specific content pertaining to migration from version 11.5.

Prerequisites / Assumptions

The MII application content can vary substantially in both size and scope, and the associated implementation styles and practices can impact the migration process in many ways.

� Version 11.5 application content is available, either on the existing 11.5 web server or a backup location.

� Version 12.x server is configured and operational with the latest service packs and patches.

� The latest migration tool (specific to your 12.x version) has been downloaded and installed on the same machine with the 11.5 content.

� The person performing the application readiness assessment is competent with both MII versions 11.5 and 12.x.

A customer representative who is knowledgeable in the application must play an active role in the upgrade process

Program Length

� The budgeted time and effort needed to complete the program will vary quite heavily on the nature and readiness of the application itself, the remediation efforts, as well as the time needed to test and confirm the functionality of the updated content.

� A mixture of Off-Site and On-Site time can be leveraged to streamline the upgrade efforts

� The following table attempts to gauge the effort (days) involved in the migration process

Application Complexity

Assessment Phase

Off-Site / On-Site

Migration Phase

Off-Site / On-Site Totals

Very Low 2 / 0 2 / 0 4

Low 2 / 0 2 / 2 6

Medium 2 / 2 2 / 4 10

High 4 / 2 4 / 5+ 15+

Very High 4 / 4 5 / 10+ 23+

Prerequisites

� In addition to those identified in the previous Introduction section, full customer cooperation and disclosure will be expected in order to deliver the completion of a successful upgrade



© 2011 SAP AG 6

� The application readiness exercise and Migration Check (part of the Migration Tool) can be performed while the NetWeaver team is configuring 12.x on the server. The Migration Tool cannot be run until the 12.x server is completely operational.

Required Skill Set

� SAP MII representatives

� Knowledge of both the 11.5 and 12.x version

� Troubleshooting ability

� Attention to detail

� Customer representatives

� Knowledge of the application content

� Access to additional resources as necessary

Migration Issue Checklist

With version 12.x moving away from the combination of Microsoft’s IIS and New Atlanta’s ServletExec to NetWeaver. The following list should be considered when analyzing the version 11.5 application prior to performing the migration.

� SAP WebAS is case sensitive, so all html paths to other web content including items like html/irpt, css, js, xml, images, etc. must be case proper.

� All web content references should use relative links and not have any file:// or fully qualified http references (unless absolutely necessary).

� LHSecurity user management has been completely replaced by NetWeaver’s User Management Engine (UME).

� Projects have been added as an organizational, backup, and deployment mechanism. Assume mirrored content folder locations in the 11.5 file system (The Definition of a Project for MII 12.x is explained later in the “Projects” section.)

� Configuration and Application content no longer exist on the operating system’s file system, but are now resident in the NW database.

� Custom Action blocks will need to be repackaged for deployment with 12.x.

Configuration

q Availability of JDBC driver files (jar / zip) for upload into MII version 12.x.

o SAP MII 12.x does not come pre-packaged with JDBC drivers as 11.5. Therefore, it is necessary to upload them into the 12.x system. There are two options:

§ Upload the drivers you are currently using in 11.5. The directory for the SQL and Oracle Drivers is generally <Drive>:\ServletExecAS\se-xMII\webapps\default\Lighthammer\WEB-INF\lib. Using these drivers in 12.x is recommended as you will not have to change your data source connection information.

§ Download the driver from the vendor’s website and upload to 12.x.

q UDS components and vendor API’s installed on the 11.5 server?

o If there are any UDS components or Vendor API’s on the 11.5 server you may need to move them.

q Virtual Server usage between 11.5 instances?



© 2011 SAP AG 7

o Updating the IP and Port data (server properties), will likely be needed in order to reference the associated 12.x system.

o Trusted Servers have been removed, so RemoteLoginName and RemoteLoginPassword properties will need to be utilized in place of the inbound server trust between MII servers.

q LHSecurity configuration in MII – LDAP, xml users, etc

o LHSecurity is no longer used. All Security is handled through SAP UME for connecting to LDAP, Databases, local users, etc. All 11.5 native xml users and attributes will be migrated as ‘UME Database’ Data Source objects (optional configuration in the Migration Tool).

o If a user’s password does not follow the UME’s Security Policy requirements (length, mixed case, digits, etc.), a default initial password will be generated and noted in the Migration log, for later communication to the user.

q Any unused, empty, backup or temp folders in any of the pertinent content locations have been removed

o This is an opportune time to do some best practices housekeeping and remove temp folders, backup folders and unused configuration objects, etc.

q 3rd

party custom action blocks have to be repackaged for upload into version 12.x of MII

o The classes in 12.x have changed; therefore you will need to repackage custom actions for MII transactions.

o Similar to JDBC drivers, you will need to upload and deploy your custom action jar file(s).

o Refer to the 12.x help on how to upload a Custom Action.

q Check to see what attributes for roles and users are being used

o All attributes will be migrated into the ‘Custom Attributes’ Administration page for MII. For those attributes that are also found in the NetWeaver UME they will be updated as well.

o If an attribute in NetWeaver UME has the same name as a Custom Attribute in MII. The Custom Attribute in MII will take precedence over the NetWeaver attribute.

q Confirm that all active Schedules are valid and have the proper scheduled frequency

o When a schedule is migrated to 12.x, by default it is disabled. After the migration is run, it will be necessary to reinitialize them in MII 12.x. Before you reinitialize a schedule, make sure that it runs as expected.

q Only Enabled Data Servers are migrated

o The Migration Tool only migrates enabled data servers. Therefore, if you want to migrate a data server that is disabled make sure to enable this server first.

o This also works the other way around, if you have a server that is no longer being used make sure to disable or remove it in 11.5.

Web Content

q All html web based references should use relative, not fully qualified paths

o If a fully qualified URL is used, after the content is migrated, this URL will not work in 12.x, therefore it is best to use relative paths if possible.

o Suggested search terms: localhost, http, ‘server name’, etc. Refer to Appendix B for search techniques.

q All html web based URLs and references should follow case-proper requirements

o Here are some examples where problems of case sensitivity could occur.

§ File extensions: .png ≠ .PNG, .css ≠ .Css, .txt ≠ .TXT and so on.

§ File Paths: Manufacturing/AssetUtilQuery ≠ Manufacturing/assetutilquery



© 2011 SAP AG 8

§ URL’s: /CompanyName/Project/Folder ≠ /CompanyName/project/folder

o All of the above examples would have worked in 11.5. IIS is not case sensitive, and therefore more forgiving than Java in this respect. During the click-through validation following a migration, if an image does not appear (red X placeholder), or your page is not conforming to the style sheet class, check the case in your object path references.

q Are there any http requests to MII from external systems?

o If you have an external system sending http requests to your MII machine. The URL path will be different for 12.x as the server name will have changed and a port will need to be included.

o The /Lighthammer web application is now /XMII

q Do any URL’s within a webpage have a Project Name in their path that already exists?

o The Migration Check tab will also alert you of this scenario in the “Subfolders with project name” check.

o The migration tool will prefix all project names in URLs with /XMII/CM. For example:

§ ‘<img src=“/SAP/Common/Logo.jpg” height=“100” width=“100” />’

exists on a web page for the project “SAP” the migration tool will modify this as

§ ‘<img src=“/XMII/CM/SAP/Common/Logo.jpg” height=“100” width=“100” />’

o If you also have a project named “Common” the migration tool with perform the prefix twice invalidating the URL

§ ‘<img src=“/XMII/CM/SAP/XMII/CM/Common/Logo.jpg” height=“100” width=“100”/>’

o Here is a breakdown of what happens. The path “/SAP” is replaced by “/XMII/CM/SAP”. Next, the Migration Tool sees the “/Common” folder, and, knowing it is also a Project, replaces it with “/XMII/CM/Common”. Thus, when these two paths are combined, they become “/XMII/CM/SAP/XMII/CM/Common/Logo.jpg ”. This is only one such scenario; therefore, it is best to use relative paths whenever possible to lessen this problem.

o Some areas to watch out for this are css files, js files, images, etc. Following good naming convention will help alleviate this issue.

o Workaround: Migrate the projects separately from each other, which will alleviate the above situation. Make sure to migrate the project with the project name in the path first. In the above example the SAP project would migrate first and then you will separately migrate the Common project.

MII Content

q Files other than transactions, query and display templates will not be migrated from the Lighthammer/Xacute/Transactions and Lighthammer/Illuminator/Templates folder, modify accordingly

o The migration tool only looks for transactions (.trx) and templates (.xml) in those folders. If there are other xml or text files in a Transaction or template subfolder then these files will not be migrated to 12.0.

o Most files that are not migrated will be indicated by a “Invalid file” notice in the migration log.

o Suggested search terms: .txt, .doc, .png, .xml (in the transactions or Templates folder), etc. Refer to Appendix B for search techniques.

q Check usernames and passwords in action blocks or URLs, make sure they are NetWeaver UME compliant

o If an MII username and password are used make sure they adhere to the NetWeaver password policy. If they do not the migration tool will modify the password to make them



© 2011 SAP AG 9

UME compliant. This will break your transactions where the username and password are used.

q Note the path in a “Transaction Call” action is case sensitive.

o If nested transaction calls are failing, check the case in the action block’s configured path to the child transaction. In Action blocks such as the "Transaction Call" block, make sure that the path specified is in the proper case. 12.x is case sensitive. For example, “SAP/SCM/Test” is not the same path as “Sap/SCM/Test” in 12.x although this would work in 11.5.

q File system reading/writing should be done through the web root directory if possible.

o If you are doing writing or reading directly from the file system other than the web root, it is recommended to consider using the web root if possible. In 12.x access to the file system may be more restrictive, if you are accessing the file system within the <drive>:/Lighthammer folder structure this will no longer be a viable option. The web root is recommended because during migration this content is more easily migrated to 12.x and is platform independent.

q Some URL calls may now need a username and password supplied.

o If you are using localhost for a URL call in 11.5, it will bypass authentication because of the Trusted Servers, this is not the case in 12.x. A username and password must be supplied and the URL must be changed.

o For example: http://localhost/Lighthammer/Illuminator?Service=SystemInfo&Mode=HostInfo&Content-Type=text/xml should be modified to: http://<12.0 MII Server Name>:Port/XMII/Illuminator?Service=SystemInfo&Mode=HostInfo& Content-Type=text/xml&IllumLoginName=Administrator&IllumLoginPassword=sap123 or if used in a transaction use: server://XMII/Illuminator?Service=SystemInfo&Mode=HostInfo&Content-Type=text/xml

o If you are using a URL in a Transaction or Query it is recommended to change http://localhost to server://. Add the username and password to the appropriate fields in 12.x.

q Transaction xPath expressions evaluating incorrectly.

o Many times in an effort to make an xPath expression in the link editor easier to read/understand, a carriage return is placed directly at the end of a line. For example, in the following expression a carriage return is placed after the asterisk “and”:

§ stringtrim(Transaction.OrderNumber) != "" and stringtrim(Transaction.Operation) != ""

After the migration is run the statement changes to the following:

§ stringtrim(Transaction.OrderNumber) != "" and stringtrim(Transaction.Operation) != ""

o In order to alleviate this problem it is always a best practice to put a space before you enter a carriage return.



© 2011 SAP AG 10

Migration Tool

The migration tool has been designed with flexibility in mind, allowing administrators to selectively migrate various aspects of the 11.5 system including Configuration, Security, Scheduler Jobs, and Projects. This also allows the migration tool to be run more than once, typically intended for repeated project content migration, or migrations to different 12.x systems on the network.

The Migration Tool interface can be broken down into the following five categories:

1. The Configuration category contains the URL and MII Administrator login credentials for the 12.x server, as well as the file system locations for the version 11.5 configuration and content.

2. The Objects to Migrate category contains several options for controlling the tasks that will be performed by the migration tool.

3. The Projects category contains the list of the root content folders found in the directory locations provided in the Configuration category.

4. The Log Output area contains the display area for logging messages during the execution of the migration process.

5. The Migration Check Tab, reports MII content that requires manual intervention for a successful migration. This check should be run before the Migration of content. Refer the “Migration Check” section for more details.



© 2011 SAP AG 11

Objects to Migrate

The Configuration option includes the majority of the server side administration settings, such as System Properties, Data Servers, Time Periods and Schedules, User and Role based Navigation, Content Links, Data Access, System Security, and others.

The Security option will migrate native xml based users and roles that were created in MII version 11.5 into UME and will belong to the UME Database Datasource. The user to role relationships are also preserved inside UME. When the Security option is enabled for a migration, the migration log should be reviewed carefully afterwards for information about pre-existing users or roles, and user password related issues.

The Scheduler Jobs option will migrate all configured scheduler tasks, but will mark them as disabled to avoid any potential conflicts.

The Projects option will create projects for the names checked in the Projects list and migrate content such as Query Templates, Display Templates, Animated Objects, Business Logic Transactions, html pages, images, as well as others into the 12.x system.

The Selected Projects Only option, which is only relevant when the Projects option is also selected, will only import content for the Projects selected in the Projects list.

Important Points

For specific details on the breakdown of specific objects in each of these categories, and project related dependencies please refer to the help documentation.

� Please review and consult the “Component Upgrade Guide” (Under Installation Guides) for details specific to the efforts performed by the migration tool as well as the options included in the interface.

� Server URL - is to the MII 12.x server including port (i.e.. http://<server name>:port)

� Username and Password - is for a NW UME user. This user must have the “XMII Administrators” or “XMII Super Administrator” (for 12.1 and greater) role assigned to it. If you are migrating users the user must have permission to create users on the UME.

� Observe the name of the log file shown in the output window and review this file for any specific errors that may have been encountered during the upgrade process

� Read Note 149461.

� Note: When migrating projects it is best to check “Projects” AND “Selected Projects Only” rather than just selecting “Projects”.

o The reason for checking both ‘Projects’ and ‘Selected Projects Only’ is if you select just the ‘Projects’ checkbox, all projects will get migrated. Projects that are not selected will be migrated to the Default project folder. If you choose to run the migration tool again with a project that has already been migrated. Currently this project would be located in the Default project folder. In order to create a project with this name, first delete the project out of the Default project folder. Otherwise it will update the Default Project and a new project folder will not be created. The Migration Tool first looks in the Default project folder. If the project is found in there, it will update the files in the Default project.

� Note: It is possible to run the Migration Tool on another system instead of the 11.5 system. In order to do so, the folder structure on the second machine needs to mimic the Lighthammer (<Drive>:/Lighthammer) and Web Root (<Drive>:/Inetpub/wwwroot) folders. The best approach is to zip up the entire Lighthammer and Web Root directories.

� The Migration Tool can be run as many times as needed. It will do inserts and updates, so content already migrated or on the system will not be deleted.

� The Migration Tool is deployed to the following directory <drive>:\usr\sap\SID\SYS\global for a Windows machine. Look in the deployment log file for the exact path, it is dependant the OS or search for the “migrate.bat” file.

� Depending on the size and extent of your application, the Migration Tool may run for a few minutes to hours, in order to publish all of the MII content up to the NetWeaver database.



© 2011 SAP AG 12

� The Refresh Projects button will reevaluate the ‘Config Directory’ and ‘Web Directory’ folder structure for updated MII content (templates, transactions, web content). This will provide an updated list of projects with their corresponding priority.

Migration Check

The Migration Check tab allows a person responsible for migrating MII content to evaluate what technical conflicts there will be before actually migrating the content. The migration checks will allow a more seamless and successful upgrade process. Below is some general information on the Migration Check tab:

· Config and Web directories correspond to 11.5 folder paths

· Can be ran multiple times

· Generates separate log file which can be exported to a spreadsheet (XMIIPreMigration_yyyymmdd_hhmmss.log)

o Log file contains potential issues which should be remediated before content migration is done.

Note: A project is a folder structure at least one of the following levels: “wwwroot”, “Illuminator\Templates”, “Xacute\Transactions”



© 2011 SAP AG 13

The Migration Check tab checks the following 11 areas for issues:

1. Non-Standard Themes

• First, the tool checks “wwwroot\Illuminator\Themes” for XSL & XML files that are default files that have been modified or new custom files outside of a project folder. Then with these results, checks “Lighthammer\Conf” subfolders where XSL/XML files are used

• Checks “\Illuminator\Stylesheets” folder for default files that have been modified or new custom files

• Check ignores files in “wwwroot\Illuminator\Themes\src” folder

2. Default Homepage Consistency

• Checks “\wwwroot” directory and subfolders for Camel case or upper case HTM/HTML files named “index” or “default”

• NetWeaver’s web server will have conflicts with web pages not in lower case.

3. Reference Documents

• Checks “Lighthammer\Xacute\ReferenceDocuments” for Reference Documents (XML files) outside of a project. If you are using the Reference Schema Loader action, your Reference Document must be stored within a project folder under the mentioned path above, if not it will not migrate.

4. Non-Standard SVG Objects

• First it checks “Lighthammer\Xacute\SVGObjects” folder and subfolders for standard MII SVG files that have been modified or new custom files outside of a project folder.

• Then with results from above, checks “Xacute\AnimatedObjects” folder and subfolders where SVG objects are referenced. From here a list of Animated Objects (SVA) are displayed for manual correction.

• Refer to the Non-Standard Animated Objects section 6 for more details.

5. Subfolders with Project Name

• Checks following folder paths for possibly duplicated project names:

• “Lighthammer\Xacute\Transactions”

• “Lighthammer\Illuminator\Templates”

• “wwwroot\”

• Refer to “Do any URL’s within a webpage have a Project name in their path that already exists?” check point in the Web Content section above for an explanation.

6. Non-Standard Animated Objects

• Changes made to the Default Animated or SVG Objects in 11.5 will not migrate to 12.x.

• On the 11.5 system Animated and SVG objects must be stored within a Project in order to Migrate

• Animated and SVG objects should be stored in the same folder structure as the Transactions they are used in.

• For example if the transaction (LineSpeed.trx) uses an animated object which is stored in the“C:/Lighthammer/Xacute/Transactions/SAP” folder, then you should store your Animated Object related to that transaction in “C:/Lighthammer/Xacute/AnimatedObjects/SAP” folder and not the root AnimatedObjects(“C:/Lighthammer/Xacute/AnimatedObjects”) directory.



© 2011 SAP AG 14

• Checks “Lighthammer\Xacute\AnimatedObjects” folder and subfolders for .SVA files that are default files that have been modified or new custom files outside of a project folder

• With results from previous step, checks “Lighthammer\Xacute\Transactions” folder and subfolders where SVA objects are referenced. List of transactions are displayed.

7. Non-Standard Stylesheets

• Checks “wwwroot\Illuminator\Stylesheets” for XSL and CSS files that are default files that have been modified or new custom files outside of a project folder

• Stylesheets not belonging to a project or part of the defaults will not migrate. Default files cannot be overwritten in the 12.x environment.

8. Duplicate File Names

• Note: Migration is done based on file names, not file extensions so duplicated file names will be overwritten in NetWeaver database

• Checks “Lighthammer\Xacute\Transactions” folder and subfolders for duplicated file names in “Lighthammer\Illuminator\Templates” folder and subfolders

• Example: Xacute\Transactions\Project1\OEEE.trx and \Illuminator\Templates\Project1\OEEE.tqta

• Check is case insensitive.

• This problem will not occur with Web content as file extensions are used which will differentiate files with the same name.

• The migration log file will also write an error message, if a duplicate file tries to migrate. The error message will look similar to the following:

• “Error processing file <File Path/File> already exists with a different file type <extension>”.

9. Folder Naming Consistency

• Checks “wwwroot\” folder names with same name in “Lighthammer\Illuminator\Templates” and “Lighthammer\Xacute” directories

• Example: wwwroot\My_Folder and \Lighthammer\Illuminator\Templates\MyFolder

• Check is case insensitive. Also removes spaces and underscores between text before searching.

10. Special Files

• Checks “wwwroot” directory and subfolders for any .asp or .aspx files

• MII cannot display .asp or .aspx files. NetWeaver supports ASP pages used in portal applications with SAP PDK for .NET

11. Long Scheduled Job Names

• Checks “Lighthammer\Scheduler” folder for jobs with over 50 characters in file name as these will not migrate.



© 2011 SAP AG 15

Projects

In MII 12.x, content is now grouped into projects. A project is defined as any top level folder in the following folders:

1. \Lighthammer\Illuminator\Templates

2. \Lighthammer\Illuminator\Transactions

3. \wwwroot

The project priorities for the Migration Tool are as follows:

� HIGH – folder name found in all three locations

� MEDIUM – folder name found in two out of the three locations

� LOW – folder name found in one of the three locations

A Project priority has NO bearing on whether or not to migrate content to 12.x. The priorities are a way to show how the content will align in MII 12.x, if it were migrated. Not all projects will have a ‘High’ priority.

In this example the first four projects have been found in all three locations and have been prioritized as HIGH. The Training folder has been found in the Web root and Templates folders giving it a MEDIUM priority level. The Testing folder has only been found in the Templates folder and has been prioritized as LOW.

Note: Each file name within a project must have a unique name

Note: Mapped networked drives will not work.



© 2011 SAP AG 16

Accessing and Publishing Files in 12.x

In MII 12.x there are multiple ways to reference files located within the Workbench.

server://

• This resolves to the local URL string, “server://” is equivalent to “http://localhost:53000”. It is for dealing with content on the web application. For example, you can use it in a Http Post action block or xml query. The reason for using this is it will easily enable the transport of transactions and queries through your landscape. If your port changes from one system to another, using this Url will solve that problem during transport.

• Used in MII content only i.e. transactions, queries, etc. Will not resolve if used in a web page.

db:// or web://

• Used in MII content only i.e. transactions, queries, etc. Will not resolve if used in a web page.

• The prefix ‘web://’ will automatically auto-publish content to the file system and the database. The ‘db://’ will only insert the content into the database.

• Use Case: A transaction saves 20 image files, for use on a web page. Best Practice is to use the ‘db://’ prefix to initially push the content into the database. Once all files are in the database, use the blowout URL to publish content to the file system. Make sure to specify the project folder where the image files are stored. By batching up the files this way, it will save on file I/O time, making the transaction run quicker. If only a few files need to be published as web content, then it is recommended to use the ‘web://’ prefix.

• Blowout URL: http://<server>:<port>/XMII/Catalog?mode=blowout&folder=<projectname>/<folder containing content to publish>

• All file paths below point to the same location:

• web://Project/Folder/File

• web://Project/WEB/Folder/File

• db://Project/WEB/Folder/File

/XMII/CM/<Project Name>/…

• Used in Web content only to reference a .css, .js, image file, etc. on your webpage, for example /XMII/CM/OEE/Common/SAP.css



© 2011 SAP AG 17

File Search and Replace

After the Migration Check Tool is run, some manual modification of files may be needed. Below is a way to use the Windows Search feature to help out with finding these files if they are not specified.

By Default Windows does not search .irpt or .trx extensions, in order to enable Windows to search for all unknown extensions. Use the following link http://support.microsoft.com/default.aspx?scid=kb;EN-US;309173&FR=1 and refer to Method 2.

MII Content:

Transactions that save files directly to the file system. For example a search for “C:\Lighthammer\Illuminator” can be changed to save files to the MII DB (Web tab) instead. This may not be necessary as it depends on how your application works.

� The best way to go about this is to do a search for a local drive path. Find the transactions that save files locally. Then determine if this can be changed, if so modify the file in 12.x to point to a Project path.

Transactions or queries that use http://localhost will need to be changed to use “server://” as this is equivalent to http://localhost:<port>. Also you will need to add MII username and password to the action blocks. Localhost does not bypass security as it did in 11.5.

Folders most commonly searched.

� Transactions (.trx) - are stored in <Drive>:/Lighthammer/Xacute/Transactions

� Query and Display templates (.xml) - are stored in <Drive>:/Lighthammer/Illuminator/Templates

� Animated Objects (.sva or .svg) - <Drive>:\Lighthammer\Xacute\AnimatedObjects and <Drive>:\Lighthammer\Xacute\SVGObjects respectively

� Reference Documents (.xml or .xsd) are stored in <Drive>:\Lighthammer\Xacute\ReferenceDocuments

Web Content:

Case-sensitivity (CSS, JSP, images, file extension, etc.)

When not using relative paths a search for <Drive>:/<web root path> or absolute paths is recommended. For example, C:/Inetpub/wwwroot is the standard IIS web root directory.

� You will most likely want to do a search for the following file extensions (*.htm, *.html, *.irpt, *.xsl, *.xslt, *.xml, *.css, *.js, etc) This list is not all inclusive, just a start - it will depend on your application.



© 2011 SAP AG 18

• The above example illustrates searching for a transaction in which a file is saved directly on the server. Now we want to change the file path to save to the 12.x database (WEB tab). On the 11.5 machine, search the “C:/Lighthammer/Xacute/Transactions” folder.

• Transactions are stored with the .trx extension. If you were to open up a transaction, it is just an xml file.

• A word or phrase on which to search could be the file path where files are being stored locally. For example, “C:/Temp”.

• No wildcards are accepted, it is searching for the phrase you entered in the document.

• Finally the transaction in 12.x will need to be changed after the Migration Tool is run. This will provide a list of all the transactions that need to be changed.



© 2011 SAP AG 19

Path 2: NW Upgrade Tool

The Upgrade Tool for NetWeaver is an independent program, run on the same box as MII 12.0. It will upgrade your existing NetWeaver system from 7.0 to 7.1.1 (CE EPH1). During this upgrade process it will also upgrade MII 12.0 to 12.1 or 12.2. Refer to the installation guides on Service Marketplace for step by step details. The NetWeaver Upgrade Tool is downloaded from Service Marketplace and is located under MII (in the Upgrade section) and not NetWeaver.

It is a good practice to backup all of your MII projects and configurations as well as NetWeaver configurations for before upgrading. A caveat is that the upgrade can only be run once.

For more specifics about prerequisites refer to the Migration guide at http://service.sap.com/instguides.

Before Upgrading do the following:

q Backup MII Projects and Configurations

q Read SAP Notes 1266062 and 1240081 (Notes refer to all MII versions)

q Obtain NW 7.1.1 and make it is accessible on the server.

q Obtain your Solution Manager Key.

q Read the Component Upgrade Guide for SAP MII 12.x. There will be section(s) specific to the NW Upgrade Tool.



© 2011 SAP AG 20

Starting the Upgrade Tool’s Frontend

Once the NetWeaver Upgrade Tool executable has been started navigate to the following URL http://hostname:4239, click on the “Start Upgrade Frontend (SDT GUI)” link. Once started the upgrade tool can be paused and restarted at a later instance if needed. For a simpler startup process, make sure that you start the upgrade GUI from a machine where Java Webstart is installed.



© 2011 SAP AG 21

Upgrade Wizard

The “Upgrade Wizard” is where you will spend the majority of your time. There are 8 different stages that the upgrade runs through. They are:

1. The Initialization screen is the starting point for the upgrade and does a system analysis.

2. The Extraction screen will begin the extraction of all relevant tools and content from NetWeaver 7.0.

3. The Configuration screen is where all the information required to run the upgrade is entered such as passwords, upgrade strategy, information about components, add-ons and support packages that you want included in the upgrade.

4. Checks which make sure that all information was entered and all prerequisites are met.

5,6,7. Preprocessing/Downtime/PostProcessing is where upgrade of NetWeaver is done and will just run in the background.

8. Finalization is confirmation that the upgrade was successful and will provide you with logs if errors occurred.



© 2011 SAP AG 22

Adding MII to the Upgrade

During the Configuration step, the Java Upgrade tool scans the EPS inbox for applicable support packages such as MII to deploy during the upgrade. Use the drop-down menu on the right to include or exclude any applicable support package for any given component. Before the upgrade is set to run, you will need to place the MII installation .sca file in this directory (EPS inbox). When the upgrade is done running MII will be updated to version 12.2 along with all of your MII content.

Note: After the Upgrade Tool is run you must manually deploy the MIIAdmin.sca file using the CE Update Manager tool if upgrading to MII 12.2. Ignore this step if upgrading to MII 12.1.

Confirm the list of components to be deployed on the target system during the upgrade. Use the drop-down menu on the right to include/exclude selected components.

� Make sure the MII 12.2 is selected and included to be deployed.



© 2011 SAP AG 23

Path 3: CE Update Manager

Since MII 12.1 and 12.2 both use NW CE EHP1, it is possible to upgrade an existing MII 12.1 system by deploying the MII 12.2 SCA files directly on the system. This will update all MII content to 12.2 specifications upon deployment. This MII upgrade must be done using the CE Update Manager. This tool is located at \usr\sap\<SID>\SYS\exe\uc\NTAMD64\ceupdatemanager.exe on a Windows machine. JSPM is not longer a valid upgrade option for moving from MII 12.1 to MII 12.2. It still an option for deploying patches and service packs on both versions.

� Migration is done on the same server

� Migration of Projects and Configurations done upon deployment of the MII application

� Must deploy the following two MII SCA files:

o MIIADMIN00_0.sca

o XMII00_0.sca



© 2011 SAP AG 24

Path 4: Configuration and Project Migration

Migrating the Configurations and Project files will enable you to migrate MII Content from a lower MII version to a higher MII version, for example:

� MII 12.0 to MII 12.1 or MII 12.2

� MII 12.1 to MII 12.2

This is accomplished through the Projects and Configurations administrative pages located under the System Management category on the MII Menu. Once all the information is exported, all that is needed is to import the zip files into the 12.x system. The migration is done during the import procedure and will modify the content to lastest MII release. Since only MII content is being migrated, two servers will be needed, one for each NetWeaver/MII version.

Note it is not possible it export MII content from a higher release to a lower one.

It is recommended to look at the help, in order to determine what content each Configuration category contains for import/export.



© 2011 SAP AG 25

Post Migration and Upgrade Tasks

Specific to the Migration Tool (11.5 to 12.x)

q After the Migration Tool has run its course, check the migration log file for errors.

o The log file will be located in the same folder as the Migrate.bat file and is stored in the following format XMIIMigration_yyyyMMDD_hhmmss.log.

o Check over the Migration log file carefully as to not miss anything; this is a vital post migration task. It should be the first step to be done after a migration.

q Check the Migration log file for the following:

o Migrated user passwords which did not adhere to the UME’s password policy. A new password will be created in the log as demonstrated below:

§ “Generate password for user Admin is 2XU8ohycbS8e&R, original password did not meet the minimum password requirements”

o Files not migrated to the 12.x system

§ I.E. “Invalid file C:\Lighthammer\Xacute\Transactions\SAP\OEE.pdf ignored”

o Duplicate files, an entry will be created in the log similar to the following:

§ “Error processing file <File Path/File> already exists with a different file type <extension>”.

General

q Following a successful application migration do an exhaustive click through of the application to confirm functionality of the upgraded content.

q Test the authentication and authorization by using user defined accounts and roles, not just relying on an Administrator login.

q Monitor and/or Observe the following:

o Sun Java Console in the browser for any client-side applet and JavaScript related issues in the web content.

o Browser status bar which can indicate script errors. This can be enhanced by enabling the Internet Explorer Advanced setting for browsing: ‘Display a notification about every script error’.

o NetWeaver logs for error messages.

q Report any MII 12.x or Migration Tool bugs/issues through the Customer Support Portal (http://service.sap.com) for attentive resolution.

q Reinitialize any Schedules migrated, test for correct functionality before enabling.

q Step through the application, it would be a good idea to have a Customer representative who knows the application well to help.

q Verify if Custom Action blocks are used, that they have been uploaded, deployed and reconfigured for the new 12.x release.

q Verify the correct JDBC driver(s) are uploaded and deployed in the MII Administrative screen.

q NW JDBC or JRA Connection may need to be set up again depending on what path was taken.

o Refer to the NetWeaver help for where this setup is done.

§ NetWeaver 7.0 - configuration is done in the Visual Administrator



© 2011 SAP AG 26

§ NetWeaver 7.1.11 (CE EHP1) – Configuration is done using NetWeaver Administrator (NWA under Configuration Management -> Infrastructure -> Destinations).

q Verify IDOC and Message Listeners are setup and initialized

o Depending on your Upgrade/Migration path the listeners may not update.



© 2011 SAP AG 27

Related Content

For more information, visit the Manufacturing homepage.



© 2011 SAP AG 28

Copyright

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

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, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Migration Strategies Mii Sdn

Documents

modehostinfoamp

servicesysteminfoamp

duplicated

suggested

ce update

error processing

standard animated

custom action