Process to Migrate Reports using Migration Manager

We often face many difficulties while migration reports. Generally user’s exports all report Rpt files using SQL queries and then import all report one by one manual.

During this process we may miss some report and even lookups, this will lead to loose of time.

IBM Maximo had provided a simple solution to migrate the report.

Note: Both Source and target environment should be similar.

Below are the steps involved:

Process to Create Package in the source system

• Go To System Configuration --> Migration --> Migration Groups.
• Search for the group ‘REPORTING’.
• Duplicate the Migration group ‘REPORTING’ and rename it as REPMIGGROUP.
• Delete ‘DMKPIMAIN’ from the new Migration Objects.
• Delete ‘APPLICATION’ and DATADICTIONARY’ from Dependencies and save.
• Go To System Configuration --> Migration --> Migration Manager.
• Create new Package definition by name ‘REPMIGMGR’ with processing action    of   ‘AddChange’ and type of ‘SNAPSHOT’.
• Select ‘REPMIGGROUP’ under Migration groups.
• Provide the where class to filter reports reportname in 'buyer_activity_report.rptdesign', 'buyer_audit_report.rptdesign',….enter all reports that you want to be in the     package’)
• Change status on the package to APPR.
• Activate Package from Select Action.
• Go To ‘Package’ tab, and click on ‘Create’ button under Packages section.
• Click on ‘Distribute’ BUTTON to save the package to a physical location on application server machine. Select the target to save package.
• If the target is unavailable. Create the target using Select action--> manage    targets.

Process to Deploy Package in the target system

• In the Target environment, go To Migration Manager Application.
• From select action from the list tab, Turn Admin mode ON using ‘Manage Admin Mode’ option.(Note: Turn the Admin Mode Off once the deployment is done)
• Upload the new package using Select Action, Upload Package action.
• From Select Action, Deploy Package option to deploy the package uploaded in the above step.
• Once the deployment is complete, Go To Report Administration Generate Request Page for all the reports and set security as applicable.
• Verify that Report security has been set as applicable.

BMXAA4092E - The SMTP Host does not have a property value

Set the following value in the System properties.

• mail.smtp.host 

BMXAA7077E to perform this operation set a value for the mxe.adminEmail property.

Set the following value in the System properties.

• mxe.adminEmail

VMJ9VM015W Initialization error for library j9gc24(5): Failed to allocate default memory space Could not create the Java virtual machine.

The above Error occurs only when the JVM heap size greater than the memory resources available.

• Check the Servers JVM  Heap Size.
• Web Sphere 7.0 Administrative console -> Servers -> Server Types > WebSphere Application servers -> Click on application server (usually MXServer) -> Java and Process Management-> Process Definition -> Java Virtual Machine.
• Maximum Heap size (Xmx): 3072(Depends on Ram Size.
• Initial Heap size (Xms): 2048(not less than 512)
• Restart application server.

* If the Issue is not yet revolved .Check whether the Generic JVM arguments field is empty .If any value exits. Remove it and restart the server.

BMXAA4107E -- Because of an implementation or customization problem, the system cannot determine how the attributes of object {2} correspond to the attributes {3} of object {0}. You might need to populate the MAXLOOKUPMAP table and restart the server.

The specified attributes must have an entry in the MAXLOOKUPMAP table or be mapped in the field validation class of {2}.{1}.

In order to add MAXLOOKUPMAP there are two ways 

Through DB 

insert into maxlookupmap (target,lookupattr,targetattr,sourcekey,seqnum,allownull,source,maxlookupmapid)
values ('target','lookupattr','targetattr','sourcekey',1,0,'source',maxlookupmapseq.nextval); 

commit; 

(for db2) 

insert into maxlookupmap

(target,lookupattr,targetattr,sourcekey,seqnum,allownull,source,maxlookupmapid)

values

('target','lookupattr','targetattr','sourcekey',1,0,'source',nextval for maxlookupmapseq ) ;

Through the front End 

Identify the attribute on which maxlookupmap need to insert 

Click on maxlookupmap icon as shown 

 

Enter the required details such as target and source and etc. as shown. For example refer CONTRACTREFNUM attribute of PO object 

Restart the application server to reflect the changes

The above Error occurs only when the JVM heap size greater than the memory resources available.

 

How to deletes Start Center configuration data by specific user or for Groups

Cleanstartcenters.bat is a tool that deletes Start Center configuration data by specific user or for all users as specified in the sccleanup.xml file. Be aware that this is only available from 7.1.1.8 or above.

Without an input file, the tools deletes Start Center configuration data for all users. When users log in to Maximo afterwards, their Start Center data will get re-populated to the latest settings.
With an input file, you can delete Start Centers for all users in a certain Security Group or use a list of users to delete Start Centers or both can be used i.e. group and user.

The sample sccleanup.xml is as follows:

<?xml version="1.0" ?>

<document docid="SCCleanup">

<!-- The line below is an example of specifying an userid for removing all start center setup for the user.
This will not remove the SC template, only removes the sc configuration for the user and related data.

<startcenters>

-->
<startcenters>
<startcenterbygroup groupname="SRMSELFSERVICE"/>
<startcenterbygroup groupname="ITADMIN"/>
<startcenterbyuser userid="MMTEST"/>
<startcenterbyuser userid="TESTUSER"/>
</startcenters>
</document>

After modifying or creating the sccleanup.xml file, you will have to add an option to make it applied when running the cleanstartcenters.bat.

For example :
- To delete start center configuration for specific users or usergroups

- To delete all just run "cleanstartcenters.bat"

Difference Between Relationship and Crossover Domain

               Linked objects and crossover domains represent different configuration mechanisms that you can employ to move data from one field in an application to another field in a different application.

The term “source” refers to an originating field or application. The term “destination” refers to a target field or application. Although similar in purpose, there are distinct differences as to how these configuration mechanisms transfer data across applications. Linked objects, for example, can pass data from a source application to a target application using database relationships.

In the destination application, the data value can be read-only or read/write depending on how you configure the input field. If you configure the destination input field to be read/write, then the system automatically updates the source application and parent object if you update a displayed value.

        Crossover domains, alternatively, pass data from one application to a different application using domains. The system passes a copy of the data value from a source application to a destination application using the crossover domain as a trigger mechanism. You cannot edit the data value in the destination application. The copied data value is essentially static.

 Summary: Both Crossover and relationship plays a similar but with a two difference

• if we use a relationship to fetch data from another field (Source field) to Target Field, the value will not be saved in the database. it is visible in the front end.
• if we modify the fetched value in the target field and save it. the change will be reflected in the source field  

How to Set default values in maximo

      

         We can achieve this in three ways

1.      By using setdefaultvalue () method

2.      By using application designer àby using set default value option

3.      Through DB config

• &AUTOKEY&
•  &SYSDATE&
• &USERNAME&
• &PERSIONID& 
       
  click hire to Refer the originalpost ::