SDU - User contributions [en]

Cohesion

2010-12-27T20:10:36Z

Trzaskowski:

'''Cohesion Application Configuration Manager 5.0 '''

Cohesion's integratration with CA CMDB v12 and above is supported by CA Support.

Cohesion can update the CMDB via a report given proper access to update the CMDB application. The report function creates an xml file that uploaded/inserted into the CMDB.
The system checks for duplicates by looking for like: system name, host name, dns name, serial number. There is also a shared MDR number between the configuration item in CMDB and the configuration item in Cohesion.
You can also export the xml file and update the CMDB manually via the command line using GRLOADER.

GRLOADER /? will give you available parameters.

typical update command is ''grloader -E -I -a -u username -p password -s http://host:8080 -i c:\filename.xml''

to insert add the -n parameter ''grloader -n -E -I -a -u username -p password -s http://host:8080 -i c:\filename.xml''

CA recommends no more than 500 servers per instance of Cohesion, any more then you have to add secondary servers

'''TroubleShooting Cohesion integration with CMDB'''

In running CMDB 12.1 with an externally hosted database we had many duplicate CI"s created when we tried to update the CMDB with XML from Cohesion, even though there should not have been. CA stated the MDR Registration process goes to sleep and sometimes does not reconnect properly. Killing the MDR_registration process on the server hosting the CMDB application before doing any imports seems to resolve this, as the MDR_registration process will restart automatically and make a solid connection to database to enable any imports.

'''SQL Tables'''

If you are interested in doing a query for which software is found which servers the two tables components_ui_table (software) and the cc_host table (servers)

The following query will give you results of software to server

use cohesion
select sw.mod_name, srv.host_name
from components_ui_table sw
left outer join cc_host srv
on
sw.host_id = srv.host_id
order by mod_name

Cohesion

2010-12-20T16:10:14Z

Trzaskowski: Cohesion's integratration with CA CMDB v12 and above is supported by CA Support.

Make a Field Conditionally Required

2010-06-04T16:26:16Z

Trzaskowski: /* Step 1. Create the script */

__NOTOC__
[[Category:Customizations]]
[[Category:r6]]
[[Category:r11]]
[[Category:Schema Change]]
{{Global Header}}
{{Global Announcement}}

== Overview ==
This article provides instructions for making a field conditionally required. The example that follows makes a field conditionally required when a ticket is being closed. However, the concept of this customization could be expanded to make a field required only if the condition has been fulfilled.

== Procedures ==
=== Step 1. Create the script ===
A script is created as an [[.spl file]] and placed in the [[$NX_ROOT]]/site/mods/majic directory. When the Service Desk service starts, the contents of the majic directory are processed and cached. You can use any naming scheme you like for your [[.spl file]], but it is recommended that the file be preceded with a 'z' for easy identification as a custom file (eg zMyCompany.spl, zcr_scripts.spl, zMyScripts.spl).

<source lang="javascript">// Use 'cr' for Requests, Incidents & Problems, 'chg' for Changes, and 'iss' for Issues
cr::zmyscript(...) {
string zmsg;
// Enter an if statement, the string1 value should be replaced with the field you want required, for example "impact" for a change order
if(is_null(string1)) {
// Enter an alert message that appears when the if statement is fulfilled
zmsg=format(" string1 is required in order to close this ticket");
set_error(1);
set_return_data(zmsg);
return;
}
}</source>

=== Step 2. Create the trigger ===
This step is to create the trigger that will initiate the script. The methods used to implement the trigger vary based on the Service Desk release.

''For r11.x releases'' triggers are created via the [[Schema Designer]] utility. Simply add the following code as a [[Site-Defined Trigger]] to the '''[[Call Req Table|cr (Request)]]''', '''[[Change Request Table|chg (Change Order)]]''', or '''[[Issue Table|iss (Issue)]]''' table.
PRE_VALIDATE zmyscript() 111 FILTER(active==0);

''For older releases'' triggers are made by creating a [[.mod file]] and placing it in the [[$NX_ROOT]]/site/mods/majic directory. Name the [[.mod file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'.

<source lang="javascript">// Use OBJECT cr for Requests, Incidents & Problems
// Use OBJECT chg for Change Orders
// Use OBJECT iss for Issues
OBJECT cr {
TRIGGERS {
PRE_VALIDATE zmyscript() 111 FILTER(active==0);
};
};</source>

=== Step 3. Publish the Schema changes ===
The methods used to publish schema changes vary based on the Service Desk release.

''For r11.x releases'', follow these steps:
#Save your Schema changes
#Stop the Service Desk service
#Run [[pdm_publish]] from a command line
#Start the Service Desk service

''For older release'' recycle the Service Desk service.

Attachments on Configuration Items

2010-05-04T17:33:38Z

Trzaskowski:

__NOTOC__
[[Category:Configuration Items]]
[[Category:Customizations]]
[[Category:r11]]
[[Category:r12]]
{{Global Header}}
{{Global Announcement}}

== Overview ==
This article provides instructions for adding attachment capabilities to Configuration Items.

''Note: This customization is designed for r11.x and r12.1 versions only.''

== Procedures ==
=== Step 1. Modify Schema ===
For ALL releases make your schema change by creating a [[.mod file]] and placing it in the [[$NX_ROOT]]/site/mods/majic directory. Name the [[.mod file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'. Take the code you need from the examples below.
<source lang="text">LREL attmnt_lrel "nr:PDM" attachments <> attmnt assets;</source>

=== Step 2. Publish the Schema changes ===
For ALL releases recycle the Service Desk service.

=== Step 3. Edit the detail_nr.htmpl form ===
Add the following code to the BODY of the form in the PDM_NOTEBOOK area (for R12 this modification can be made to cmdbNotebook.htmpl):
''additional extension forms will need to be modified appropriately detail_har_virx.htmpl, detail_har_serx.htmpl,''

<source lang="html4strict"><PDM_TAB ID=attmnt SRC="OP=SHOW_DETAIL+HTMPL=xx_attmnt_tab.htmpl+FACTORY=nr+PERSID=$args.persistent_id" NAME="Attachments" height=300></pdm_tab></source>

=== Step 4. Edit the xx_attmnt_tab.htmpl form ===
This step will add "Edit" and "Delete" right-click options if the Inventory Functional Access is granted on the user's Access Type. If this scripting is not added then you will only have the option to view a document.
Search for the following scripting:<source lang="javascript">switch ("$prop.factory") {
case "cr": attmntAccess = "${ACCESS.call_mgr:0}" - 0; break;
case "iss": attmntAccess = "${ACCESS.issue_mgr:0}" - 0; break;
case "chg": attmntAccess = "${ACCESS.change_mgr:0}" - 0; break;
}</source>... and add the following case:<source lang="javascript">
case "nr": attmntAccess = "${ACCESS.inventory:0}" - 0; break;</source>

=== Step 5. Clear the web cache ===
Publish your changes via the [[Web Screen Painter]]. The process of publishing automatically initiates a [[pdm_webcache]].

== NOTICE ==
Be advised that implementing this customization will result in a few ERRORS in the stdlogs, but there has been no reported degradation in functionality.
<source lang="text">kt_daemon 16316 ERROR DomWrap.c 1106 cSelect: failed In method select_sd_ref_num. Error Message: Error 103 AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id
kt_daemon 16316 ERROR DomWrap.c 806 Failed to complete reply method: 'select_sd_ref_num' ,BOP Name:'attmnt:400063' in class:'CAttmntLinks', Error:AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id
domsrvr 13132 ERROR attr.c 6164 Error in ATTR_INIT trigger get_attached_name for attached_name: AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id</source>

Attachments on Configuration Items

2010-05-04T17:31:49Z

Trzaskowski: /* Step 3. Edit the detail_nr.htmpl form */

__NOTOC__
[[Category:Configuration Items]]
[[Category:Customizations]]
[[Category:r11]]
{{Global Header}}
{{Global Announcement}}

== Overview ==
This article provides instructions for adding attachment capabilities to Configuration Items.

''Note: This customization is designed for r11.x versions only.''

== Procedures ==
=== Step 1. Modify Schema ===
For ALL releases make your schema change by creating a [[.mod file]] and placing it in the [[$NX_ROOT]]/site/mods/majic directory. Name the [[.mod file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'. Take the code you need from the examples below.
<source lang="text">LREL attmnt_lrel "nr:PDM" attachments <> attmnt assets;</source>

=== Step 2. Publish the Schema changes ===
For ALL releases recycle the Service Desk service.

=== Step 3. Edit the detail_nr.htmpl form ===
Add the following code to the BODY of the form in the PDM_NOTEBOOK area (for R12 this modification can be made to cmdbNotebook.htmpl):
''additional extension forms will need to be modified appropriately detail_har_virx.htmpl, detail_har_serx.htmpl,''

<source lang="html4strict"><PDM_TAB ID=attmnt SRC="OP=SHOW_DETAIL+HTMPL=xx_attmnt_tab.htmpl+FACTORY=nr+PERSID=$args.persistent_id" NAME="Attachments" height=300></pdm_tab></source>

=== Step 4. Edit the xx_attmnt_tab.htmpl form ===
This step will add "Edit" and "Delete" right-click options if the Inventory Functional Access is granted on the user's Access Type. If this scripting is not added then you will only have the option to view a document.
Search for the following scripting:<source lang="javascript">switch ("$prop.factory") {
case "cr": attmntAccess = "${ACCESS.call_mgr:0}" - 0; break;
case "iss": attmntAccess = "${ACCESS.issue_mgr:0}" - 0; break;
case "chg": attmntAccess = "${ACCESS.change_mgr:0}" - 0; break;
}</source>... and add the following case:<source lang="javascript">
case "nr": attmntAccess = "${ACCESS.inventory:0}" - 0; break;</source>

=== Step 5. Clear the web cache ===
Publish your changes via the [[Web Screen Painter]]. The process of publishing automatically initiates a [[pdm_webcache]].

== NOTICE ==
Be advised that implementing this customization will result in a few ERRORS in the stdlogs, but there has been no reported degradation in functionality.
<source lang="text">kt_daemon 16316 ERROR DomWrap.c 1106 cSelect: failed In method select_sd_ref_num. Error Message: Error 103 AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id
kt_daemon 16316 ERROR DomWrap.c 806 Failed to complete reply method: 'select_sd_ref_num' ,BOP Name:'attmnt:400063' in class:'CAttmntLinks', Error:AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id
domsrvr 13132 ERROR attr.c 6164 Error in ATTR_INIT trigger get_attached_name for attached_name: AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id</source>

Change Order Schedule

2009-11-17T15:32:55Z

Trzaskowski: Customization of the CHange Order Schedule Version 12.1

Customization of the Change Order Schedule Version 12.1

== The Change Order Schedule Calendar can be customized via the list_chgsched_config.htmpl in the web screen painter. ==

By Default the Change Order Schedule Calendar starts on Friday. CA does this as they claim most changes are on the weekends, and they are then more easily viewed.

This can be changed to start to a different day to display the Start of the week in the Calendar, via the area in '''BOLD''' below THe following example has the first day as Sunday

Change Order Schedule Configuration

The following lines can be modified to change the appearance and contents
of the change order schedule calendar views.

The schedConfig macro is required to define a schedule form and specify
overall options. Arguments are:
autoSearch - Automatically reissue search when required (1=yes; 0=no)
defaultView - Initial view: 1=day; 7=week; 30=month; 99=nday; 0=list
export - iCalendar export template code (0=no export)
'''firstday - The first weekday from 0 (Sunday) to 6 (Saturday)'''
legend - Position of legend (1=top, 2=bottom, 0=none)
maxgroups - Maximum number of groups per cell in month view
ndays - Contents of n-days dropdown (0=none)
round - Event time rounding as (hr,min) (0=no rounding)
timefmt - Time format as 24hr or ([am],[pm])

</PDM_IF>

<PDM_MACRO NAME=schedConfig
autoSearch=1
defaultView=30
export=ChangeSchedule
'''firstday=0'''
legend=2
maxgroups=4
ndays=(3,7,14,28)
round=(0,15)
timefmt=24hr>
<PDM_IF 0>