SAP MII 12.0 Upgrade Program - Archive · 2019. 11. 12. · ©SAP AG 2007, SAP MII 12.0 Upgrade Program / Jeremy Good & Erik Schrampf / 7 Upgrade Program – Criteria (2 of 2) Prerequisites

SAP MII 12.0 Upgrade Program

Jeremy Good & Erik Schrampf

SAP Labs - ASM Manufacturing

July 3, 2008

Introduction and Prerequisites

Upgrade Program

Upgrade Process

Follow Up

Appendixes

© SAP AG 2007, SAP MII 12.0 Upgrade Program / Jeremy Good & Erik Schrampf / 3

Introduction and Prerequisites (1 of 2)

The principal objectives of this upgrade program is to make the transition from SAP MII version 11.5 to 12.0 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, as well as specific content pertaining to migration from version 11.5.

General References and Links– Guides: http://service.sap.com/instguides– Help Documentation:

http://help.sap.com/saphelp_xmii120/helpdata/en/index.htm– Ramp-up Learning Map Content:

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000691323&_SCENARIO=01100035870000000202&

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


Introduction and Prerequisites (2 of 2)

The partner/customer created 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.

Prerequisites / Assumptions– Version 11.5.x application content is available, either on the existing 11.5.x

web server or a backup location– Version 12.0 server is configured and operational with the latest service packs

and patches– The latest migration tool 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.0– A customer representative who is knowledgeable in the application must play

an active role in the upgrade process


Appendixes

Upgrade Process

Follow Up

Upgrade Program


Upgrade Program – Criteria (1 of 2)

The following criteria have been identified to detail and support the Upgrade Program and the associated efforts.

Client Engagement Goals– Shorten the upgrade cycle time– Reduce the technical and development support load– Customer satisfaction

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

42 / 02 / 0Very Low

14+4 / 4+4 / 2High

4 / 4

2 / 2

2 / 0

Assessment Phase

Off-Site / On-Site

4 / 6+

2 / 4

2 / 2

Migration Phase

Off-Site / On-Site

6Low

18+Very High

10Medium

TotalsApplication Complexity


Upgrade Program – Criteria (2 of 2)

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

– The application readiness exercise can be performed while the NetWeaver team is configuring 12.0 on the server, but the Migration Tool cannot be run until the 12.0 server is completely operational

Required Skill Set– SAP MII representatives

Knowledge of both the 11.5 and 12.0 versionsTroubleshooting abilityAttention to detail

– Customer representativesKnowledge of the application contentAccess to additional resources as necessary


Upgrade Program

Appendixes

Follow Up

Upgrade Process


Upgrade Process - Getting Started

With version 12.0 moving away from the combination of Microsoft’s IIS and New Atlanta’s ServletExec to NetWeaver 7.0 (2004s). 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 htm/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 (See Appendix A for more information)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.0.


Upgrade Process: Configuration (1 of 2)

Availability of JDBC driver files (jar / zip) for upload into MII version 12.– SAP MII 12.0 does not come pre-packaged with JDBC drivers as 11.5 did. Therefore it is

necessary to upload them into the 12.0 system. There are two options you can take: 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.0 is recommended as you will not have to change your data source connection information.Download the driver from the vendor’s website.

UDS components and vendor API’s installed on the 11.5 server?– If there are any UDS components or Vendor API’s on the 11.5 server you may need to move

them.Virtual Server usage between 11.5 instances?– Updating the IP and Port data-server properties will likely be needed in order to reference the

associated 12.0 system.– 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.LHSecurity configuration in MII – LDAP, xml users, etc– LHSecurity is no longer used, all Security is handled through the 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).

– 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.

Any unused, empty, backup or temp folders in any of the pertinent content locations have been removed– This is an opportune time to do some best practices housekeeping and remove temp folders,

backup folders, unused configuration objects, etc.


Upgrade Process: Configuration (2 of 2)

3rd party custom action blocks have to be repackaged for upload into version 12.0 of MII– The classes in 12.0 have changed, therefore you will need to repackage custom actions for MII

transactions.– Similar to JDBC drivers, you will need to upload and deploy your custom action jar file(s).– To download the Guide on how create actions for 12.0 go to

https://www.sdn.sap.com/irj/sdn/manufacturing-tools, click on the “xMII 12.0 Sample Projects and Tools” link. You will then be able to download the “Custom Action Developer Kit”.

Check to see what attributes for roles and users are being used– All attributes will be migrated into the ‘Custom Attributes’ of MII. For those attributes that are also

found in the NetWeaver UME they will be updated as well.– 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.

Confirm that all active Schedules are valid and have the proper scheduled frequency– When a schedule is migrated to 12.0, by default it is disabled. After the migration is run, it will be

necessary to reinitialize them in MII 12.0. Before you reinitialize a schedule make sure that it runs as expected.

Only Enabled Data Servers are migrated– 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.– 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.


Upgrade Process: Web Content (1 of 2)

All html web based references should use relative, not fully qualified paths– If a fully qualified URL is used, after the content is migrated, this URL will not work in

12.0, therefore it is best to use relative paths if possible.– Suggested search terms: localhost, http, ‘server name’, etc. Refer to Appendix B for

search techniques.

All html web based URLs and references should follow case-proper requirements– 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/assetutilqueryURL’s: /CompanyName/Project/Folder ≠ /CompanyName/project/folder

– All of the above examples would have worked in 11.5 as 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.


Upgrade Process: Web Content (2 of 2)

Are there any http requests to MII from external systems?– If you have an external system sending http requests to your MII machine. The URL path will be

different for 12.0 as the server name will have changed and a port will need to be included.– The /Ligthammer web application is now /XMII

Do any URL’s within a webpage have a Project name in their path that already exists?– The migration tool will prefix all project names in URLs with /XMII/CM. For example, if a URL such as:

‘<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” />’

– 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”/>’

– 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.

– Some areas to watch out for this are css files, js files, images, etc. If you follow good naming convention you should not run into this problem.

– 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.


Upgrade Process: MII Content (1 of 2)

Animated and SVG Objects– Changes made to the Default Animated or SVG Objects in 11.5 will not migrate to 12.0.– 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.

Reference Documents and Schemas– On the 11.5 system Reference Documents and Schemas must be stored within a Project in order to

Migrate. This is similar to the way Animated and SVG objects behave in the above point.

Files other than transactions, query and display templates will not be migrated from the Lighthammer/Xacute/Transactions and Lighthammer/Illuminator/Templates folder, modify accordingly– 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.

– Most files that are not migrated will be indicated by a “Invalid file” notice in the migration log.– Suggested search terms: .txt, .doc, .png, .xml (in the transactions or Templates folder), etc. Refer to

Appendix B for search techniques.


Upgrade Process: MII Content (2 of 2)

Duplicate file names within the same folder structure on your 11.5 system, for example:– Note this will only happen with Transactions and Query or Display templates– C:\Lighthammer\Illuminator\Templates\SAP\AssetUtilization.xml– C:\Lighthammer\Xacute\Transactions\SAP\AssetUtilization.trx– After migration a Project called “SAP” will be created. Extensions are not shown in the

Workbench’s ‘Content’ tab, therefore the first file to be migrated is the file Workbench opens. All other files after this are not migrated into 12.0. In this example the file that migrates first is the query or display template. This will cause the transaction file not to be migrated and the Workbench will open the query/display template (.xml file).

– This is also the case for Animated Object (.svg and .sva files), the .sva file is migrated first with the Migration Tool. Therefore the .sva file will open in then Workbench.

– 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 write an error message to the log 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>”. If you look for this error in the migration log file you can find which files where missed and then modify the file name and re-migrate. Remember that if this transaction, query/display or animated object are used in a web page, transaction, schedule, etc. to modify the path accordingly.


Upgrade Process: MII Content – Transactions (1 of 2)

Check usernames and passwords in action blocks or URLs, make sure they are NetWeaver UME compliant– 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 UME compliant. This will break your transactions where the username and password are used.

Note the path in a “Transaction Call” action is case sensitive.– 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.0 is case sensitive. For example, SAP/SCM/Test is not the same path as Sap/SCM/Test in 12.0 although this would work in 11.5.

File system reading/writing should be done through the web root directory if possible. – 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.0 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.0 and is platform independent.


Upgrade Process: MII Content – Transactions (2 of 2)

Some URL calls may now need a username and password supplied.– 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.0. A username and password must be supplied and the URL must be changed.

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

– 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.0.

Transaction xPath expressions evaluating incorrectly.– 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) != "" andstringtrim(Transaction.Operation) != ""

After the migration is run the statement changes to the following:stringtrim(Transaction.OrderNumber) != "" andstringtrim(Transaction.Operation) != ""

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


Upgrade Process – Running the Tool (1 of 2)

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

– This guide is located at http://service.sap.com/instguides -> SAP xApps -> MII -> 12.0

Server URL - is to the MII 12.0 Server including Port (i.e.. http://<server name>:port)Username and Password - is for a UME, MII 12.0 user. This user must have the “XMII Administrators” role assigned to it. If you are migrating users it must have permission to create users on the UME.Fill out the required information in the Configuration, Objects to Migrate, and Projects sections.Press the ‘Start Migration’ buttonObserve 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 processRefer to Note: 1149461 for known problems with the Migration Tool B9 and earlier.Note: When migrating projects it is best to check “Projects” and “Selected Projects Only” rather than just selecting “Projects”


Upgrade Process – Running the Tool (2 of 2)

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 Windows machine. Look in the deployment log file for the exact path, it is dependant the OS or do a 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.


Follow Up (1 of 2)

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

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.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.Check the log file for the following:– 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”

– Files not migrated to the 12.0 systemI.E. “Invalid file C:\Lighthammer\Xacute\Transactions\SAP\OEE.pdf ignored”

– 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>”.


Follow Up (2 of 2)

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

Test the authentication and authorization by using user defined accounts and roles, not just relying on an Administrator loginMonitor and/or Observe the following:– Sun Java Console in the browser for any client-side applet and JavaScript

related issues in the web content– 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’.

– NetWeaver logs for error messagesReport any MII 12.0 or Migration Tool bugs/issues through the Customer Support Portal (http://service.sap.com) for attentive resolutionReinitialize any Schedules migrated, test for correct functionality before enabling.Step through the application, it would be a good idea to have a Customer Representative who knows the application well to help.


Upgrade Program

Upgrade Process

Follow Up

Appendixes

AppendixesA: Project Source Location

B: File Search and Replace

C: Accessing and Publishing Files

D: Logging


Appendix A: Project Source Locations (1 of 2)

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


Appendix A: Project Source Locations (2 of 2)

The ‘Config Directory’ and ‘Web Directory’ settings point to local file system where the MII content can be found. The default location will point to C:/Lighthammer and C:/inetpub/wwwroot as shown in this example. Note: Mapped networked drives will not work.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.The Templates and Transactions folders are located in the directory dictated by the ‘Config Directory’ path. The Webroot is located in the directory dictated by the ‘Web Directory’ path. The three screen shots (previous slide) show the root folder level locations that the Migration Tool evaluates to determine a projects priority. – The project priorities are as follows:

HIGH – folder name found in all three locationsMEDIUM – folder name found in two out of the three locations LOW – folder name found in one of the three locations

– 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.

A Project priority has no bearing on whether or not to migrate content to 12.0. It is just a way to show how the content will align in 12.0, if it were migrated. Not all projects will have a ‘High’ priority.Please review the documentation for further details on how projects are migrated into the 12.0 system.

AppendixA: Project Source Location



D: Logging


Appendix B: File Search and Replace

General: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.0 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.


Appendix B: File Search and Replace: Example 1

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.0 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 were 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.0 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.




D: Logging


Appendix C: Accessing and Publishing files in 12.0

server://– This resolves to the local URL string, as server:// -> 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 point to the same location: web://Project/Folder/Fileweb://Project/WEB/Folder/Filedb://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




D: Logging


Appendix D: Logging

http://<server>:<port>Logging in MII 12.0 has changed from the 11.5 version. All log files are now stored in the NetWeaver DB

Log Management is no longer an option in the MII Menu as in 11.5. Listed below are the two options for accessing the log files for MII:

– NetWeaver Web Interface

– Standalone Log Viewer

The screenshot above is for the Basic NetWeaver Administration, it has options for UME, System Information, NetWeaver Administration and more.

The log files are located in the “SAP NetWeaver Administrator” link or you can type in “http://<server>:<port>/nwa” which will take you directly to the page.


Appendix D: Monitoring

Note: The active user will need permission to access the logs and traces.


Appendix D: Logs and Tracers

By default there are no predefined views for MII you will have to create them:MII (Warning Level) - Filter by Content

Application -> contains -> xmiiandSeverity -> is greater than or equal to -> warning


Appendix D: Stand Alone Log Viewer

Advantages:The Stand Alone log viewer is

quicker than the web based version, it loads all logs at once. The initial startup time will take longer, but after the initial load time navigation of the logs will be quicker.

Disadvantage:Not as intuiative as the web

based version. Need to have Stand Alone Log

Viewer installed on system, it is not web based.

If you are not able to find the Stand Alone Log Viewer, do a search on the <Drive>/usr folder for Logviewer.bat.

The active user will need permission to access the Log Viewer.


Appendix D: Log Viewer Essentials

Local Logs -> Drive (C:) -> usr/sap -> Instance name (F02\JC30) -> j2ee -> Server0 -> log

The log files MII uses in the Stand Alone viewer are:

applications.log – This log is easier to use and find what you need.

defaultTrace.trc – This log will contain full java stack Traces for errors, it will log everything making it more difficult to find items.

Your best option is to first look into the Applications.log first. Then if needed you can then take a more in depth lookinto the defaultTrace once you have a specified time range.

Filtering options are also available and can be setup as we showed for the web interface.


Special Thanks to our Partners!

A special thank you to the following integration partners who helped us refine the Upgrade Program materials by attending a three day workshop on February 12-14, 2008.

Global Automation Partners - Michel Renard ([email protected])

Infodat, Inc. - Joe Montagna ([email protected])

NEORIS Brasil - Flávio Carneiro Maeda ([email protected])

SEAL Consulting Inc. - Vaidy Iyer ([email protected])

Tata Consultancy Services - Shubhashish Chaudhuri ([email protected] )

Vesta Partners - Rich Crossan ([email protected])


Copyright 2007 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, 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 in several other countries all over the world. 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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.


Copyright 2007 SAP AG. Alle Rechte vorbehalten

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower und PowerPCsind Marken oder eingetragene Marken der IBM Corporation.

Adobe, das Adobe Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern.

ORACLE® ist eine eingetragene Marke der ORACLE Corporation.

UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.

Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.

HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.

JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie.

MaxDB ist eine Marke von MySQL AB, Schweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge , und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet.

Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden.

SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.