Yeah, AIE is very finicky after an upgrade or refresh from production to 
another environment. Once those jobs get corrupted, it's hard to get them back 
in order. Did you keep your old 7.6.0.0 environment around as a backup? If so, 
you might consider uninstalling/reinstalling AIE and you can export your AIE 
Data exchanges from you old 7.6.0 reference server to the new server. 
Here's what I did:
I am not sure how this works in Linux but in Windows under the BMC Software\ 
AtriumCore directory there a subdirectory one called UninstallBMCAtriumCore. 
You can run an uninstall from there, but unselect everything except Atrium 
Integration Engine. That is how you uninstall AIE. Be careful if you are in a 
server group because when you reinstall it, it will put the server group name 
in the ar monitor file and some of the pluginsvr_config files. Search for the 
pluginsvr files and make sure that they have the application server name, not 
the server group name in them.
 There is not that much of a change between 7.60 and 7.6.04. When you open the 
user tool\AIE Console and go to the data exchanges, there is an additional menu 
at the top that says AIE, click on it and you will see "export configuration". 
That'll give you a menu to export to another server or to arx files. I chose to 
export the exchanges directly to the server. The good thing about this is that 
it will automatically put them in the existing new Instance that was created in 
the install process. 

Jesus Ortega
Senior II, Implementation Engineer 
LyondellBasell Industries
Office: 713 309-4914
Cell:    281 546-0735

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain
Sent: Friday, March 29, 2013 4:21 AM
To: arslist@ARSLIST.ORG
Subject: Re: AIE Configuration after upgrade to ITSM 7.6.04

If you don't have too many AIE jobs you could try:
- in the user tool search for the EIE:BackupLoadFlag form
- export the records to an arx file
- edit the arx file to change the old server details to the new one (including 
the ARS port number if that was changed)
- import the modified arx replacing the existing records
- open each of the AIE jobs and select a new instance
- bounce the AIE service

If that doesn't work try turning on AIE logging in one of the exchanges and 
checking the log files.

Also, check that the AIE config file holds correct details for the new 
installation.

Cheers

Peter

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Maxence Nhouyvanisvong
Sent: 29 March 2013 08:43
To: arslist@ARSLIST.ORG
Subject: AIE Configuration after upgrade to ITSM 7.6.04

Hi All,

Hoping someone already faced the issue we have with AIE. We applied the BMC 
method to upgrade from ITSM/CMDB 7.6.00 to 7.6.04 sp4 (BPCU, new OOTB 
installation 7.6.04 on new Linux servers and new database, database dump to 
overwrite the OOTB database freshly installed, then DDM).
Now all AIE jobs are pointing to non-existing instances.
It is not possible to modify the AIE jobs anymore.
Not possible to modify the OOTB AIE created process using aiecfedit.
The OOTB AIE processes cannot be started.
We don't know how to uninstall only AIE without uninstall CMDB.

Anyone has an idea?

Thanks a lot for your help.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers 
Are, and have been for 20 years"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers 
Are, and have been for 20 years"




Information contained in this email is subject to the disclaimer found by 
clicking on the following link: http://www.lyondellbasell.com/Footer/Disclaimer/


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to