cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading from XI/PI7.0 to 7.1 having problems with message mapping

Former Member
0 Kudos

Hello,

We are in the process over the past week of testing our XI/PI functionality after upgrading our 7.0 XI/PI environment to PI7.1; in particular several maps that were accessible in 7.0 will not open or diaplay in 7.1 complaining of a missing node in the mapping structure. Currently working with SAP on a possible fix but wanted to know if anyone else has done a true migration on top of an existing XI/PI7.0 system and experiencing similar issues (note: the maps can execute in the runtime environment but we can't display the maps source within message mapping; this also does not occur for all maps and there is no clear consistant theme to those that can be displayed and those that can't).

The lattest issue just encountered related to message mapping is that in test mode of a map (that can be displayed) attempting to display the data queue for the mapped elements are blank no data being displayed giving an error noting that the source text of object message mapping: name of the map; has syntax errors, java area import line x, package ibm.com.xi.mapping does not exist/ import ibm.com.xi.mapping UDF:

Has anyone upgraded from PI7.0 to 7.1 and experienced errors with existing maps that worked ok (ans still work in our QX/PRD systems) in their 7.0 envirinment but encountereing strange errors once upgrated to 7.1?

Thanks

Dereck Purnell

NewellRubbermaid

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member187437
Contributor
0 Kudos

Hi,

We are also currently working on Upgradation.

Got some similar issues you have mentioned.

The mapping will work fine if you dont do any changes in PI 7.1. But if you try to edit and reactivate it may throw error.

If the std function FormatNum is used in the mapping, then it may say a argument is missing if we try to edit and save.

It was overcome by giving a space for the second parameter.

Got similar issue for FixValues Function and for UDFS which handles Context and Suppress values.

Please let us know once you have got a fix for your issues.

Former Member
0 Kudos

Here is the solution we received from SAP to address the issue, there were several mapping related issues we started havng from maps that worked in our 7.0 system prior to the upgrade to PI 7.1. I will try to encorporate the solutions in this response.

a) From Customer to SAP

1. We are unable to open some massage mapping, it is throwing

exception

2. Number Format functions throw exception.

But following issue is still unresolved:

3. When we display message queue, it throws exception

***) 05.02.2009 - 12:34:33 CET - Reply by SAP

The patch has been released at the Service Marketplace.

Please update the scas described in the note 1264871.

The "FormatNum" function issue has also been taken care in this patch.

Please go through the Note 1264871 for other behaviour changes after

upgrade. Let us know if you need any further help.

Regards,

B) From Customer to SAP

04.02.2009 - 00:23:44 CET - Info for SAP

We discovered another issue with mapping.

For some of the mappings, we are unable to display mapping queue. When

we execute, Interface mapping and Massage mapping, it works fine. But

display queue throws exception. Itu2019s not able to recognize libraries

used from dependent software component.

Please find document "Display Mapping Queue Issue" providing example

problem.

25.02.2009 - 07:05:28 CET - *Reply by SAP*

Thank you for your update. I wanted to check with "CopyValue"

function's index. It has to take an input integer and the problem that

found while debugging the opening of your mapping is that the input

was empty thus causing the exception.

I was going to suggest the intended use of "CopyValue" function.

When the input to "copyValue" is a constant, "copyValue" is totally

not necessary. Thus constant can be directly mapped to other function.

When the input is a node with values in context, you can treat one of

values say input[0] to used in mapping by using CopyValue[0].

But please make sure that input[0] will always produce a value.

Note 877964 will describe in detail on Copyvalue usage.

I am marking this Message as complete. Please confirm.