Modified on by Christian Karasiewicz
This blog post contributed by Bhargav Perepa, a WebSphere IT Specialist/Architect at IBM Federal Software Group in Washington D.C.
Are you feeling confused with mobile withdrawal symptoms? Are you living like Neanderthals disconnected from your mobile devices due to uncovering of Heartbleed vulnerability in the OpenSSL library? Rest assured you are in a very large company.
A billion smartphones were sold in 2013 according to mobilethinking.com, and smartphone users employ their devices for many reasons, for example:
To make routine and urgent phone calls
To communicate with friends, family and coworkers using voice, SMS and MMS texting and email tools
To manage business and personal appointments using calendar and location features
To engage in extended social interactions using social media avenues (Twitter, Facebook, LinkedIn and so forth)
To make critical and much-needed transactions online (purchase medicine from online stores or deposit a check using a mobile banking application)
We engage in daily routine and mission critical activities (for both personal and business purposes) using mobile devices, and OpenSSL is present in many of these engagements behind the scene.
Mobile devices are uniquely positioned to be more vulnerable for a couple of reasons. One is their portability: since they are portable they are prone to physical theft or user forgetfulness or misplacement. Another is that mobile devices have a concept known as rooting and jailbreaking. Rooting refers to acquiring administrative privileges on the device in an unapproved sense from some stakeholder’s perspective (the device OS vendor or your IT department, or from a running application perspective).
Consider the following wisdom from Tech Net:
If a bad guy has unrestricted physical access to your mobile device, it's not your mobile device anymore (nor his if someone else steals from him).
Given how critical mobile devices are to our daily lives, we need to be extra aware of mobile vulnerabilities. The moral of the story is: do not lose your smartphone if you have rooted or jailbroken it—if you can help it!
How could Heartbleed vulnerability potentially affect the Worklight community?
Here is an update from our IBM Worklight, WebSphere development and thought leadership team members respectively (Bill Dodd, Bill J. O’Donnell and Dustin Amrhein).
For the Worklight Server: We do not use OpenSSL in IBM Worklight Server. SSL termination for the Worklight Server is handled by the application server (WebSphere, Liberty or Tomcat). WebSphere and Liberty are not affected by this vulnerability. Per our understanding, Tomcat may be using OpenSSL, depending on configuration options. Hence clients using Worklight Server on Tomcat should verify if their Tomcat installation is vulnerable and, if so, take recommended actions.
For the Worklight client: Customers using Worklight client mobile applications with FIPS 140-2 capabilities enabled (for data in motion security) are at risk of the Heartbleed vulnerability. For more information, please visit IBM Security Bulletins.
Stay ahead of threats
IBM X-Force Research and Development employs security professionals to monitor and analyze a variety of security issues, including threats stemming from usage of mobile and portable technologies. It also produces the IBM X-Force Threat Intelligence Quarterly report to help clients.
IBM X-Force Threat Intelligence Quarterly - 1Q 2014 is available now and covers the topic of "Mobile threats: Perception versus reality” (page 12). As I mentioned previously, when mobile devices are stolen or forgotten or otherwise orphaned, these devices could potentially contain valuable enterprise data related to electronic protected health information (ePHI—such as lab results or other patient information in email format), personally identifiable information (PII—such as SSN) or intellectual property (such as a filed but undisclosed patent). As part of this mobile topic coverage, X-Force research uncovered no reported incidents of ePHI being lost or stolen from mobile devices (see Figure 1).
Figure 1: Public disclosures of ePHI by mobile media type, 2009 to 2013
For more insights on the most recent IT security threat landscape and to better understand the mobile threats with regard to perception versus reality, please read our latest and complete IBM X-Force report here.
Have you ever thought about the vulnerability of ePHI, PII or your enterprise’s intellectual property on your BYOD smartphone or tablet? Share your insights, tips and wisdom with me on Twitter @Bperepa.
Modified on by MartinKeen
This blog post contributed by Owen Cline, a member of the IBM Software Services for Websphere team based in San Diego, California.
What is headless BPM?
Headless business process management (BPM) is the concept of using only the IBM BPM Process Server to execute process flows without any user interface (UI) coach forms.
Why do it?
There are good architectural reasons why someone would consider a headless BPM solution. Consider these scenarios:
You have a BPM workflow that is a batch workflow (or micro flow) and doesn't require any human tasks. In this case, the BPM process application is started externally. It runs through its activities, and finally the process application completes.
You already have an existing UI layer that it likes. For example, the client has a portal developed that it will continue to use.
You have a technical challenge, like the client wants to embed an existing UI page (a JavaServer page [JSP], for example) in an iFrame in a coach. One issue with doing that is that the "look and file" between the coach and the embedded page will be different. Another issue can arise if there is a requirement to signal the coach when the user completes data entry in the embedded page.
Your UI developers only know a particular technology like .Net, JSP or JavaServer Faces (JSF) and they don't plan on learning how to develop coaches.
You need to provide a mobile app that you host from IBM Worklight that is the UI to your BPM process application.
Headless BPM patterns
Use coaches in an external user interface
In this pattern, an external UI displays coaches in an iframe. This pattern is used if the user does not want to use the IBM BPM process portal but does want to use the coaches.
Use coaches programmatically
Using coaches programmatically means that you do nothing special in your BPM application. In this pattern you add user tasks with coaches as you normally would.
This allows you to have a coach UI in the BPM application in case some users will work with the coach forms from within the BPM process portal.
But, this pattern also allows you to progress through the BPM process application programmatically from an external UI or application.
This is because the BPM REST API allows you to claim a User Task (Assign Task), modify a User Task's output variables (Set Data) and, finally, complete the task (Finish Task).
Take this BPM process application, for example:
And here are the process application variables:
And, here is the headless BPM User Task:
And, here are the headless BPM User Task variables:
First, we start an instance of the headless BPM process application. And, the process instance blocks on the headless BPM User Task where the task ID is 207.
Next, using the BPM REST API Tester, we claim the task (Assign Task to Me, the admin user):
Next, we check the Process Inspector to verify that the headless BPM User Task is assigned now to the admin user:
Next, we will issue a Get Data command to check the value of the output variable. If there were more output variables, we could set all of them in one Get Data command. Notice that the output variable is NULL.
Next, we will issue a Set Data command to change the value of the output variable. If there were more output variables, we could set all of them in one Set Data command.
Next, we will issue a Finish Task command (and set the output variable).
After the Finish Task call, the task (and the process instance) completes.
Use external implementations
You can provide an external implementation for User and System Tasks. Think of them as breakpoints in your process flow. And, yes, they can have input and output variables that you can externally access and set using the BPM REST API commands seen above. The User and System Tasks are handled the same way that the User Task implemented with coaches was above. You still have to claim them (Assign Task), change the variables and then complete them (Finish Task).
This pattern is a common one for mobile-based UIs that connect to the BPM engine.
Here we create an external implementation:
And here we assign the newly created external implementation to a System Task (and it could have been a User Task with no coaches):
You can also use a hybrid solution where you have both a User Task with coaches and a User Task implemented as an external implementation. In front of them, you have a gateway to test a Boolean variable that routes to one of the two.
As I mentioned above, there can be good requirements where you will need to model headless BPM process applications.
You can use several patterns depending on your particular business requirements, like:
You need to use and existing application.
You are developing a mobile app for IBM Worklight for your BPM application.
There is some reason why the client doesn't want to use coaches.
You can consider several patterns:
Use coaches but programmatically complete them.
Use external implementations of User or System Tasks.
Use both in a hybrid BPM process implementation.
Have you tried a headless BPM solution? Let me know how it went or post your questions below.
Modified on by Neil.Patterson
In it,Tina covers the key capabilities of MQA and the incredible value these bring to a variety of stakeholders, both inside and outside your organization. Tina shows through the whiteboard session, the value of:
distributing apps in minutes to your testers, both internal and external;
reporting bugs in seconds with rich contextual data effortlessly captured and submitted;
mining mobile app ratings and reviews in an intuitive, powerful dashboard with drilldown
Modified on by Christian Karasiewicz
This blog post is contributed by John Samuel who focuses on the Internet of Things and M2M with IBM.
You might have seen my previous articles about how technology like IBM MessageSight can connect cars or help insurance firms reduce installation costs. I use these two scenarios when I talk to audiences about IBM MessageSight, and because most people drive cars, they always listen and become engaged in the discussion. But nothing gets an audience talking more than a demo, and it is even better if they can take part in that demo.
Well thankfully there is an awesome demo available that I use during these presentations. It is called StarFighter, and it is based on 1980s arcade games like Asteroids. You too can access it here.
Up to twenty players can play at once, so you can ask your audience to just access the link if they’d like to have a go at it. While the willing volunteers are busy playing the game, you can explain what is happening by showing the viewer panel. A quick warning here: you might have to re-explain what was happening as this game is so addictive and competitive that the audience can become fixated on it and might be unable to hear your explanation.
So let me explain what it is showing and why it is so awesome. Each time you hit a control button like the space bar (fire button), cursor button (left or right arrow) or thrust button (up arrow), an MQTT (MQ Telemetry Transport) message is sent or published to the IBM MessageSight appliance, which then sends an MQTT message with that action to all the subscribing players. This way the other players see your bullets or maneuvers in their browsers or on their mobile devices. The really cool bit I like about this is the shear speed—all this happens in near real time!
Because these actions happen in almost real time you can avoid being blasted by the others playing the game or you can do your best to blast them out of the game. Each time your spaceship hits a space rock you get points, and if you destroy another spaceship you get more points. For those of you who might get addicted, there are multiple levels to play. The harder the level, the more points you will get for blasting stuff, but beware because your shields won’t protect your ship for as long and aren’t repaired as quickly.
I like presenting this action demo because I’m rubbish at playing it: my name, JS, doesn’t appear on the leaderboard often.
What it does show to mobile app developers and designers is how MQTT can be used to send data from mobile devices either to another mobile device or into the enterprise by leveraging the power of IBM MessageSight. Because IBM MessageSight is also a secured appliance, it can safely be put at the edge of a data center in the DMZ so the company doesn’t have to open scores of firewall ports to potentially hundreds of thousands of mobile devices. Keeping a firewall strong is a recommended way of keeping yourself safer from hackers, so this is an important point if you are deploying mobile apps.
I’ve heard it said that we learn quickly and easily through games, and this StarFighter game certainly helps to show that. It is a great assistant when I’m explaining how IBM MessageSight can help get data from multiple mobile devices back to the companies that need that data.
So why not have a go and have some fun while you learn? Be careful though, playing this game to excess can lead to extreme extremeness.
If you are interested in trying out IBM MessageSight for yourself, you can download the virtual appliance at no cost here.
Have fun and please feel free to comment here if you like, or follow me on Twitter @JSamuelatWork as I often post about the Internet of Things.
Modified on by TinaZhuo
This blog is contributed by Jungwhan Cho, a mobile architect from IBM with 10 years of experience in the mobile industry.
It’s a well-known fact that iterating releases for bug fixes and improvements is critical for an app’s success. Using various monitoring tools and methods such as Google Analytics and A/B testing, developers find ways to improve the quality of apps and making it easier for users to do what the developers want them to do. However these types of feedback don’t tell the whole story; how do users actually feel about your application?
This is where user reviews come in. In both the short and long run, you can’t ignore user reviews; after all, users are spending time to rate and comment on your app, and sometimes they can be unpleasant; but they are all critical to the success of your application. A lot of times, you don’t get that many reviews a day, allowing you to determine the areas of improvements on which you should focus. However when your app finally gets the attention it deserves, it’s difficult to get an overview of how users feel about your latest release, and keying on one area without prioritization makes you feel uneasy.
There is also a good chance that you are ignoring signs of a significantly poor area. Perhaps if you are like me, a techie, you may have a natural tendency to focus on technical issues and features and discard comments of a subjective nature such as poor usability or inconsistent UI designs that probably deserve more attention. So you hire someone to do constant monitoring of the quality of the app, by testing the app before the release, as well as collecting crash and analytics data. There is a good chance that your new hire, an aspiring graduate from an eminent university, will be sacrificing his/her evenings having to go through hundreds or thousands of reviews, reorganizing them in an excel file that is ever evolving, unwilling to yield into simplicity.
If you’ve ever wondered, with all the hype of semantic web and big data, why there isn’t a tool out there that allows you to get an overview of user reviews, then you’ve come to the right place.
Having developed numerous applications, a few with relative success and others not so much, I believe my experiences speak for many developers out there who found iterative releases by listening to users to be a critical factor in building a successful app.
Below is a snapshot I got from using IBM MQA during the open beta. And it delivers exactly what it promises to; by considering the large amount of information available on each area, filtered on areas that really do matter and which users do tend to care about.
The report shows that while usability, content and interoperability scored high, it's saying that there isn't sufficient information on elegance, pricing and privacy to provide a quantified information.
I have not disclosed the name of the app, but you can tell that the app is free without any in-app purchasable items, and without much UI and concerns about privacy, security (which may mean network connection is not required). However usability, performance and interoperability are high, and they scored high relative to other apps. If you guessed this app is a video player, then you've guessed it right. Having gone through the reviews manually in the past, I am quite surprised that the report reflects rather accurately on the overall user reviews, and also reflecting on iterations we had to go through in order to focus on what mattered in a video player.
Seeing a few other apps’ user sentiments, it’s clear that once you are used to this feature, you will not want to go back to a world where this is without. Check it out for yourself at the IBM Mobile Quality Assurance site.
Modified on by MartinKeen
This blog post is contributed by Martin Keen, an IBM Redbooks Project Leader.
The IBM Redbooks app (available for Android and iOS) provides no-charge access to technical books and papers covering all aspects of IBM’s products and services. Since its release earlier this year, the app has already received over 20,000 downloads.
In this hands-on video I demonstrate the Solution Topics feature added to V1.1 of the app. This feature allows users to find Redbooks deliverables grouped by IBM’s strategic focus areas. It addresses focus areas for: some of the highlights of the app. I found the best features to be the speed with which I could navigate the catalog and the ability to save books locally onto my mobile device so I could read them even when I’m offline (perfect for my next plane journey).
Big data and analytics
Expert integrated systems
I found the Solution Topics feature to be a much better alternative to using the search feature to find deliverables on these topics.
Have you downloaded the latest version of the IBM Redbooks app and used the Solution Topics feature? Which other focus areas would you like to see added? Let me know in the comments or connect with me on Twitter.
Modified on by TinaZhuo
Mobile apps, like yours, are developed for people. People like you and me. We have opinions and emotions. We are curious. We are willing to give your app a try, and if we like it, we will let our friends know. If we don’t like the experience, it takes only a couple of finger gestures to delete your app. If we still like you as a brand, and would like you to deliver a better app, we may go to the app store and give you a 1 star rating and ask you to get your act together with review comments that could be devastating to you. These comments will be there in public app stores for a very long time, for everyone to see.
So how do you develop apps that people will love to use? Dong Nguyen, the Flappy Birds developer, may have found some secret recipe for it. But if your target users are different from Flappy Bird, the secret recipe will likely not work. However it is no secret to all of us that a great mobile app needs to be fit for purpose. And it needs to be engaging and easy to use. And you simply can’t put enough emphasis on user experience when you develop mobile apps.
So how do you test out your app’s user experience? TestFlight has been a very popular beta testing web service for mobile app developers. However, it would no longer offer Android support starting in March. You can learn more about it from this news report from TechCrunch on TestFlight Owner Burstly Acquired By Apple.
If you are developing mobile apps for multiple platforms, you want a single user-testing solution for it! We strongly recommend IBM Mobile Quality Assurance (MQA) as an alternative. IBM Mobile Quality Assurance is a cloud service that offers a broad set of tools for mobile app developers who want rich user feedback at different stages for mobile app development. And it supports beta user testing for iOS, Android and Windows Phone. I recommend you check out this developerWorks article by Leigh Williamson on Add IBM Mobile Quality Assurance to your quality regimen.
I would like to highlight IBM Mobile Quality Assurance’s ability to enable testers to submit defects in seconds while using the app from their mobile devices. These testers could be your in-house testers, crowd-sourced testers, beta users, and key business stakeholders. They can simply shake their mobile devices to take screen captures, annotate them, write a sentence or two about issues that they have experienced, and submit a bug report from the device. Please check out this 90-second video on IBM Mobile Quality Assurance. You will see exactly what I am talking about. IBM Mobile Quality Assurance has made it effortless for testers/beta users to send you a rich and meaningful bug report. In fact, it has made it so easy that testers will love testing your apps, and your stakeholders will enjoy collaborating with you. With them on your side from the very beginning of the journey, you are equipped to deliver a great mobile experience for your users
Modified on by Christian Karasiewicz
This blog post contributed by Owen Cline, a member of the IBM Software Services for Websphere team based in San Diego, California.
With IBM Worklight, you can extend your business to mobile devices. Worklight provides an open, comprehensive and advanced mobile application platform for smartphones and tablets. It helps organizations of all sizes to efficiently develop, test, connect, run and manage mobile applications. Using standards-based technologies and tools, IBM Worklight provides an integrated platform that includes a comprehensive development environment, mobile-optimized runtime middleware, a private enterprise application store and an integrated management and analytics console, all supported by various security mechanisms.
Patterns in IBM PureApplication System
Many critical tasks related to application development, configuration and deployment are time-consuming and expensive while also requiring high skill levels and carrying the risk of human error. But what if these activities were contained within a modular pattern that automatically executed and performed most of the required steps in these tasks? That is exactly what the IBM PureApplication System is designed to do.
IBM PureApplication System environments employ embedded patterns that deliver all of the expertise needed to deploy, manage and maintain an application. IT departments can save time and eliminate risk while gaining an efficient, repeatable deployment option that ensures configuration consistency.
Today, patterns are available for deploying web applications, databases and data marts, and other middleware environments. More than 100 other patterns are available from independent software providers. They include patterns for business process management, portals, web content management, business intelligence and more.
There are also patterns specifically for IBM Worklight, such as IBM Mobile Application Platform Pattern Type and IBM Mobile Application Platform Pattern Extension for Worklight Studio.
The IBM Mobile Application Platform Pattern Type is composed of the following patterns:
IBM Web Application Pattern
IBM Mobile Application Platform Pattern
In addition to all components provided by IBM Web Application Pattern, IBM Mobile Application Platform Pattern provides the following components:
Worklight application component
Worklight adapter component
Worklight configuration component
Worklight application component link to enterprise application (Websphere Application Server) component
Worklight adapter component link to enterprise application (Websphere Application Server) component
Enterprise application (Websphere Application Server) component link to Worklight configuration component
Worklight configuration link to user registry (Tivoli Directory Server)
Deploying to the cloud using IBM PureApplication System and IBM SmartCloud Orchestrator
Worklight provides the capability to deploy and manage IBM Worklight Servers and applications on PureApplication System and IBM SmartCloud Orchestrator.
Using IBM Worklight in combination with PureApplication System and SmartCloud Orchestrator provides a simple and intuitive environment for developers and administrators to develop, test, and deploy mobile applications to the cloud. The following components are available:
IBM Mobile Application Platform Pattern Type: Provides IBM Worklight runtime and artifacts support for IBM PureApplication System
IBM Mobile Application Platform Pattern Extension for Worklight Studio: Provides Mobile Application Platform Pattern tooling support for Worklight Studio
Ant command line interface: Provides an alternative method to build and deploy Worklight Virtual Application
Installation of IBM Worklight support for PureApplication System
Install the IBM Mobile Application Platform Pattern Type
You must install the IBM Mobile Application Platform Pattern Type and IBM Worklight PureApplication System Extension for Worklight Studio.
You use the PureApplication System Workload Console to install the IBM Mobile Application Platform Pattern Type.
You can find the worklight.ptype-184.108.40.206.tgz file in the worklight-pattern-offering.zip file. Make sure you extract it before you start this procedure:
Log in to IBM PureApplication System with an account that has permission to create new pattern types.
Go to Workload Console > Cloud > Pattern Types.
Upload the IBM Mobile Application Platform Pattern Type .tgz file.
On the toolbar, click the plus (+) button. The "Install a pattern type" window opens.
On the Local tab, click Browse, select the IBM Mobile Application Platform Pattern Type .tgz file, and then wait for the upload process to complete. The pattern type is displayed in the list and is marked as not enabled.
In the list of pattern types, click the uploaded pattern type. Details of the pattern type are displayed.
In the License Agreement row, click License. The License window is displayed stating the terms of the license agreement.
To accept the license, click the Accept button. Details of the pattern type now show that the license is accepted.
In the Status row, click Enable. The pattern type is now listed as being enabled.
Install the IBM Worklight PureApplication System Extension
IBM Worklight PureApplication System Extension is included with IBM Worklight Studio Enterprise Edition and Consumer Edition. When IBM Worklight Studio is installed in the Eclipse development environment, the Worklight PureApplication System Extension is also installed.
Working with the IBM Mobile Application Platform Pattern Type
Working with the IBM Mobile Application Platform Pattern Type involves creating an IBM Mobile Application Platform Pattern, integrating with Tivoli Directory Server, connecting to a Tivoli Directory Server and managing Worklight VAP instances.
Working with IBM Worklight PureApplication System Extension for Worklight Studio
Working with IBM Worklight PureApplication System Extension for Worklight Studio involves setting up PureApplication System preferences, deploying your Worklight project to PureApplication System and integrating with Tivoli Directory Server.
Building and deploying IBM Worklight virtual applications by using the command line interface
IBM Mobile Application Platform Pattern includes a set of Ant tasks to help you build Worklight virtual applications and artifacts and deploy to IBM PureApplication System.
Deployment of the Application Center on IBM PureApplication System
You must configure and connect the operational components of the Application Center to deploy the enterprise application on PureApplication System.
For more information, check out this reference site or leave a comment or question below.
Modified on by ddbaron
Companies use IBM UrbanCode Deploy to achieve automated deployment at scale for web, distributed and now mobile apps alike. While this kind of DevOps practice may be starting in your company, if you’re the mobile team, you may not realize how it can help you too.
As I visit with IBM clients, I’m thrilled to see the practice of continuous integration (CI) used consistently by teams to automate building mobile apps. In the beginning, the CI solution often involves Git and Jenkins, and why not? With Jenkins supporting over 600 plug-ins and a very active community, it’s the #1 open source CI server.
However, I’ve noticed some recurring patterns in how these teams evolve:
It doesn’t take long after they really want an integrated way to track who's doing what, and when it will get done. I’m not going to elaborate on this today, so let me just suggest you checkout IBM JazzHub (and you don’t have to give up Git or GitHub to get started).
The CI Server gets overloaded with deployment tasks, and the deployment and testing part of the pipeline gets inefficient, fast.
I’m going to focus on issue #2, and stick to just the Android OS target for now.
You’ll find the Android Emulator Plugin for Jenkins offers a lot of very useful features. As part of a CI process, it’s great for doing some basic shake down testing using an emulator or device. In this blog entry, Hans Capelle does a nice job describing workarounds for some common issues you’re likely to encounter.
But don't make the mistake of overloading this useful plug-in. Despite a matrix job feature, it really only allows you to launch one emulator per job. To launch automation tests for different phases, different types of tests, different form factors, and different Android OS versions, it means you have to create tens of Jenkins jobs and manage them. Furthermore, if you’re targeting multiple platforms, not just Android, there’s no way to specify if the build should actually be deployed and tested on Android.
Enter the new Android SDK plug-in for IBM UrbanCode Deploy (UCD). Rather than trying to force Jenkins to handle the deployment of your Android app to emulators or devices, you can use the automated deployment engine of UCD to handle it.
And you don’t have to give up Jenkins because UCD has a plug-in for that too! Simply use Jenkins to do the CI work it’s best at, and then pass the APK (and Android SDK-based tests) to UCD to handle the automated deployment of your app to one or more distinct environments for testing. So your environment, for example, could be:
The new Android SDK plug-in makes it possible to define deployment processes that deploy and even test your app. With the Android SDK plug-in, you can interact with the app by:
Install app / Remove app
Run an ADB command (an SDK tool)
Run an Android command (an SDK tool)
UI Automated Testing (Android SDK)
Unit (or Activity) testing (Android SDK)
Random UI (or monkey) Testing (Android SDK)
And the plug-in doesn’t stop at application interaction; you can also manage your emulators through:
Create / Remove
Start / Stop
You can download the new plug-in here, and don’t hesitate to provide feedback; it’s critical and highly appreciated. Best of luck with your Android apps!
Have you tried out the open beta for IBM Mobile Quality Assurance? Looking to find out more so you can take full advantage of this great new service? Do you have questions about the product? Come meet up with us on February 20, 2014 at 4 PM ET.
Use this time to better understand the key features of the product and the benefits they provide. Ask questions you may have. We are here to help you make progress and we would also like to hear from you any problem areas or concerns that you may have.
INSTRUCTIONS TO JOIN WEB CONFERENCE
1. Go to the URL, https://www.ibm.com/collaboration/meeting/join?schedid=2241845
for IBMers, https://w3.ibm.com/collaboration/meeting/unyte.nsf/join?OpenForm&schedid=2241845
2. Please choose "Sign In" in the upper right hand corner of the page
3. Click 'Join Meeting' button on the right side of the page
INSTRUCTIONS TO JOIN AUDIO CONFERENCE
AT&T Reservationless Conference Information
Toll free: 1-888-426-6840
Participant Passcode: 130 21 519
The IBM Mobile Quality Assurance product team