Hey, be glad you got them to come in at all.
Based upon the belated information from David "... and load everything you wish
to be present once the upgrade is complete."
...we moved the upgrade of Kinetic Request 4.0.03 to 5.0.1 (and theoretically
the import of the alarmpoint integration applications) to NOW instead of after
the ITSM 7.6.04 upgrade as we had planned - NOW being the point where we have
upgraded AR on the Staging Server to 7.6.04 (21 Feb) and run the BPCU in
-Prefix and Overlay modes (took from 22 Feb until 23 March to get that to work
correctly since Support was absolutely CLUELESS) and were just starting to
reconcile all of the overlays it created that it should not have.
Upgrading Kinetic Request involves manually deleting whole ranges of forms and
workflow, then re-importing them from .def files. When I try to import them in
Developer Studio 7.6.04 (Best Practice Customization Mode), not all of them
come in, and I get the error:
Base and overlay object must be the same type.; KS_ACC_Attachment, 8861,
ERROR (8861): Base and overlay object must be the same type.; KS_ACC_Attachment
at
com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
Source)
at com.bmc.arsys.api.ProxyJRpc.ARImport(Unknown Source)
at com.bmc.arsys.api.ARServerUser.importDefFromFile(Unknown
Source)
at com.bmc.arsys.api.ARServerUser.importDefFromFile(Unknown
Source)
at com.bmc.arsys.apiext.definition.DefinitionImport.if(Unknown
Source)
at
com.bmc.arsys.apiext.definition.DefinitionImport.importObjects(Unknown Source)
at
com.bmc.arsys.studio.ui.common.definition.DefinitionHelper$5.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
I get the same basic thing from an attempt to import in the Admin Tool
7.1.00.002 (yes, at this point I AM getting desperate to find some process that
actually works):
Base and overlay object must be the same type.: KS_ACC_Attachment (ARERR 8861)
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Form does not exist on server : Invalid object or object name for overlay mode
set (ARERR 303).
Those that DO import are marked Custom, but if the system is recognizing this
stuff as Custom, then overlays should not be involved at all!!
I'm getting very close to bailing out on 7.6.04 entirely at this point, after
losing a month to BPCU follies already.
Christopher Strauss, Ph.D.
Call Tracking Administration Manager
University of North Texas Computing & IT Center
http://itsm.unt.edu/
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Atul Vohra
Sent: Monday, March 28, 2011 11:41 AM
To: [email protected]
Subject: Re: Overlay and custom in 7.6.4
David:
"Once you do this, you'd really never want to run BPCU again. Any new objects
that you import into the server will become custom or overlaid objects. And
any upgrades of BMC products will only touch the origin (base) objects. " ---
I imported some forms from 7.6.3 system in to 7.6.4 system and they came in as
Unmodified. Am I missing something? They should have come in as 'custom'?
Regards
Atul Vohra
-----Original Message-----
From: "Easter, David" [[email protected]]
Date: 03/28/2011 12:30 PM
To: [email protected]
Subject: Re: Overlay and custom in 7.6.4
BPCU is intended to assist in the conversion during an upgrade process to
v7.6.04 (or later) - and thus intended to be used once in the overall upgrade
process. Simply put the process is (and I'm way oversimplifying this - follow
the real documentation for all the actual steps):
1. Take a pre-7.6.04 system and load everything you wish to be present once the
upgrade is complete.
2. Run BPCU to determine if there are any fields or objects that are "illegal"
and must be corrected prior to the upgrade.
3. Correct the illegal fields (or determine if they are in fact 'legal' and
note those to be bypassed by BPCU)
4. Upgrade to AR System 7.6.04
5. Run BPCU to convert the 7.0.03p9 or later applications to overlays and
custom objects
6. Reload the original BMC applications so that your origin (base) objects are
now BMC OOTB.
7. Upgrade your applications
Once you do this, you'd really never want to run BPCU again. Any new objects
that you import into the server will become custom or overlaid objects. And
any upgrades of BMC products will only touch the origin (base) objects.
-David J. Easter
Manager of Product Management, Remedy Platform
BMC Software, Inc.
The opinions, statements, and/or suggested courses of action expressed in this
E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary
participation in this forum is not intended to convey a role as a spokesperson,
liaison or public relations representative for BMC Software, Inc.
