cannot create or modify global parameters

[Former Member]

Hello,

when I try to add global parameters, I can do so and they appear in the list in the global parameters dialog. When I close the dialog and open it again, the newly created parameter has vanished. Same for changes on existing parameters, the changes are not applied.

What's the reason for that?

Kind regards,

Matthias

[Former Member]

This Bug will be fixed in SAP MII 12.0 SP05

[agentry_src]

Hi Matthias,

If you are working in 11.5, the file is probably write protected in the folder where global properties are stored. Usually a good thing in production, it is a pain in development. Check your folder properties or get the sysadmin to give MII permissions to modify that file.

Good luck,

Mike

[Former Member]

Hi Mike,

were on 12.0, the globals are stored in the database, right? Hence write protection shouldn't be the reason. Any other ideas?

Thanks,

Matthias

[agentry_src]

You are actually changing it, but you have to restart the instance to have it take effect. Which version of 12.0 are you using? Supposed to be fixed in 12.1.

Mike

Edited by: Michael Appleby on Aug 13, 2008 1:57 PM

[Former Member]

I've just tested it, but also after a restart of the workbench I can't see the created or modified globals. We are running 12.0.4 Build(120). Any other ideas?

Thanks for your help,

Matthias

[agentry_src]

Matthias,

You are going to hate this answer, and I am sorry, but I meant to say restart the NW instance.

It is a bug and should be fixed in 12.0.5 and in 12.1.

Good luck,

Mike

[Former Member]

Hi,

We've restarted the NW Instance, but still the same behaviour : (

Thanks,

Matthias

[agentry_src]

Matthias,

That is odd. I think you may need to escalate this with a ticket to SAP. Please post your results when they respond.

Thanks,

Mike

[Former Member]

Hi Mike,

I've just created a SAP ticket, I'll let you know the result.

Thanks,

Matthias

[Former Member]

Mike,

I've been on 12.0.2 for a while now but has never experienced this behavior, infact I make extensive use of the Global Properties.

Is this a known bug with 12.0.4?

[agentry_src]

Hi Udayan,

That is what I have been told by two of the MII support personnel. I have worked on both 12.0.2 and 12.0.4, but did not set up Globals for either one. I did hear mention of this problem from my 12.0.2 customer, but did not experience it firsthand. I am not sure if some NW settings or the server setup (multiples with multiple nodes) might be affecting it. But you just reminded me of something to check on with them.

Matthias,

What is your NW server configuration like? Can you give us a rough idea of servers and nodes? Also what database is it built upon.

Thanks,

Mike

[Former Member]

Hi,

these are the NW configurations:

System XMT

Message Server

Host: xmtdb01a

Port: 3900

Enqueue Server

Host: xmtdb01a

Port: 3200

Database

Name: XMT

Host: xmtdb01a

Type: Oracle (Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production With the Partitioning and Data Mining options)

Software Components all components...

Name Version Applied

sap.com/SAP-JEECOR 7.00 SP15 (1000.7.00.15.0.20080216073628) 20080408151839

sap.com/SAP-JEE 7.00 SP15 (1000.7.00.15.0.20080216073456) 20080408151802

Instance JC01 All processes running

Host: xmtdb01a

OS: Linux (amd64) 2.6.5-7.244-smp

dispatcher Running

VM system properties...

PID: 27981

Name: IBM J9SE VM

Vendor: IBM Corporation

Version: 2.2

VM Parameters

Cluster

Node ID: 17346800

Kernel Version: 7.00 PatchLevel 110760.44

HTTP Port: 50100

HTTPS Port: 50101

P4 Port: 50104

Telnet Port: 50108

server0 Running

VM system properties...

PID: 27982

Name: IBM J9SE VM

Vendor: IBM Corporation

Version: 2.2

VM Parameters

Cluster

Node ID: 17346850

Kernel Version: 7.00 PatchLevel 110760.44

SDM Running

VM

PID: 27983

SDM Port: 50118

Cheers,

Matthias

[Former Member]

Hi all,

here is the answer of the SAP ticket:

This has been identified as a bug and will be fixed in SP05. SP05 is in testing at the minute and should be released shortly.

Cheers,

Matthias

[agentry_src]

Matthias,

I did touch base with my old customer. They had an issue on a number of things caused by multiple nodes on multiple servers. Apparently they would do a change like the global properties and it would be saved on one server. Then the servers would synchronize and the old settings were wiping out the new. There was a sequence of update, save, shutdown for the two servers which would force the synchronization to work (overwrite the old with the new). I am working from home and it is written down on my desk. I will update with the sequence tomorrow when I get back.

You may also want to touch base with a NW professional for some assistance with this. There is some documentation out there, but I have no idea where. Perhaps a post on the NW forum would provide the answer.

Good luck,

Mike