The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
X
Bridging the gap between clients and IBM TRIRIGA SupportI am new to the IBM TRIRIGA Support organization, working as a Level 2 Support Engineer. It has been my observation when reviewing PMR's that there is a lot of time spent going back and forth between the customer and the support engineer. It seems to me that this is due, in part, because not enough information was initially provided. Many times I have seen, in a PMR, that the customer is getting some error. Sometimes they just say they are getting an error or they may report the specific error with no information about how it happened, what version they were using or what they were doing. Many times there are vague steps with our client thinking that TRIRIGA engineers should know what they are trying to do.
I wanted to share what happens in support so that clients might understand why information about a problem is so important. When support receives a PMR we try to reproduce the issue based on the information given to us. If we are not given enough information, we are forced to collect it by making requests that can take days or even weeks to accomplish. Time zones play a role where each email can take a full day to get to the right people and get a response. In some cases, if we are provided with not enough information we may fail to replicate the problem which does not mean it is not an issue, it just means we may have replicated incorrectly because we are missing information or there are configurations or customized workflows that we do not have. There could be something in the way that the customer is doing something versus how the support engineer is doing something, because with software, there can be more than one way of doing something. If we need to get additional information it just takes that much more time.
We recognize that your time is valuable and it can be frustrating going back and forth to get the necessary information to reproduce an issue. What would help us in IBM TRIRIGA Support, is when entering a PMR, clients provide detailed step by step instructions as if you were asking your non tech-savy grandmother to reproduce. It may sound corny but it really is all in the details. As I mentioned, there could be more than one way to do something and left to our own devices, we might not do it the same way as you (the customer), so the more details the better.
If you have ever cooked and followed a recipe you are following steps. You might think of that approach for entering your steps to reproduce an issue.
For example:
etc
Your time is valuable and we recognize that. The more detailed you are with your initial entry on the PMR, the less time spent going back and forth trying to get the steps and more time can be spent on reproducing and resolving your issue.
Remember, we do have a document we often call a “Must Gather” or “Information To Collect” document for TRIRIGA PMRs. You should always submit this when you open a PMR. You can generally fill it out and save it so you always have it handy to attach to PMRs, just remember to update it when something changes. See it here: http |
|||||||||||||||||||||
IBM IoT will soon Launch the new IBM Support Community for its offerings
You can find a list of common FAQs for your offerings in the following technotes:
We hope you enjoy the enhancements of this new IBM support experience and welcome your feedback. |
|||||||||||||||||||||
Changes made in TRIRIGA as a result of Security Vulnerabilities
In this day in age, security is a very hot topic and as soon as one vulnerability pops up, it is addressed and mitigated, another one is found. It is a vicious circle of identifying and addressing that does not seem to let up. In our fixpack release notes, information regarding mitigation of vulnerabilities that were addressed without an APAR is listed. And sometimes, a vulnerability could be addressed as an APAR.
The reason I am mentioning security vulnerabilities is that sometimes, when they are resolved, there is an effect that impacts existing functionality and it may not always be clear. Sometimes, the result of fixing these vulnerabilities can “change” functionality. As an example, in the 3.5.2 release, there is mention of an APAR related to external URL navigation items will now open in a new window to avoid cross origin scripting vulnerabilities. Prior to the 3.5.2 release, if you used an external URL in the navigation, it just opened in the same window. We have seen some issues where clients wanted the original design, but that is no longer possible since the change was made as a result of fixing a security vulnerability. The current behavior is correct and cannot revert to the old design. So in this case, there was an APAR referenced. But in others, there may not be. You can look at the 3.5.2.1 release notes (found here http
As the product develops and security vulnerabilities are found and addressed, it could mean a change in how something works. Reading the release notes can be a source of information but it may not always be clear why something changed. We all know change is hard, especially when we are so used to it working a certain way. I don’t know about you, but if the change was made to address a security vulnerability, I can live with that and accept the change.
|
|||||||||||||||||||||
TRIRIGA and the WAS Liberty Profile that does not want to be a serviceWell, you get TRIRIGA 3.4.2 or later to install and see how cool to use the Liberty Profile for WebSphere Application Server (WAS). This lets you install both the web server and TRIRIGA at one strike and self deploys itself from TRIRIGA installer. What an easy deal!
After installing TRIRIGA and the WAS Liberty profile, the user logged into the service and running it cannot log out or the service will be stopped. Many businesses do not allow an Admin user to be logged in indefinitely.
Now you're thinking you have to install all over again in a WAS deployed first. You double check and see WAS Liberty cannot run as a service as a product limitation. What a drag...
Well, there is one workaround you can try. Using the Apache's daemon you can create a Windows service. The following instructions are an idea for how you can implement it, but it depends on your architecture and installation:
Note: If you run into any issues, check the logs in the LogPath directory location for any errors - the errors as listed in the event viewer logs from Windows do not give meaningful errors.
References: There is an RFE to implement this and I encourage you to vote for it: http
developerWorks Forum: http
|
|||||||||||||||||||||
New Feature in the IBM Support Community
Are you new to the IBM Support Community and managing your support cases opened with IBM? Would you like to have the ability to see case updates in your email from support?
A new feature was recently implemented that will allow you to see your case updates directly in your email. You no longer have to log into the community to see your case updates. To do this go to "My Settings" (located in the upper right hand corner of the community) and under Case Notification Settings select the following:
See Case Email Notifications for further details. |
|||||||||||||||||||||
IBM Watson IoT Support Lifecycle ResourcesIBM Watson IoT Support Lifecycle ResourcesResources ____ End of Support (EOS) Announcements IBM provides advance notification of End of Support (EOS) dates allowing customers reasonable time to complete software upgrades or to refresh application products. EOS announcements are made in April and Sept.
Announcement letter dates are U.S. only. Information for other country announcements is available on the IBM Offering Information page. Select the date to view the announcement letter. Note that some product versions may not have online announcement letters.
View all IBM Software EOS announcements for 2016 and 2017. IBM Software End of Support (EOS) ____
This section describes some of the standard and enhanced IBM Software Support Lifecycle Policies and common questions. Additional details and answers to commonly asked questions regarding the Support Lifecycle Policy can be found on our Frequently Asked Questions page.
Q: What are the major Support Lifecycle milestones? A: The major Support Lifecycle milestones are:
Q: How do you determine if your installed software is still supported? A: Search by product name or keyword using the Supp
Q: What happens when EOS is announced? A: Often, there is a newer version of the software available for download. In most cases, you’ll have sufficient time to plan for and install the latest version. For more information on the lifecycle stages, including EOS, view this short YouTube video on the IBM
Q: What is the standard version format for IBM Software products? A: The full product version is expressed by a four-digit code known as the IBM Version, Release, Modification and Fix Level structure, or VRMF. View this Technote for additional information and description of each element. You may also find this Glossary of product support and maintenance terms helpful.
Q: How can you connect with Watson IoT on social media? A: You can follow us on Twitter - http
Q: Where can you find more information on IBM Support policies? A: You can view and download the IBM
____
For more information on IBM software support topics, check out the following resources:
____ |
|||||||||||||||||||||
IBM TRIRIGA - What are the differences between Fixpacks and Limited Availability Fixes and what are best practices for fixes?
Occasionally we have IBM TRIRIGA customers who need clarification on the differences between Fixpacks and Limited Availability fixes. I want to share this information with you and state best practice guidelines here:
GENERAL AVAILABILITY FIXPACK (GA FIX) GA Fixpacks deliver product defect fixes that have undergone a full development release cycle and the most extensive QA testing of all maintenance releases. These fixes are delivered for any issue reported either internally or externally regardless of severity. Fixpacks occasionally deliver minor functional enhancements and modifications to add or update supported platforms, browsers, databases, middleware, etc. Fixpacks are cumulative and each new fixpack contains all fixes from all previous fixpacks/interim fixes for that release.
LIMITED AVAILABILITY FIX (LA FIX) An LA Fix is an unofficial mechanism to deliver emergency fixes for severe product issues that cannot be delayed until the next regular maintenance delivery. LA Fixes also go by the names “1-off” or “1-off Hotfix” but they all mean a single APAR fix delivered directly to a customer from Support.
Conditions that may warrant an LA Fix
Risks associated with LA Fixes
BEST PRACTICES FOR FIXES It is perfectly acceptable to take an LA FIX to address an issue when warranted. However, the risk associated with taking an LA FIX should always be weighed against the perceived benefits. If at all possible, it is always best to wait for a fully tested GA Fix. Also, if you do take an LA Fix, it should only remain in place until a GA Fix containing the fix needed is available. At that point, the GA Fix should be applied.
|
|||||||||||||||||||||
Restart IBM TRIRIGA on WebSphere Liberty Profile on Microsoft Windows OS
If you have a need to restart Tririga on WAS Liberty Profile in Windows you must first find your tririga_root install path. If you used the default for the installer, this should be C:\IBM\Tririga. If you are not sure of the location, you can search for the following files (these should be in the Tririga \bin directory.): "run.bat" and "shutdown.bat"
STOP TRIRIGA: To stop Tririga, navigate to the trir Alternatively, on Windows servers, you can open a command prompt and run the command to shut down the Liberty profile: trir
START TRIRIGA: To start Tririga back up, navigate to the trir Alternatively, on Windows servers, you can open a command prompt and run the command to start the Liberty profile. trir
If you need further assistance please contact IBM Tririga support. |
|||||||||||||||||||||
Understanding TRIRIGA PerformanceWe sometimes hear in support, that TRIRIGA performance is slow. No other details are given. That doesn't help us out a lot. We need to know more, like what was going on at the time that? Is it impacting the entire system or just one area?
Performance of TRIRIGA is a bit complex. and there is rarely any one thing that can be done to improve performance. Performance can be impacted by hardware, network connectivity, software versions, queries, indexes, customizations, configurations and more. The answer to performance concerns is often solving some combination of these things. But some things can be reviewed to help point you into a direction where to look and what to do.
Some things like hardware and network connectivity are out of our control and need to be reviewed by your own IT department or a business partner to perform a health check or performance analysis on your system. We do provide a list of minimum hardware requirements that TRIRIGA should be running on in our installation guides. We also have a compatibility matrix to show you what configurations are supported for your particular version here: http
To help diagnose the problem, TRIRIGA has performance logs that can be enabled, retrieved and analyzed. There is a wiki page that describes the process of enabling the performance log files as well as analyzing them, which can be found here: The wiki will walk you through how to enable the performance log and then analyze the output.
In case of performance concerns, TRIRIGA Administrators should ALWAYS review best practices to ensure they are following recommendations before entering a PMR. The wiki regarding Performance can be found here: http
Once you have the performance log, you can create the following pivot table to help identify where something is taking too long.
Generally, if something is taking longer than 10 milliseconds then it is taking too long to. For instance, in this example, you can look at the query for the report and see if it is optimized correctly. You may need to look at your database to see if anything needs to be adjusted at the database level.
It should be noted, that if you are using multiple servers in your environment, you would need to access the console from the server that is having the problem. If you have 3 UI JVM's and 2 process servers, where one of them is the workflow agent and you know you are having issues with workflow performance, then you would access the console from the server that has the WF agent running.
So using the performance log can help you identify what could be taking so long and if you enter a PMR that is something that can help us out as well. It is important to remember, that TRIRIGA Support is committed to every clients success, however; performance is not typically covered as part of the support agreement. Our goal will be to help point you in the right direction but since most performance inhibitors are unrelated to TRIRIGA, the support team cannot commit to resolving performance related issues. We may advise you but the resolutions are often up to you.
|
|||||||||||||||||||||
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next GenerationAre you considering migrating your data from Rational DOORS to Rational DOORS Next Generation(RDNG)? Are you looking for guidance and best practice before you begin to be successful first time?
If so, then your starting point is definitely the detailed guidance on developerWorks on how to Migr
New Sizing and Best Practice Guide on Jazz.net's Deployment wiki Since the developerWorks article was published, we realized that more detailed sizing information was required prior to executing the migration of data packages from DOORS 9 to RDNG. We collated pertinent sizing information from the Rati There are significant improvements to the import timings with RDNG 6.0.2 release, so please refer to this article if you are evaluating an existing or future migration as this could indeed be an influencing factor.
The document details: Sizing Guidelines for Rational DOORS Next Generation 6.x Recommendations on the maximum sizes of your modules, projects and repositories so as to maximize your success when importing your packages and working in the future within RDNG.
Hardware considerations The considerations for hardware are simplified from guidance published elsewhere in the Deployment wiki, but here they are explained within the context of how to plan for your new world.
Guidance on how to convert your Rational DOORS modules prior to migration Invariably there will be modules and projects within DOORS 9 which will not match up to the guidance prescribed for RDNG. Use this section to understand how to easily manipulate your data before migrating.
What if the data to be migrated exceeds the recommendations? The guidance is clearly aimed for the general use cases and is very much our strongest recommendation. It is understood that there are very large enterprise requirements management estates out there. It is recommended that you contact IBM if this applies to you.
|
|||||||||||||||||||||
Feeback Wanted!! Learn to IoTize your Rhapsody Model in just 9 minutes
1. IBM: |
|||||||||||||||||||||
Continuous Engineering for the Electronics IndustryContinuous Engineering for the Electronics Industry- See how IBM continuous engineering solutions can help you tackle the challenges and opportunities of Mobile, Internet of Things and Software and help you Define better, Design Faster, Develop Smar
Learn more about the IBM Internet of Things Continuous Engineering Solution: Tools, best practices and services to help organizations create the connected products at the heart of the internet of things. The IBM Internet of Things Continuous Engineering Solution is designed to help manufacturers create smart, connected devices for the Internet of Things. This solution helps teams adopt continuous engineering practices to address cost, time and quality challenges in delivering complex, connected products. IBM is now adding new product line engineering (PLE) features to help engineers streamline the design of product lines while reducing data duplication and the chance of design errors. And don't miss the featured white paper: The |
|||||||||||||||||||||
Rational Common Licensing – a series of educational videos
Rational Common Licensing – Latest educational videos
Create a Chargeback report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create a chargeback report.
Create an available licenses report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create an available licenses report.
Create a concurrent peak denial report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create a concurrent peak denial report.
Create a concurrent peak usage report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create a concurrent peak usage report.
Create an expiration report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create an expiration report.
Create a license details report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create a license details report.
Create a Token Value report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create a Token Value report.
Create a Userbased report - This video demonstrates how use the IBM Rational License Key Server Administration & Reporting Tool to create a Userbased report.
All these videos are available in the Rational Common Licensing playlist: http
|
|||||||||||||||||||||
About the IBM Software Accelerated Value Program
Do you need extra assistance deploying IBM software that has been sitting on the shelf? Need assistance with managing your upgrades? Would it help to have a single point of contact within IBM Support who can help you connect with a team of subject matter experts? If you are struggling to manage your IBM Software deployment with limited resources, the Accelerated Value Program (AVP) may be able to help.
So, what’s in it for me you ask?
If you plan on attending the upcoming TRIRIGA University event on November 28-29, you can learn more by attending the Accelerated Value Program session hosted by our AVP Program Director, Betsy Autry. Further information and registration details are available in
Additional resources:
|
|||||||||||||||||||||
IoT for Manufacturing: Deep dive of Visual Insights for Quality
IoT for Manufacturing: Deep dive of Visual Insights for Quality with Zachary Ruland, Technical Solution Specialist in Watson IoT
IoT
|
|||||||||||||||||||||
More about Maximo Network on Blockchain
Last week we blogged about a new introductory video: An Introduction: IBM Maximo Network on Blockchain to help you get a better understanding of the IBM Maximo Network on Blockchain solution. This week we are expanding on that topic by including two more recently released videos.
IBM Maximo Network on Bloc
IBM Maximo Network on Blockchain: The General Ledger Query application - You can use the General Ledger Query application to enable your business network to query general ledger transactions according to a specified date range.
You can view the full list of videos in this playlist: IBM
|
|||||||||||||||||||||
New videos for Jazz Reporting Service 6.0.6
New videos are available for the latest 6.0.6 version of IBM Jazz Reporting Service.
JRS:
JRS:
|
|||||||||||||||||||||
CLM 6.0.5 iFix002 available on Fix Central
CLM 6.0.5 iFix002 was made available for download on January 26. This iFix contains fixes for 71 defects broken out for the following products:
For information about downloading this fix (and fixes available for other versions) please go here. |
|||||||||||||||||||||
CLM configuration management: a series providing guidance for planning configuration management
CLM configuration management: Adoption guidance and practices - After you determine whether your organization would benefit from configuration management, you need to evaluate your existing processes and determine how they will change to reflect the new concepts and operations. This article guides you through important considerations for adopting configuration management. See the related articles for additional details about practices and decisions points.
CLM configuration management: Defining your component strategy - Components typically represent physical or logical subdivisions of your product or system. A
CLM configuration management: Patterns for stream usage - This article introduces several patterns of stream usage, or stream strategies, which are described in more detail in additional linked articles. You should already be familiar with the configuration management capabilities, and have decided to investigate further. For the introduction to this series, see Adoption guidance and practices. As part of planning your adoption of configuration management you need to determine your stream strategy.
CLM configuration management: Single stream strategy - Use the single stream pattern for basic change management that’s only in a single domain application (that is, requirements or tests or designs). Typically you use this pattern with the Requirements Management (RM) or Design Management (DM) appl
CLM configuration management: Multistream variant strategy - This article discusses patterns of stream usage for situations where multiple variants of lifecycle artifacts need to be maintained in parallel for each of several releases. This is a common need of product-centric organizations. These and other patterns – including several that these patterns build on – are introduced in the companion Patterns for stream usage article. Read about these base patterns before you read this article. You’ll also find links there to the other stream pattern articles in this series.
CLM configuration management: Multistream concurrent release development strategy - This article explores patterns of stream usage for situations where you work on multiple releases of a product concurrently. Many organizations find these patterns useful on their own. These patterns also form the basis of the more complex multistream variant patterns, as explained in the Multistream variant strategy article. Many patterns are introduced in the companion Patterns for stream usage article. That article in turn points to the other stream details articles in this series. We suggest you read about the more basic patterns, such as the single stream strategy, before you read the current article. The patterns we present here are relatively complex. If an opportunity to “go simpler” presents itself, even for a single component, we encourage you to do so. For example, if you can build and maintain a reusable component of regulatory requirements using a single-stream pattern, rather than one of the multistream patterns, by all means use the simpler pattern.
|
|||||||||||||||||||||
What else did we improve in Collaborative Lifecycle Management 6.0.5 - key updates for client experienceOn December 4th 2017, we announced Now
The list below focuses not on the new product features, but instead, the key wins in the 6.0.5 release which will make life better for users and administators in particular.
Backups There were two main focuses to address the complexity of backup strategies. There is now an inte Typically, like buses, two articles are now available. We wrote a specific article on back We now strongly encourage you to backup your DOORS Next Generation indices so as to lessen the likelihood of needing to run a repotools reindex.
Windows VM users can now consider using alternative performance settings for DOORS Next Generation We have focused on DNG backup strategy mentioned above, so as to ensure that we do not need to run repotools reindex. This was in part prompted by the desire for Windows Virtual Machine(VM) users to be able to use a DNG
Guidance on adopting IBM CLM configuration management across the lifecycle During the same time frame, there was a large intiative to provide guidance on adopting CLM lifecycle configurartion management. Tim Feeney's blog explains the new Bes
Validating and documenting on WebSphere Liberty Profile and Jazz Authorization Server (JAS) It is now possible to authenticate using Smart Cards, or certificates (.p12) with Liberty: and with JAS, see related article: Conf We have also improved the formal IBM Knowledge Center on these topics, cross-linking so you don't need to find these additional resources: Conf Last but not least, Mul
Jazz.net previews In case you missed it. Here's a reminder of the blog post highlighting our new Previews tool: htt In a preview, an expert guides you step-by-step through the various products in the IBM IoT continuous eng
Jazz Community sharing site: A big thank you to the German User Group for creating a new public sharing site available to everyone - see Rolf Nelson's Intr
|
|||||||||||||||||||||
Build a cognitive alert system for your IT operations
Build a cognitive alert system for your IT operations - Monitoring tools today generally send alerts through incidents or email notifications. Often, though, IT teams need a more visually perceptive approach. For example, when an incident or email is received, or an action from an IT service management tool occurs, the IT operator needs either an audible signal on a speaker or a visual signal on a lamp. These types of alerts mean that operators no longer have to keep an eye on the screen or their smartphones. Implementing a solution that integrates service management systems with these types of devices can be quite complex depending on the current architecture. This article by Juscelino Candido de lima Junior demonstrates how you can use a low-cost set of hardware (a Raspberry Pi in a TJBot robot) and Watson APIs, IBM Watson IoT Platform, and other IBM Cloud services to build a cognitive alert system for your IT operations. [Read more...]
Downloadable resources: PDF of the demo use case instructions
|
|||||||||||||||||||||
Recommended better practices when using Lease Accounting Payments in TRIRIGA
Recommended better practices when using Lease Accounting Payments in TRIRIGA - Edgar Mengelberg discusses some simple steps you can consider that are seen as recommended best practices where it concerns your Lease Accounting Payment Schedule run. [Read more...]
More posts from Edgar:
See even more posts on the IBM Real Estate and Facilities Management blog |
|||||||||||||||||||||
Maximo 7.6.0.8+: Setting Security Access for Work Centers
Maximo 7.6.0.8+: Setting Security Access for Work Centers - New features are available starting with the Maximo 7.6.0.8 release to streamline security access to Work Centers with templates. This video starts with an overview of the architecture and features, and then provides a detailed demonstration of the features. Video by Pam Denny, IBM Maximo Analytics Architect
|
|||||||||||||||||||||
DOORS 9 - DNG integration: How does link discovery work?Links between DOORS 9 and DNG use Link Discovery. The link is stored in the source application and is discovered by the target application so :
You should see the "discovering Links" indicator during the process
|
|||||||||||||||||||||
How to upgrade CQ-RTC synchronizer from 5.0.2 to 6.0.3 using ApacheTomcat/7.0.59
Related link:
Environment: RTC upgrade from 5.0.2 to 6.0.3
HTTP Status 404 - ProxyServlet: /cqconnector/
Workaround tomcat library for CQ synchronizer 603 upgrade.
1. Before upgrading the CQ synchronizer from 5.0.2 to 6.0.3, take backup of tomcat libraries present in gateway/tomcat folder.
|
|||||||||||||||||||||
Best Practice for creating SRs and PMRs – Understanding the IBM TRIRIGA Support Process
This page has a Support Resources Home section that provides numerous links to some great resources, including a link to our IBM Service Request system where you can open a Service Request (SR). For convenience, the link for creating a Service Request (SR) is here: http Alternatively, on the IBM TRIRIGA Information and Support Resources page there are also IBM Support phone numbers that can be used to call for support. Once an SR/PMR is opened, it can be tracked for updates via the SR tool. You may also request an update at any time and this will notify the Support team to follow up with you as soon as possible.
For the most efficient IBM TRIRIGA support experience, a few guidelines should be followed:
Also, it is important to have one problem per SR/PMR because if the problem reported is determined to be a defect, we will create an APAR for it and an APAR also can only cover one distinct problem and we can only create on APAR per SR/PMR. More information about SRs, PMRs, and APARs can be found here: http
Please keep in mind that if all issues are logged as severity 1 issues, this is a misrepresentation, and IBM will be unable to provide adequate timely resolution for truly critical issues for all customers.
Keep in mind that any inside knowledge about your particular problem or environment is good to provide as well because Support deals with a wide variety of issues and test cases and might not be aware of how a particular customer has customized their envi
Finally, try to be prompt and clear in your responses as we communicate during the resolution process. Especially with high priority issues. The quicker you can reply that you have received any updates and let us know your response, the better. Again, due to the large volume of issues coming in, by quickly responding it can ensure that your issue remains at the forefront of the minds of those involved.
For additional guidance on the IBM TRIRIGA Support process, please see the following link for our IBM Support Handbook: http
|
|||||||||||||||||||||
GIT RTC integration - How to clone repository via http, file size greater than 300 MB
GIT RTC integration (How to clone repository via http, file size greater than 300 MB) How to clone repository via http, file size greater than 300 MB.
Node.js based server for RTC and Git integration:
Tried with below scenario combination but was unable to clone repos, via ssh if the file size is more than 300 MB. a. GIT RTC integration (how it's descibed in the officicial documentation for RTC 6.0.2):
1) set the value (--m --ma
http
"Ser
|
|||||||||||||||||||||
Using an Agile approach to scope software projects
Using an Agile approach to scope software projects - Authored by Christina Lynch: Software development methodologies are often religiously observed. But we think you stand to lose out by arbitrarily closing yourself off to alternatives. That being said, when it comes to the software scoping process, the best tool for the job is Agile. Why? Because it’s proven time and time again to provide an effective and efficient framework for propelling new software initiatives forward. Helastel take project scoping very seriously indeed and the results of doing that speak for themselves. It boils down to posing the right questions about what the business requires, while gaining a 360 degree understanding of user perspectives, to plot a pathway to the optimum end 'product'. Here's why an Agile methodology lends itself so well to supporting that process. [Read more...] |
|||||||||||||||||||||
IBM TRIRIGA and How to run a simple Survey Fact ETL Job ItemQuestionI would like an example of running an ETL Job Item as simply Running the process fails. CauseUsers see the Activated record and assume they can click Run Process and will get results. There is actual need to enter a set of restraining data to get results. AnswerEvery ETL Job Item is different. You need to fill in information to the record in order to get the results necessary for the transformation or processing. A complete list of field requirements and processing possibilities can be found in the manual link below.
This blog entry is for a sample run of a Survey Fact ETL Job Item.
Related informationIBM TRIRIGA - Running ETL transforms |
|||||||||||||||||||||
How to know if a license is needed for accessing a form or portal?Sometimes a user that supposedly has licenses for a form or portal is not being able to see it, so how do I determine if some license is missing or if the licenses I have are enough? This question often comes up when users start reporting they can not access portions of the application and call in complaining about it. Answer:The best way to see it is to log as an Admin user, for instance "system" and follow these instructions:
In the below example you see that a user accessing via Cloud needs license "IBM Facilities and Real Estate Management on Cloud Enterprise" to access the Contact Center (form triContactCenter).
If you have questions on specific licenses, contact your sales representative from IBM or Business Partner. They are able to see what you are entitled of.
|
