Search BMC.com
Search

1 2 3 Previous Next

BMC Atrium

65 Posts
Share: |


>> Atrium Webinar Series 

Dear Users,


We would like to take this opportunity to thank everyone who participated in our Atrium Webinar- Understanding CMDB Drift Management Webinar on April 10th, 2014


For people who missed this event or if you would like to go through the recording, watch the video below.



If you get any additional questions on Drift Management, then we suggest to create new discussion on BMC Atrium Community group.


Please add comment for any suggestions or feedback on this webinar session, we welcome all your feedback

Share: |


Problem Statement:

AtriumCore 8.1 to 8.1 SP1 upgrade fails if the base stack has AR 8.1 Patch 1 or Patch 2 applied along with the Atrium Core Hot-fix as described in “Applying the Data Management hotfix” section of the ITSM Patch documentation "Patch2 for version 8.1.00: 8.1.00.001(and002)". This blog explains pre-upgrade steps to avoid the failure during AtriumCore 8.1 SP1 upgrade installation.

 

The Data Management hotfix adds two Fields on PCT:LoadProdModelVersion namely CompanyID (ID: 536870914) and CompanyInstanceID (ID: 536870913). In AtriumCore 8.1 SP1, upgrade installer corrects Field IDs of these fields to 420000166 and 420000179 respectively.

 

While upgrading from AtriumCore 8.1, in an environment where Data Management hotfix is applied, the 8.1 SP1 upgrade installation fails with following errors which you will see in the AtriumCore installation logs.

 

(Feb 25 2014 03:29:06.939 AM -0800),SEVERE,com.bmc.install.product.atriumfoundation.dsl.DSLRuleEngineInstallerExecutorTask,
  THROWABLE EVENT {Description=[Failed to execute Rule Engine 2],Detail=[[ERROR][Tue Feb 25 03:26:39.936] ImportFileNode- ARImport() for "pct_deplapp.def" returned non-zero return code 2
[ERROR][Tue Feb 25 03:26:39.936] ImportFileNode- 314 Field does not exist on current form PCT:ProductVersionJoin : <420000165>
[ERROR][Tue Feb 25 03:26:39.936] ImportFileNode- 392 Field/VUI name must be unique for the form -- there is already a field or VUI using this name CompanyID
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:Product Cost LookUp
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:ProductVersionPatchKey
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:ProductVersionPatchJoin
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:ProductAliasModVerLookUp
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:Product M-V Uti Com LookUp
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:ProductVersionJoin
[WARNING][Tue Feb 25 03:26:39.937] ImportFileNode- 55 The following item was not imported PCT:ProductAliasCPYAssocLookUp
[WARNING][Tue Feb 25 03:26:39.966] ImportFileNode- 55 The following item was not imported PCT:VersionStatusFlagsJoin








The installation fails due to the Field IDs clashing in AtriumCore 8.1 SP1. You can use following simple steps to avoid 8.1 SP1 upgrade failure.


In case you do not have Data Management Hot-fix then you may ignore these steps. You can directly proceed with 8.1 SP1 upgrade.


Solution:


From your ARSystem install directory, run the archgid to change the Field ID of following fields.


Form: PCT:LoadProdModelVersion field ID: 536870914 to 420000166

Form: PCT:LoadProdModelVersion field ID: 536870913 to 420000179

 

"archgid" program lets you change the internal ID of a form, field, VUI, or group within the AR System. 


The following is a sample command which you can use to change the field IDs. You will need to replace input values of –u, -p and –x.


archgid -c 2 -i 420000166 -s "PCT:LoadProdModelVersion" -f 536870914 -u "Demo" -p "" -x "cmdbqa.labs.bmc.com"
archgid -c 2 -i 420000179 -s "PCT:LoadProdModelVersion" -f 536870913 -u "Demo" -p "" -x "cmdbqa.labs.bmc.com"


-u    The name of an Admin user

-p    Password for the user specified

-a    Authentication string for the user specified.  For Windows where the NT domain is needed for login, this is the domain name.  Generally, this option is not needed.  If this value is omitted from the ommand line, a backup prompt is issued only if the user name is also prompted for.

-x    Name of the server the Field/Form is on

-t   TCP port, that the Server is used for communication.  This setting is not needed if the server is registered with port-mapper.  If this value is omitted from the command line, a backup prompt is issued only if the server name is also prompted for.


What if I have already run Atrium Core 8.1 SP1 and installation failed due to above reason?


In case you have already run installer of 8.1 SP1 and have encountered the installation failure with the same error mentioned above in log file snippet, then along with above steps you will need following extra clean-up steps to be carried out.


1) When installer fails for some reason, it creates an entry in SHARE:Application_Properties form with Property Name = “state” and Property value = “failed”. Search for such entry and delete it from SHARE:Application_Properties form.

 

2) Edit the AtriumCoreInstalledConfig.xml  from AtriumCore Install directory and remove the failed feature(s) from the FAILED section:


<name>FAILED_INSTALL_FEATURES</name>

Change <value>feature*</value>  to <value></value>


Delete the copies of this file from the %TEMP% folders. This is the same location where atriumcore_install_log.txt would be found.

You can re-run the AtriumCore 8.1 SP1 installer once you have successfully completed above clean-up steps.

Share: |


>> Atrium Webinar Series 

Dear Users,

We would like to take this opportunity to thank everyone who participated in our Atrium Webinar- Understanding SSO in a Clustered Environment Webinar on March 13th, 2014


For people who missed this event or if you would like to go through the recording, watch the video below.


 

Additionally, you can find presentation from this webinar session in an attachment or on this online document. 

 

If you get any additional questions while using SSO in clustered environment, then we suggest to create new discussion on BMC Atrium Community group.


Please add comment for any suggestions or feedback on this webinar session, we welcome all your feedback


Share: |


>> Atrium Webinar Series 

Dear Users,

We would like to take this opportunity to thank everyone who participated in our Atrium Webinar- Best Practices for Designing Atrium Integrator Jobs in Spoon Webinar on February 12th, 2014


For people who missed this event or if you would like to go through the recording, watch the video below.



If you get any additional questions while Designing Atrium Integrator Jobs in Spoon, then we suggest to create new discussion on BMC Atrium Community group.


Please add comment for any suggestions or feedback on this webinar session, we welcome all your feedback


Share: |


During testing of the latest updates available from Red Hat we noticed a change in behaviour that may have RHEL users scratching their heads (and not necessarily only ADDM users).

 

In 6.5, Red Hat have included numerous bug fixes in the coreutils package (8.4-31.el6) affecting the way the 'su' command handles session return values and exit status handling.

 

When running the ADDM upgrade processes, the process starts and stops various services. We noticed that after updating the OS packages the upgrade itself would be terminated when a service was stopped. Odd. The 3rd party service itself isn't a true service but rather a script that uses the services functions to manage starting and stopping of a daemon-like program - a legitimate use case.

The upgrade was starting the service which in turn ran a program as another user with the 'su' command. When a service stop was called the service script would use kill to stop the called program (who's parent session is now the upgrade's after the service start script run finished). The exit status would then trickle back to the upgrade process and terminate that too. Surprise!

This is an artefact of the Red Hat changes and the differences between 'su' and 'su -'. You'll find 'su username -c command' (no minus) executes a command as username but with (most of) the current environment while 'su - username -c command' (with minus) executes a command as a username but, according to the man page, "make the shell a login shell" - essentially a whole new session. Previously if you used 'su' (no minus) you could safely kill the sub-process but now, be warned, 'su -' is your friend.

We raised this with Red Hat because, in my opinion, the bug has been around long enough that fixing it is more like a change in behaviour. RH responded with the fact the new behaviour is expected but will raise a knowledge base article to add extra visibility. Details on the specific bug fixes can be found the RHEL 6.5 Technical Notes.

Share: |


>> Atrium Webinar Series 


Dear Users,

We would like to take this opportunity to thank everyone who participated in our ‘Atrium Webinar- How to unlock the potential of Common Data Model in BMC Atrium CMDB’ Webinar on October 10, 2013.


For people who missed this event or if you would like to go through the recording, watch the video below, presented by Daniel Hudsky

 

 

If you get any additional questions on Common Data Model, then we suggest to create new discussion on BMC Atrium Community group.


We look forward to meet to you all soon



Share: |


My favorite new feature of the Normalizaiton Engine in 8.x version of AtriumCore is the Custom one.

 

I was very excited when I first saw that added because it allows for normalization of attribute fields. Some of the actions have a lot to offer when it comes to data enrichment, transformation and normalization.

 

You have functions like Concat, lower/UPPER, REPLACE, Substring, Truncate, Major (version). All of these can really help with automated data processing.

 

Anyone I've talked to about this feature raves about it . I personally use it every chance I get and it is a definetely one of the best new features of the AtriumCore. If you've not noticed it yet then please check out the Normalization Console - Normalization Features panel. I think you'll be amazed with this addition to the Normalization Engine.

 

Daniel

Share: |



I ran into this recently and although this was not a BMC Software product issue, it directly impacted the way our products communicate.
I would not have thought to check these registry settings in Windows, but the workaround is simple enough.

 

CMDB sync fails when firewall closes the connection KA400749. See link for details:

 

Be sure to subscribe to the BMC Atrium CMDB > Discussion community forums.

(Login Required:  https://kb.bmc.com/infocenter/index?page=content&id=KA400749)


Daniel

Share: |


NOTE:  2012-03-04:  This has been reposted under the BMC Remedy forum where I will maintain my future DM blog entries.

 

The latest Remedy 8.0 release includes significant improvements to the Data Management features allowing imports of data from spreadsheets, LDAP-enabled directories and databases. These features can reduce the manual input of numerous records throughout the system and ease the process of creating/updating many types of records and on-boarding new system users, support groups, etc.

 

A system administrator must configure a location to which data management servers may write temporary files for their operation.  Because data management jobs may be processed by multiple servers in a single environment, the location must be shared by all DM servers in the environment. This setting is made in the Administrator Console > Application Administration Console > Custom Configuration
> Foundation > Advanced Options > System Configuration Settings - System Settings.

 

SysSettings.png

 

For Windows-based servers, the share is defined as a universal naming convention (UNC) compliant shared folder (e.g., \\server\sharedfolder\).  Note that the trailing slash is required, and you must create this share before testing the shared path.

 

For Linux/Unix-based servers, the location is a file system location (e.g., /opt/sharedfolder/). Note that the trailing slash is required.  Linux/Unix servers may share a common SAN (storage area network) LUN (technically, this is a logical unit number however, it is frequently used interchangeably with ‘virtual hard drive’ that a SAN provides to a client) which may be shared across multiple Linux/Unix servers as a mounted volume.

 

DMT_LoadFilePath.png

 

A user must be a member of the appropriate permissions group in order to access the Data Management (DM) features.

The two permission groups and a brief description of their capabilities are:

 

  • DMT Admin – Membership in this group grants full control over all DM features and access to all jobs regardless of tenant or company from which the job was initiated or impacted.
  • DMT User - Membership in this group grants full control over all DM features and access to all jobs for a particular tenant or company to which the user in a member.

 

Lastly, if you rename your midtier (e.g. from oldserver to myserver), you likely need to create a new entry (or update the existing one) in the UDM:RAppPassword form (e.g. http://myserver:8080/arsys/forms/myserver/UDM:RAppPassword ). 

  1. Click New Request.
  2. Set Server Name to myserver.  (I had to add an entry for TEN after installing as LOCALHOST.)
  3. Set RApp Password to <whateveryourpasswordis>.
  4. Click Save.

RAppPassword.png

Share: |


As the versions 7.5 and 7.6 of the AtriumCore have reached end of support stages we felt we had to cover all the angles someone might run into. It's only fair to do so.

 

Information was added to the User Group Communities. The update includes a webex recording on how to apply the certificates and many other steps that should help to resolve any known issues with the Tibco certificate updates or starting the Tibco AMX Administrator service.

 

Be sure to subscribe to the BMC Atrium CMDB > Discussion community forums.

(Login Required:  https://communities.bmc.com/communities/message/274608#274608)

 

Daniel

Share: |


WWRUG12 starts in a couple of hours in San Jose, CA.

 

We're all very excited (and finalizing presentations or logistics )

  • You're participating? Great, let's F2F!
  • You could not make it? Too bad. Don't worry, we'll keep you updated on Twitter. And next year, let's make sure you make it, to share and learn with the biggest Service Management Community meetup on the planet ... actually the Universe ;-)

WWRUG12_hotel.png

Fairmont San Jose, great location, and enjoyable weather!

 

 

To know more about the event, use wwrug12.com.

To see the #wwrug live feed and interact with other users, use the WWRUG group (that's where we'll blog about what happens during the event).

 

Wishing you a great week, Matt

Share: |


With the release of version 8.0, documentation is available at the BMC online documentation portal. Gone are the days of jumping from PDF to PDF and cross-references pointing to entire guides. Now your documentation is consolidated in a space for the entire BMC Atrium Core platform, with easy access to other important documentation spaces such as BMC Remedy Action Request System and BMC Service Request Management.

5 fun facts about our new online documentation

  1. We have organized a What's New page to describe the enhancements that have been made in BMC Atrium Core 8.0, with links to more information in the documentation. For example, you can see the important enhancements that make to the installation process easier here.
  2. You can easily search for content. Use the search box on the left to search within the documentation space. From the results, you can change the filters to narrow or expand your results. For example, find only content updated in the last month. Expand your results to all your favorite documentation spaces.
  3. We have organized an end-to-end process for implementing BMC Atrium Core, taking you from the steps needed to plan your CMDB, to making your data available in CMDB, through to normalizing and reconciling your data so it can be used by all of your IT Service Management applications.
  4. The end-to-end process is supported by a video that reinforces the key concepts and shows you how data moves into and through BMC Atrium CMDB.
  5. BMC Atrium Core documentation is now part of the end-to-end installation instructions and upgrade instructions for the entire BMC Remedy IT Service Management suite. We've consolidated information such as requirements and Oracle settings. And we provide a spreadsheet that you can use for planning your installation.

We want your feedback!

Have a question about the documentation? Can't find what you're looking for? Think you found an error? Click the Add comment link at the bottom of any documentation topic and let us know. You'll get an email notification when a BMC Information Developer replies, and when the topic is updated. 

Miss PDFs?

Within each documentation space, you can find a ready-made PDF of the entire documentation space. Or you can export any set of topics to form your own custom PDF.

Sounds great, how do I access the documentation?

Follow the links (above or below) to the documentation. To log in, use your Support user ID and password. The first time you access the BMC online documentation portal, you must agree to the usage terms (same as on the Electronic Product Download). One caveat is that your browser locale must be set to en-us.

The new 8.0 online documentation is available from these links:

Share: |


Synopsis

 

This question comes up so very often that although documented we've decided to create this Knowledge Module to answer all possible angles of this question.

 

Problem/Symptoms

For example you need to create an attribute called MyNewAttr in the BMC.CORE:BMC_Monitor and you want this attribute to be visible in the AST:Monitor Asset View. Some customers assume that you can do this using overlays. We need to explain the how and why-not's to full extend. Reasons behind this are slightly complex.

 

Applicable To

 

This KA is to answer questions related to the BMC Remedy ARS Server 7.6.04 feature of Overlays and how it relates the managing the classes and attributes of BMC.CORE.

 

Showme

For the full article see: KA380649 (Requires Support Login)

 

Want to see more AtriumCore KA content like this and solutions poisted by the BMC AtriumCore support?

We got them in the BMC Support Knowledge Base (Requires Support Login).

Share: |


Synopsis

How do I know that my install of AtriumCore Webservice went well?  What are the certificates about?

 

Problem/Symptom(s)

Just installed AtriumCore Webservices? Now what? How do I get to the WSDLs methods or the UDDI? Basically I need to validate my installation and get the URLs that include the WSDL links to various services of the AtriumCore.

 

Applicable to

This KA is great to troubleshoot interaction with the CMDB data through the Web Service gateway.

  • BMC Atrium Core Web Services 7.6.04, 8.0
  •  


    Show Me

    For the full article see: KA322377 (Requires Support Login)

     

    Want to see more AtriumCore KA content like this and solutions posted by the BMC AtriumCore support group? We got them in the BMC Support Knowledge Base (Requires Support Login).

    Share: |


    If you have just installed ARS and then added applications without fine-tuning the ARS queues and java plugins then you might be wondering why the ARS Server is performing poorly. The system must be properly fine tuned to alleviate queue over loads.

     


    Update: We've heavily modified the original KA and broke it down to multiple new KA's. Please visit the Knowledge Article set with your login.

    Want to see more AtriumCore KA content like this and solutions posted by the BMC AtriumCore support group? We got them in the BMC Support Knowledge Base (Requires Support Login).


    Filter Blog

    By date:
    By tag:
    It's amazing what I.T. was meant to be.