AcdntlPoet 2700019V2G Visits (1291)
Introduction - Creating your first app with IBM Rapid Apps for Bluemix (Part 1 of 10): Would you like some help getting started with Rapid Apps? Watch this video series to learn how to create your first app. You can follow along and create your own simple app for managing an office supply closet. Your co-workers can use the app to make requests for the office supplies they need. Send your co-workers a confirmation email when they make a request and again when the supplies arrive.
Be sure to click through the rest of the videos below to walk through the whole lifecycle of app creation with BlueMix!
Create a native data set - Creating your first app with IBM Rapid Apps for Bluemix (Part 2 of 10): This video is part 2 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Create a data set to store the supply request information that is submitted to app. Start a data set from scratch by creating a native data set. To begin, define what kind of data you want to collect with your app. Create column headers, which are called attributes and set formatting requirements for each one.
Create the app - Creating your first app with IBM Rapid Apps for Bluemix (Part 3 of 10): This video is part 3 in the video series, Create your first app with IBM Rapid Apps for Bluemix. When you create the app, provide a name and select a template to use as your first screen. After you create the app, create the other screens.
Customize the screens - Creating your first app with IBM Rapid Apps for Bluemix (Part 4 of 10): This video is part 4 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Open the screen editor to customize the screens for your app. Change the template text and add additional widgets to the screens.
Create navigation between screens - Your first app with IBM Rapid Apps for Bluemix (Part 5 of 10): This video is part 5 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Use button widgets to create navigation between the screens of your app.
Preview the app - Your first app with IBM Rapid Apps for Bluemix (Part 6 of 10): This video is part 6 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Preview the progress of your app through an iPhone simulator, iPad simulator, or web browser.
Create a confirmation email - Your first app with IBM Rapid Apps for Bluemix (Part 7 of 10): This video is part 7 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Create a rule that sends a confirmation email to your co-workers every time that they submit a supply request through your app.
Create an email for order arrivals - Your first app with IBM Rapid Apps for Bluemix (Part 8 of 10): This video is part 8 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Create a rule that sends a notification email to your co-workers when the supplies that they ordered arrive.
Test the email rules -Your first app with IBM Rapid Apps for Bluemix (Part 9 of 10): This video is part 9 in the video series, Create your first app with IBM Rapid Apps for Bluemix. Test the email rules by submitting test data in your app. Then check your email to verify that the rules are working correctly.
Deploy the app - Your first app with IBM Rapid Apps for Bluemix (Part 10 of 10): This video is part 10 in the video series, Create your first app with IBM Rapid Apps for Bluemix. When your app is ready to be used, deploy it to IBM Bluemix and share the URL with your co-workers.
AcdntlPoet 2700019V2G Visits (1121)
In this 7 part blog series surrounding the DevOps culture, Adrian Cho (Program Director, Continuous Delivery Evangelist, and Author of The Jazz Process: Collaboration, Innovation, and Agility) tackles some of the less tangible issues as they relate to the connection between delivery logistics, development culture, and continuous delivery.
DevOps Culture – Retrospectives and continuous improvement: In the Collaborative Lifecycle Management (CLM) project we have declared three imperatives for improvement in order to increase our agility with a goal of continuous delivery: culture, process, and tools. Of these three things, culture is, in my opinion, the most difficult thing to change because it’s less tangible than processes and tools and because culture is often deeply ingrained in an organization and a team. [Read More...]
DevOps Culture – Enabling continuous improvement with IBM’s DevOps Maturity Model and Rational Team Concert: In my last post about retrospectives I discussed the way we have been tracking pain points and associated improvement actions to address those pain points. In this post I want to discuss how we’ve taken this even further by using Rational Team Concert to help track our continuous improvement and how we’re using IBM’s DevOps Maturity Model. [Read More...]
DevOps Culture – Increasing shared awareness: The ability of any team to execute with agility is predicated on a shared awareness of important team elements such as the team’s strategy, plans, and current status. A measure of shared awareness is easily gained when team members work alongside one another. You can’t help but notice what your teammate is doing when she is sitting right next to you or in the same room and that can be invaluable if you are working together. However, when teams are spread across physical locations and time-zones, a more conscious effort must be made to create shared awareness. [Read More...]
DevOps Culture – Teaming up: In a previous post Sreerupa Sen wrote about run teams and feature teams and how they are helping to make our continuous delivery successful. I want to expand on that in this post and talk a bit about the culture that enables such fluid organizational constructs to work successfully. [Read More...]
DevOps Culture – Managing friction: In a previous post about retrospectives and continuous improvement I described how we track “pain points” which are issues that block or hinder our ability to develop a specific development capability. Another way to think of pain points is that they are sources of friction. [Read More...]
DevOps Culture – Building robust teams: When it comes to managing projects and teams, the natural inclination for many people is to try to predict and control everything while taking comfort in tools and technology and processes and practices. This happens frequently in software development despite the fact that other, far more mature, domains learned long ago that this approach doesn’t work, especially in a world of constant change. [Read More...]
DevOps Culture – Thriving at the edge of chaos: In my previous post on building robust teams, I mentioned the need to have some people in a team with an appetite for risk and some who are risk-averse. Some people take risks because they are too inexperienced to know better but some experienced people know that it’s important to take risks. [Read More...]
AcdntlPoet 2700019V2G Visits (1010)
Rational Team Concert: Resolve a Conflict- This video describes how to resolve a conflict in Rational Team Concert v4.0. More info
Rational Team Concert: Resolving Conflicts in File Content- This video describes how to resolve conflicts in file content in Rational Team Concert v4.0.3. More info
PaulLiskay 06000284J3 Visits (1291)
The Rational Test Workbench family of products includes
These products have optional components and sometimes it's hard to figure out which package to down load to get everything needed for one of the products.
The components are available individually but they're also bundled into three offerings
RTW (Rational Test Workbench) Offering contains
Note with 8.7 the RITPP is now bundled with RTCP as a separate feature
RPTS (Rational Performance Test Server) Offering contains
RTVS (Rational Test Virtualization Server) Offering contains
Note with 8.7 the RITPP is now bundled with RTCP as a separate feature
Note that some of the individual products are available in two different offerings. In addition some of the optional components for a product requires obtaining two of the three offerings.
For example, to get Rational Performance Tester you'll want the Rational Test Workbench Offering and then the Rational Performance Tester Agent from either the RPTS or RTVS offering.
The complete set of four components for Rational Integration Tester are:
1. Rational Integration Tester (RIT)
2. Rational Integration Tester Agent (RITA)
3. Rational Integration Tester Platform Pack (RITPP)
4. Rational Tester Control Panel (RTCP)
It doesn't matter which offerings these components are obtained, as long as you get all four of them. For Rational Integration Tester customers I usually recommend getting the Rational Test Workbench offering which includes RIT, RITPP, RTCP, and then either the RPTS or RTVS component to get the Rational Integration Tester Agent.
AcdntlPoet 2700019V2G Visits (1684)
Achieving continuous deployment with UrbanCode Deploy by integrating with Rational Team Concert - This article on jazz.net explains in detail how to add the Rational Team Concert integration in Urban Code Deploy and how to extract files from RTC source control management and add in component versions. In our scenario, we have to extract artifacts from Rational Team Concert (RTC) and load them in to components of UCD. However, UCD doesn't include RTC for source configuration by default. So, we will have to download and install a plugin so that we can extract artifacts from RTC.
Read on for more detailed steps as authored by Shuchita Tripathi, an IBM Rational Product Specialist in Tata Consultancy Services Ltd. within Technology Excellence Group (TEG).