||Strategy for what's next in Service management||IBM &
||Using Accelerators to Take ITIL Best Practices from Plan to Real Service Delivery||Icaro (BP)||Laerte Sabino|
||How Pirean's SMBus Solution Enables Easy Migration to IBM Tivoli Service Request Manager with Zero Downtime and Minimal Risk||Pirean (BP)||Andy Bentley|
||How Intesa Sanpaolo Successfully Transformed Their Change and Configuration Management Processes Using CCMDB||Intesa Sanpaolo||Serio Rubinetti/
||Cisco's Approach and Key Learning on Fixed Assets Management||Cisco||Maryanne Flynn|
||(Birds of a Feather) Customer Experiences with IBM SmartCloud Control Desk||IBM||Rich Johnston|
Don't miss these IT Service Management events at IBM Pulse today (Tuesday, March 6). All events take place in Room 112.
The IBM Pulse conference will be livestreamed from Las Vegas starting at 8 am PT/11 am ET this morning and until Wednesday this week on ibm.com/pulse.
Today's LiveStream schedule (all times are PST: Pacific Standard Time):
08:00 a.m. - 09:30 a.m.
General Session with Scott Hebner, Robert LeBlanc & Danny Sabbah
10:00 a.m. - 11:00 a.m.
Cloud Keynote with Jamie Thomas, Marie Wieck & Erich Clementi
11:15 a.m. - 12:15 p.m.
Security Keynote with Steve Robinson & Brendan Hannigan
03:45 p.m. - 04:00 p.m.
Interview with Steve Mills, Todd Watson & Scott Laningham
04:10 p.m. - 04:30 p.m.
Champions Recognition with Steve Mills, Todd Watson & Scott Laningham
05:00 p.m. - 05:30 p.m.
Day Closing Show with Bob Picciano, Todd Watson & Scott Laningham
jmatlock 270000DVMH Tags:  srm report ccmdb birt tamit analytics control_desk cognos 8,458 Views
As you may be aware, there are some exciting changes in store for the next release of our IBM Service Management software to be called SmartCloud Control Desk. This product will be the next evolution of IBM Tivoli® Service Request Manager®, IBM Tivoli Change and Configuration Management Database, IBM Tivoli Asset Management for IT, and IBM Tivoli Service Manager Quick Install. If you're attending Pulse, you'll hear a lot more about the changes and you'll also hear more from IBM in the coming days.
For this blog post, we're asking for your help in understanding how your organization is implementing reporting and analytics in your IBM Tivoli® Service Request Manager®, IBM Tivoli Change and Configuration Management Database, and IBM Tivoli Asset Management for IT installed environments. Additionally, we're interested in knowing whether you would benefit from a Tivoli User Group that would be focused on report and analytics development.
So, enter your email address in the comments section of this blog if:
When debugging a problem or when looking to recycle a JVM, it is useful to know which users are logged onto the system and what JVM they are working on. If a JVM needs to be recycled, you could then notify the users on that JVM that they will get an interruption in service. Or when debugging a problem it is useful to know what a user was doing on a particular JVM that was experiencing difficulties. If you know when a problem occurred and what users were logged into the JVM at that time, it helps narrow the potential pool of users considerably. So how can you figure this out? Enter the MAXSESSION table.
The MAXSESSION table is used to track connected servers and users. Every active or inactive user and server on the system has an entry in the MAXSESSION table.
When a user logs in or an application server starts, an entry is made in the MAXSESSION table. The column ISSYSTEM column has a 1 if it is an instance of a server (JVM) that is connected and a 0 if it is a user that is connected.
When a user logs out, their entry is cleared from the MAXSESSION table.
For a user the lastactivity field is updated whenever they do any activity
in the system. Inactive users can be detected when the last activity timestamp
is not current.
When a user is closes a session abnormally (for example not using
the normal Sign Out button but by clicking the X button of an IE window ), that user's session is not deleted from MAXSESSION until the
specified session timeout is reached.
The same is true if some type of error occurs that causes the session to end abnormally.
You can set the system property mxe.enableConcurrentCheck to 0 to prevent users from logging in more than once. If this property is set and the user closes the browser without logging out, they will not be able to log back in until the session timeout occurs or the system administrator logs them out.
When you understand the function of the MAXSESSION table, it is easy to create queries to pull out the data that you need to diagnose problems or understand who is working on the system.
alucches 2700012QJC Tags:  cognos data bilog analysis maximo birt v7 adhoc compare report ibmeam 5,172 Views
Pam Denny wrote an interesting blog post in the Asset Management blog about the Tivoli process automation engine 7.x reporting tools. Her post compares BIRT and Cognos for two of their reporting components, which are Operational and Ad Hoc Reporting. For more information, see her post.
the following Demo demonstrates how the user can perform TWA workload administration in a multi-engine environment from the Dynamic Workload Console, which provides a centralized access point.
Please review it and provide us any comment on that!
On January 30, 2012, updates for both the
TWA Rome Development team are looking for customers and business partners who are interested in participating in a Beta program for the next release of Tivoli Workload Scheduler for Applications and TWA 8.6 FP1 and SPE Features.
The Beta program provides participants with the opportunity to get an early look at the next release and provide feedback directly to the Development team to influence the future direction of the product. It will start on February 2012 ending on May 2012.
Beta program participants will receive education on the new features by webcast or recorded talk, and will be able to download Beta code from a web site and install it in their own test environment.VMware images are also provided.
We understand that participants have primary duties to perform at their companies and many demands on their time, there is no minimum time commitment in order to participate in the Beta program.
Participant benefits of a successful Beta Program include:
The opportunity to influence this product release and future directions
The ability to validate product code and documentation to ensure compatibility
The opportunity to obtain support from Development during the Beta Program
Please contact firstname.lastname@example.org if you are interested in this Beta or if you have any questions. The two steps to register are to complete a form with background information and to agree to an online Beta license.
Self Tuning Memory Manager (STMM) is a feature introduced since DB2 9 to get you out of memory tuning hell. It allows DB2 instances to adjust all database shared memory (buffer pools, sort heap, lock list, package cache, catalog cache, etc) to improve the overall performance. By default, STMM is turned on. Overall, STMM works great for IBM Tivoli service management products.
As Rick mentioned, statement concentrator could be a huge performance booster for IBM Tivoli service management products, so we generally recommend its usage for Maximo. However, during our performance benchmark, we did find a few interesting things about STMM, when statement concentrator is turned on. The following chart shows the overall system page hit rate (throughput) under different workload (number of users). In this benchmark, we gradually added users into the system to observe its performance. Interestingly, when STMM is turned on for all shared memory area, the system's performance started to degrade when approaching near 3000 users and then kept getting worse with more users added:
One symptom we could observe was that STMM kept increasing the size of the package cache, which reached 2GB at the end of 4000-user stage. DB2 statement concentrator enables queries that are identical except for the values of literals to share the same access plan. In addition to the "shared" plan, it also put a small "stub" entry for each original query (with literals) in the package cache. When these large number of small "stub" entries fill up the package cache, it trigger STMM to increase the size of the package cache, which then quickly got filled up again and enlarged again and again ... Eventually, DB2 spent majority of its time in just managing this extra large package cache which caused the performance degradation.
To resolve this problem, we turned off STMM for package cache (only) and use a smaller, fixed size for it (pckcachesz). We have observed near 50% CPU decrease on DB2 with 25% improvement in overall response time.
Note that DB2 9.7 FP5 includes a fix to address this problem. With FP5, when both statement concentrator and STMM for package cache is turned on, the package cache size is always under 100MB for our benchmark.
LeandroCassa 270002840B Tags:  external tpae process srm useful ccmdb system tiny restapi things rest restful integration tivoli engine little automation 3 Comments 13,662 Views
The XML output is similar to the integration framework format. And it is possible to extend the existing serializers to generate different outputs.
The URL above returns the list of person records on the target system.
Where 1 is the PERSONUID. If referring to a CI object, it would be CIID and not the CINUM; this is actually the unique ID of the table that represents the object.
The displayname and status are the fields to filter by. the operator ~eq~ stands for equal. MAXADMIN is the person I'm looking for and I'm also filtering by ACTIVE users. Using the first URL in this post, you can identify all fields that you can use to filter by. There are many operators (like ~eq~) that can be found in the information center reference provided at the beginning of this post, this post is limited to the most basic operations possible through the REST API.
the following document describes how to preserve customized if you want to upgrade from Tivoli Workload Scheduler V8.4 to Tivoli Workload Scheduler V8.5.x .
Please review this file and post your question on IBM TWA Forum !
This is the pdf:
Note: This blog entry was originally created by Zach Zhang in the Asset Management Group. I wanted to share this info with the Process Automation Group too.
There's some intermediate resource required by Oracle database to execute sql statements. One among them is Oracle Temporary Table Space when pure-in-memory operations could not be performed due to resource limitation or specific execution plan.
Before we start to discuss how and when Maximo application will use temp in Oracle database, there's one thing worth mentioning: it's Oracle database to decide when and how to use the Temp segment, while any application code just want the query result.
Tivoli Workload Scheduler 8.5.1 Fixpack 3 and Tivoli Dynamic Workload Console 8.5.1 Fixpack 3 have been shipped at the end of December 2011 and can be downloaded from Fix Central.These fixpacks (TWS and TDWC) deliver 160 APARS plus internal defects to our customers.Notice that the IBM ID needs to be entitled to download them from fixcentral.
If a customer or IBMer is experiencing a problem with the entitlement, please refer to the following links:
- Page where IBM internal can be entitled:http://www-947.ibm.com/systems/support/fixes/en/fixcentral/help/index.html- Entitlement error and resolution for customers:http://www-947.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html#entitlement_error
The fixpacks can be found by accessing the Fix Central section of the Tivoli Workload Scheduler: http://www.ibm.com/support/fixcentralThis fixpack's main themes
"Most important New features:Enhancements to the file transfer job type"
- Support for transfer mode selection
- Support for local and remote code page (valid only for FTP servers running on z/OS systems)
- Support for remote custom codepages (valid only for FTP servers running on z/OS systems)
- Support for the FTP, FTPS, FTPES, WINDOWS, SSH, protocols
TWS Improvement on current behaviour:
Ambiguity for jobs scheduled when Daylight Saving Time switches off
"If a job stream or a job run on a timezone where the Daylight Saving Time
(DST) switches off, that is the clock is put one hour back, and if you define
a time dependency for such job streams or jobs in relation to another
timezone, it might happen that this time dependency occurs during the
second, repeated time interval. In this case the time dependency would be
resolved during the first time interval.
Now Tivoli Workload Scheduler recognizes that the time dependency
occurs on the second, repeated time interval and resolves it accordingly.
No user action is required to activate this behaviour"
TWS Every job is now Daylight Saving Time aware:
"If the EVERY keyword is defined for a job when the Daylight Saving Time
switches off, that is the clock is put one hour back, the job does not run
during the second, repeated time interval.
Now the command EVERY JOB is DST aware and it runs also during the
second, repeated time interval. No user action is required to activate this behaviour."
lucabuvoli 060000YHQW Tags:  jes z/os for scheduling on tws agent extended comparison migration 5,594 Views
Hi fellows, as anticipated a while back we added suggestions about migrating your job definitions to the TWS database should you decide to go from the extended agent for z/OS to the new distributed agent (for z/OS) available with TWS 8.6. Give it a read if you are interested in the subject, as it explains how to keep the procedural part of your JCLs on z/OS while moving only the job cards to the TWS database. You can find the document on the TWS WIKI (path Tivoli Workload Scheduler>