MergingWorkOrderTracking(CM) Features into Work Order Tracking (Tr)

IBM Maximo for Transportation MergingWorkOrderTracking(CM) Features into Work Order Tracking (Tr) Version 7.5.1

Note Before using this information and the product it supports, read the information in Notices on page 9. This edition applies to version 7, release 5, modification 1 of IBM Maximo for Transportation and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2010, 2013. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents Chapter 1. Overview......... 1 How merging affects modifications....... 1 Prerequisites.............. 1 Chapter 2. Merging the Work Order Tracking applications......... 3 Merging presentations........... 3 Step 1: Make a backup of both Work Order Tracking applications.......... 3 Step 2: Create initial changes in the product descriptors.............. 3 Step 3: Specify the Work Order Tracking (CM) menu items that are to be copied into Work Order Tracking (Tr)............. 4 Step 4: Run updatedb to apply the changes in the database............... 5 Step 5: Redefine bean classes........ 5 Step 6: Authorize the menus........ 6 Step 7: Review and rearrange the layout of the application elements in the now-merged Work Order Tracking (Tr) application....... 6 Step 8: Check the results......... 6 Merging reports............. 7 Accessing help for Work Order Tracking (CM) features in the merged Work Order Tracking (Tr) application............... 7 Notices............... 9 Trademarks.............. 10 Copyright IBM Corp. 2010, 2013 iii

iv IBM Maximo for Transportation: Merging Work Order Tracking (CM) Features into Work Order Tracking (Tr)

Chapter 1. Overview The purpose of merging applications is to extend one application, called the target application, by adding menus, reports, and UI controls (such as fields, dialog boxes, and menus) from another application, called the external source application. The process that is described here applies specifically to the merging of the Work Order Tracking applications from two industry solutions. The Work Order Tracking (Tr) application from IBM Maximo for Transportation is the target application. The Work Order Tracking (CM) application from IBM Maximo Asset Configuration Manager is the external source application. The Work Order Tracking (CM) application features are merged into the Work Order Tracking (Tr) application. Work Order Tracking (Tr) and Work Order Tracking (CM) are clones of the same core Work Order Tracking application. How merging affects modifications Prerequisites IBM Maximo Asset Management lets you apply modifications to an application, such as adding new UI controls, rearranging existing ones, editing menus, and so on. The merging process does not support the merging of any UI control modifications from the external source application. Source application modifications must be manually applied to the target application after the merging process. For example, a new tab that was added to Work Order Tracking (CM) is not added to Work Order Tracking (Tr) by the merging process. The tab must be manually added to Work Order Tracking (Tr) if you need the added tab in the merged application. Modifications that you applied to the target application remain in place after the merging process. Unmodified UI controls that are brought from Work Order Tracking (CM) by the merging process are placed in Work Order Tracking (Tr) among the out-of-the-box UI controls and any modified UI controls that you might have added to Work Order Tracking (Tr). To perform the merging process, you need the following skills: v Familiarity with editing XML files v Familiarity with Maximo Asset Management configuration applications such as Application Designer, Security Groups, and Report Administration The following products must be properly installed: v Maximo Asset Management 7.5 or later, plus the latest corresponding hotfix. v Maximo for Transportation 7.5.1 or later, plus the latest corresponding hotfix. v Maximo Asset Configuration Manager 7.5.1 or later, plus the latest corresponding hotfix. IBM 2010, 2013 1

2 IBM Maximo for Transportation: Merging Work Order Tracking (CM) Features into Work Order Tracking (Tr)

Chapter 2. Merging the Work Order Tracking applications Merging presentations Merging the Work Order Tracking applications consists of two main tasks: v Merging the presentations v Merging the reports Merging presentations is the process of moving Work Order Tracking (CM) (PLUSAWO) application UI controls and menu items into Work Order Tracking (Tr) (PLUSTWO). Merging presentations consists of eight main steps: 1. Make a backup of both applications. 2. Create initial changes in the product descriptors. 3. Specify the Work Order Tracking (CM) menu items that are to be copied into Work Order Tracking (Tr). 4. Run updatedb to apply the changes to the database. 5. Redefine bean classes. 6. Authorize the menus. 7. Review and rearrange the layout of the Work Order Tracking (CM) actions within Work Order Tracking (Tr). 8. Check the results. Step 1: Make a backup of both Work Order Tracking applications Back up both Work Order Tracking (Tr) and Work Order Tracking (CM) before you make changes. 1. Start the application server (IBM WebSphere Application Server or Oracle WebLogic Server). 2. Log into Maximo Asset Management. 3. Open the Application Designer application. 4. Open the PLUSTWO application (the Work Order Tracking (Tr) application). 5. Export the application definition. 6. Save the generated page into an XML file. 7. Open the PLUSAWO application (the Work Order Tracking (CM) application). 8. Export the application definition. 9. Save the generated page into an XML file. Step 2: Create initial changes in the product descriptors Specify information to indicate that all presentation items (tabs, fields, and so on) are to be merged from Work Order Tracking (CM) into Work Order Tracking (Tr). Important: It is best to revise XML with an XML editor application. If you copy and paste text from this document into tags in your code, ensure that, in your tags, all single Copyright IBM Corp. 2010, 2013 3

quotes are straight single quotes ('). Some editors render the straight single quotes (') as close single quotes ( ) after pasting. Close single quotes in your tags can generate errors when you run updatedb. 1. Open the following file in any text editor: <Maximo root>\applications\maximo\ properties\product\transportation.xml 2. Inside the <product> tag, under <lastdbversion>, add the following content: <depends>aviation</depends> That content explicitly establishes a dependence link between Transportation and Asset Configuration Manager. 3. Inside the <extensions> tag, add an <extendpresentation> tag with the following content: <extendpresentation app= PLUSTWO baseapp= PLUSAWO product= aviation > </extendpresentation> That tag specifies that all the UI controls of the PLUSAWO application from Asset Configuration Manager are to be added to the PLUSTWO application. 4. Inside the <extensions> tag, also add the following content: <class extends= psdi.webclient.beans.workorder.workorderappbean >psdi.plust. webclient.beans.plustwo.plustwoappbean</class> <class extends= psdi.webclient.beans.workorder.wochangestatusbean >psdi. plust.webclient.beans.plustwo.plustwochangestatusbean</class> 5. Save the file. 6. Open the following file in any text editor: <Maximo root>\applications\maximo\ properties\product\aviation.xml 7. Add the following content inside the <extensions> tag: <class extends= psdi.webclient.beans.workorder.workorderappbean >psdi.plusa.webclient. beans.workorder.plusawoappbean</class> <class extends= psdi.webclient.beans.workorder.wochangestatusbean >psdi.plusa. webclient.beans.workorder.plusawochangestatusbean</class> 8. Save the file. When updatedb is run (step 4), the first inserted <class> tag causes the application bean class from Work Order Tracking (Tr) to extend the one from Work Order Tracking (CM). The second inserted class tag causes the Change Status bean class from Work Order Tracking (Tr) to extend the one from Work Order Tracking (CM). Step 3: Specify the Work Order Tracking (CM) menu items that are to be copied into Work Order Tracking (Tr) The merging process does not, by default, copy the menu items from Work Order Tracking (CM) to Work Order Tracking (Tr). You must select the MAXMENU and SIGOPTION records that are to be copied to Work Order Tracking (Tr). 1. Open the following file in any text editor: <Maximo root>\applications\maximo\ properties\product\transportation.xml 2. Go to the <Maximo root>\tools\maximo\transportation folder. 3. Run the menusdiff tool (menusdiff.bat in Microsoft Windows or menusdiff.sh in UNIX). The tool accepts a parameter with the name of the file to be generated. (For more information, invoke the tool with the h parameter). If the parameter is not provided, the default file name is results.xml. 4. Open the generated file in any text editor. 5. Copy all <add_sigoption> and <add_maxmenu> tags from the generated file and add them inside the <extendpresentation> tag from transportation.xml. 4 IBM Maximo for Transportation: Merging Work Order Tracking (CM) Features into Work Order Tracking (Tr)

6. For each <add_sigoption> tag that was added to transportation.xml, change the app value from "PLUSAWO" to "PLUSTWO". 7. For each <add_maxmenu> tag that was added to transportation.xml, change the moduleapp value from "PLUSAWO" to "PLUSTWO". 8. Optional: Edit the <add_sigoption> and <add_maxmenu> tags that you add to transportation.xml. Each of the tags will become either a SIGOPTION record or a MAXMENU record in Work Order Tracking (Tr). You can prevent any individual record from being inserted by removing the corresponding tag from the file. 9. Save the transportation.xml file. Step 4: Run updatedb to apply the changes in the database To apply the changes that you made in step 3 to the database, you must run the updatedb.bat file. 1. Shut down the application server. 2. Go to <Maximo root>\tools\maximo. 3. Run updatedb.bat. 4. Start the application server and log into Maximo Asset Management. Step 5: Redefine bean classes Now that the Work Order Tracking (CM) elements are merged into Work Order Tracking (Tr), you must redefine the bean classes in the post-merge presentation to ensure that events are properly handled. 1. In Maximo Asset Management, open the Application Designer application. 2. Open the PLUSTWO application. 3. Export the application definition. 4. Save the generated page into an XML file. 5. Open the file in any text editor. 6. Find the line that contains the following text: id="plustwo" 7. In that line, replace the beanclass value with "psdi.plust.webclient.beans.plustwo.plustwoappbean". The result should be a line similar to the following line: <presentation id="plustwo" resultstableid="results_showlist" mboname="workorder" orderby="wonum" beanclass="psdi.plust.webclient.beans.plustwo.plustwoappbean" version="7.1.0.0"> 8. Find the line that contains the following text: id="common_task_table" 9. In that line, replace the beanclass value with "psdi.plust.webclient.beans.plustwo.plustwotasksbean". The result should be a line similar to the following line: <datasrc beanclass="psdi.plust.webclient.beans.plustwo.plustwotasksbean" id="common_task_table" orderby="wosequence,taskid" relationship="showtasks"/> 10. Find the line that contains the following text: id="actuals_actuals_aclabor_aclabor_table" 11. In that line, replace the beanclass value with "psdi.plust.webclient.beans.plustwo.plustactuallaborbean". The result should be a line similar to the following line: <table beanclass="psdi.plust.webclient.beans.plustwo.plustactuallaborbean" id="actuals_actuals_aclabor_aclabor_table" label="labor" relationship="showactuallabor"> 12. Find the line that contains the following text: id="actuals_actuals_actools_actools_table" Chapter 2. Merging the Work Order Tracking applications 5

13. In that line, replace the beanclass value with "psdi.plust.webclient.beans.plustwo.plustactualtoolsbean". The result should be a line similar to the following line: <table beanclass="psdi.plust.webclient.beans.plustwo.plustactualtoolsbean" id="actuals_actuals_actools_actools_table" label="tools" relationship="showactualtool"> 14. Find the line that contains the following text: id="status" 15. In that line, replace the beanclass value with "psdi.plust.webclient.beans.plustwo.plustwochangestatusbean". The result should be a line similar to the following line: <dialog beanclass="psdi.plust.webclient.beans.plustwo.plustwochangestatusbean" id="status" label="change Status" relationship="wochangestatus" savemode="onload"> 16. Find the line that contains the following text: id="list_status" 17. In that line, replace the beanclass value with "psdi.plust.webclient.beans.plustwo.plustwochangestatusbean". The result should be a line similar to the following line: <dialog beanclass="psdi.plust.webclient.beans.plustwo.plustwochangestatusbean" id="list_status" label="change Status" relationship="wochangestatus"> 18. Save the file. 19. Open the Application Designer application. 20. Click Import Application Definition. 21. Browse for the file that you edited and click OK. Step 6: Authorize the menus The Select Action menu entries from Work Order Tracking (CM) are now available in Work Order Tracking (Tr). You now must grant permissions to your users to access actions. 1. In Maximo Asset Management, open the Security Groups application. 2. Configure the access permissions. Step 7: Review and rearrange the layout of the application elements in the now-merged Work Order Tracking (Tr) application The copying of menu items, tabs, table windows, fields, and so on that is done during the merging process attempts to mimic the arrangement from Work Order Tracking (CM). However, the resulting arrangement of the copied items in Work Order Tracking (Tr) might be different, due to existing Work Order Tracking (Tr) elements. You can rearrange the application elements. 1. In Maximo Asset Management, open the Application Designer application. 2. Open the PLUSTWO application. 3. Use the options to modify the Select Action, Toolbar, and Search menus. Because the Work Order Tracking (CM) UI controls are now available in Work Order Tracking (Tr), you can also change the layout of those elements in Application Designer, if necessary. Step 8: Check the results The merging of presentations is complete. Check your work. v Check that all selected menu items from Work Order Tracking (CM) appear in the now-merged Work Order Tracking (Tr) menus. 6 IBM Maximo for Transportation: Merging Work Order Tracking (CM) Features into Work Order Tracking (Tr)

v Merging reports v Check that all previously existing menu items from Work Order Tracking (Tr) remain in the now-merged Work Order Tracking (Tr) menus. Check that the fields that are specific to Work Order Tracking (CM) appear in the intended positions on the now-merged Work Order Tracking (Tr) screens. If necessary, repeat one or more of the previous steps to make corrections. If you have any reports that are specific to your Work Order Tracking (CM) application, follow the specified steps to make the reports available in the merged Work Order Tracking (Tr) application. 1. Copy <Maximo root>\reports\birt\reports\plusawo\plusareports.xml to <Maximo root>\reports\birt\reports\plustwo. 2. Open the <Maximo root>\reports\birt\reports\plustwo\plusareports.xml file in any text editor. 3. For each <report> tag, the value of the <attribute> tag with name="filename" must refer to the Asset Configuration Manager.rptdesign file, so the value has to be prefixed with../plusawo/. For example: if the current value is <attribute name="filename">plusawo_report_name.rptdesign </attribute> it must be changed to <attribute name="filename">../plusawo/ plusawo_report_name.rptdesign</attribute> 4. Save the file. 5. Rebuild the Maximo EAR file. 6. Start the application server (IBM WebSphere Application Server or Oracle WebLogic Server). 7. Log in to Maximo Asset Management. 8. Go to Administration > Reporting > Report Administration. 9. From the Select Action menu, select Set Application Security. 10. On the Applications table window, select the PLUSTWO application. 11. In the Application Level Security table, click New Row to add a record. 12. Specify a group in the Group field. 13. In the new record, select the All check box. 14. Repeat the preceding three steps for each new group. 15. Click OK to save the changes. 16. In the Report Administration application, generate the request pages, either by displaying each report and clicking Generate Request Page, or by clicking Generate Request Pages on the List tab. The merging of reports is complete. Check that all reports from Work Order Tracking (CM) are now available in Work Order Tracking (Tr). Accessing help for Work Order Tracking (CM) features in the merged Work Order Tracking (Tr) application Merging the Work Order Tracking applications does not affect the installed help for the Work Order Tracking (Tr) and Work Order Tracking (CM) applications. You can access help for Work Order Tracking (CM) features from the navigation pane on the help window. Chapter 2. Merging the Work Order Tracking applications 7

Prerequisites The merging of the Work Order Tracking (CM) application into the Work Order Tracking (Tr) application should be complete. Maximo Asset Management help should be installed and deployed. Maximo for Transportation help should be installed and deployed. Maximo Asset Configuration Manager help should be installed and deployed. Procedure To access help for the Work Order Tracking (CM) features that are now merged into the Work Order Tracking (Tr) application, follow these steps: 1. Open the Work Order Tracking (Tr) application. 2. On the title bar, click Help, then click Work Order Tracking (Tr) Help. This provides access to help for the original, pre-merged Work Order Tracking (Tr) application features. 3. In the navigation pane of the help window, click the plus sign (+) to expand the Maximo Asset Configuration Manager help. 4. Expand the help for Managing and synchronizing data for production. 5. Click Managing work orders. This provides access to help for the Work Order Tracking (CM) features, which are now merged into the Work Order Tracking (Tr) application. Alternatively, you can enter a search phrase in the Search field above the navigation pane. For example, if you specify work packages in the Search field, then click Go, topics about work packages are displayed in the results list. Clicking on a work packages topic from Maximo Asset Configuration Manager help provides another means of entry into the help for Work Order Tracking (CM) features. 8 IBM Maximo for Transportation: Merging Work Order Tracking (CM) Features into Work Order Tracking (Tr)

Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM 2010, 2013 9

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: U.S.A.IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/ copytrade.shtml Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. 10 IBM Maximo for Transportation: Merging Work Order Tracking (CM) Features into Work Order Tracking (Tr)

Printed in USA