Sidebar

Web Service Basics for IBM i

Web Languages
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

As you go through this chapter, know that you will probably start out creating web services in a manner that is both wrong and right.

Written by Kevin Schroeder

Editor's note: This article is an excerpt from Chapter 8, "Web Service Basics," of Advanced Guide to PHP on IBM i.

 

By definition, a web service is a remote procedure call that is made over the web. The web is run using HTTP. So for a remote procedure call to be called a web service, it needs to be called over HTTP or some derivative thereof. Although several protocols are used to pass information back and forth between machines, if this exchange is done over HTTP, then it is technically a web service.

 

No web service standard exists that we need to follow for something to qualify as being a web service. This is both a benefit and a drawback. It is a benefit because getting a web service up and running can be quick and easy to do. The drawback is that the lack of a standard and real constraints makes the world of web services incredibly fragmented. What is "cool" is often what wins out, and it is difficult to find a pattern of best practices because everyone is doing things differently.

 

So, as you go through this chapter, know that you will probably start out creating web services in a manner that is both wrong and right. But understand that it matters less than you think unless you are using a standard such as Simple Object Access Protocol (SOAP), which is very defined, rigid, and verbose.

 

REST

We will start our examination with Representational State Transfer, or REST. There is lots of conversation about what is and is not REST, most of which is largely futile. On a basic level, REST means do X for Y via resource Z. But where the confusion sometimes lies is in how X is done and how Y is represented and what Z looks like. And the confusion is made worse by those who assert that certain REST services that claim to be RESTful are not truly RESTful and give a litany of reasons that rival the 95 Theses, when in reality they just need to take themselves a little less seriously. Most services are not truly RESTful, but it does not really matter.

 

In actuality, most services are REST-like and not RESTful. This is probably because people were using REST-like systems well before REST came along, but REST provided an opportunity for a communication type to coalesce around a standard. As is true with almost every standard, however, nobody follows it perfectly. Perhaps the controversy stems from the fact that nobody wants his or her PhD dissertation to be misrepresented, but reading the dissertation itself does not render a clearly defined standard. Comparing the debate about REST to a "strongly" standards-based approach such as a Request for Comment (RFC) document or W3C standard will demonstrate why there is such confusion around REST. REST is not a highly structured protocol but a series of practices or, rather, an architectural style.

 

As you read through this chapter, know that it would probably throw the REST author in a loop. However, my concern in writing this is to explain the benefits of a REST-like approach as opposed to ensuring RESTful compliance. As with many things, value is in knowing what to use, what to ignore, and how to balance both to optimally implement a given circumstance. As such, I will be highlighting important points to note. If you intend to build a fully RESTful interface, several online and print resources are available that expound upon the subject in fuller detail.

 

Basics

The definition of REST might seem somewhat restrictive because REST is intended to solve web-based problems in a web-based style. For an API that serves a few hundred requests daily, many of these limitations might seem overkill, but the design of REST is intended to allow for several processes to occur.

 

A REST-based architectural style has several constraints, but we will focus on just a few of them. The first is that the system is intended to be scalable. A REST-like system should be stateless. Stateless protocols are much easier to scale than those that are required to maintain state. As a web developer, you will undoubtedly be familiar with the world's most popular stateless protocol: HTTP. Because HTTP is stateless, each request is isolated from other requests and has no knowledge of what happened before, making responses easily cacheable. This is a significant component of designing a REST-like architecture.

 

Caching can be done either on the client or on an intermediary in between the client and the server. As such, an API can use a layered system with many different caches in between, and the client will be none the wiser. Generally, caching is managed via HTTP caching headers to inform any intermediary servers (or the client) what the caching parameters are. However, because each URL is intended to be a location to a representation of a resource, the content can (and should) be cached on the server side as well.

 

Resource Definitions

Much of REST's magic is managed in the way it handles resource endpoints. The tactic was not new or novel, but it unified the approach being used. A REST-based scenario has two basic types of URLs: collection-based and entity-based.

 

When building a typical API, developers often build out the API by using endpoints with verbs; for example, http://localhost/api/users/getUsers (we will be doing something like this later). But this is not the REST way. REST is intended to be representational. In other words, it is supposed to represent the data in your organization, not describe what that data is doing.

 

So for the user example, rather than having a verb in your API call, you have a resource location. In this case, it is http://localhost/api/users. When that URL is queried, the client will receive a list of user resources that will include a URL.

 

Here is where you might get the purists' panties in a bunch. How do you return the results of the query for the user collection? You might think that returning a list of defined users is what you should do. And you would be wrong. Instead, for your API to be properly RESTful, you should return a list of user endpoint URLs. You would then query those individual URLs to retrieve the user data for each. That is what you need for the API to be RESTful.

 

To retrieve an individual entity, you put its unique identifier at the end of the URL: http://localhost/api/users/1. Each entity will have a URL where its data payload can be downloaded from, and only from there.

 

But isn't that kind of wasteful? "I could be making hundreds, or thousands, of queries against an API to get each of the entities I need," you might say. And you would be right. This is exactly why many people use the REST characteristics without being truly RESTful. Being truly RESTful can be a giant pain in the butt. So take some shortcuts, if you must.

 

However, by taking shortcuts, you will lose some of the benefits, namely caching. If you retrieve a user collection that returns entities, can you cache the results? Well, yes. But what happens when someone tries to retrieve the entity via its unique URL? And then what happens when that entity has changed? Now you need to know all the places where that entity has been cached and invalidate them all. Doing so is somewhat easy if you are caching internally in PHP. But what happens if you are using Varnish or some kind of multitier caching system? Then it becomes much more problematic.

 

Usage of HTTP Verbs

Did you know that HTTP has more method actions than just GET and POST? RFC 2616 defines eight (GET, POST, HEAD, OPTIONS, CONNECT, PUT, DELETE, and TRACE), and RFC 5789 adds another one (PATCH) that REST can exploit. A REST-like API does not use verbs in URLs, so you determine the type of action to do via the HTTP method.

 

Wikipedia has a great chart (Table 8.1) that helps put this into perspective. (You can find the chart, along with other information about REST, at http://en.wikipedia.org/wiki/representational_state_transfer.)

 

Table 8.1: Relationship of REST endpoint types and HTTP methods

Resource

GET

PUT

POST

DELETE

Collection URI

List the URIs and perhaps other details of the collection's members.

Replace the entire collection with another collection.

Create a new entry in the collection. The new entry's URI is assigned automatically and is usually returned by the operation.

Delete the entire collection.

Element URI

Retrieve a representation of the addressed member of the collection, expressed in an appropriate Internet media type.

Replace the addressed member of the collection, or if it does not exist, create it.

Not generally used. Treat the addressed member as a collection in its own right and create a new entry in it.

Delete the addressed member of the collection.

 

So to delete an individual user, you would use an HTTP request like this:

 

DELETE /api/users/1 HTTP/1.0

 

To update the same user, use this:

 

PUT /api/users/1 HTTP/1.0

Content-Type: application/json

Content-Length: 68

 

<user>

<name>Kevin</name>

<email>This email address is being protected from spambots. You need JavaScript enabled to view it.<;/email>

</user>

 

Or to delete all of the users, code the following:

 

DELETE /api/users HTTP/1.0

 

Considering that Roy Fielding co-authored the HTTP protocol, it makes perfect sense that he would use it when defining REST. REST does not specifically require HTTP, but it is a protocol that fits REST's needs for statelessness and easy caching better than most others. As such, the HTTP methods correspond nicely to the verbs that REST requires.

 

Authentication

REST does not have a specific method of authentication as part of the standard, so you are free to use whichever authentication method you would like. Given that inherent within the REST definition is the ability to delete an entire collection, you should implement some level of authentication and access control as part of your API. But because you would do that separately from REST, though on top of HTTP, we will not cover it here but later in the chapter (with a more general discussion on authentication for APIs).

 

SOAP

Ah, SOAP. The only protocol that makes you feel dirty after using it. SOAP is one of the most bloated, complicated protocols you will ever see, but it's one of the most sophisticated. For this reason, many developers have rebelled against SOAP and opted for a REST-like approach. Unlike REST, which is an architectural style as opposed to a protocol, SOAP is a protocol that has stringent requirements and expectations from the clients that it interacts with. SOAP's stringent data requirements are also a benefit. Because SOAP is a complex protocol, we will take only a basic look at both the protocol and the PHP implementation.

 

You implement SOAP through the use of an XML document that is generated on the server and then returned to the client. Unlike with REST or many other web service implementations, the structure of the document is extremely important. Additionally, unlike REST, in SOAP the URL is largely unimportant because the remote procedure call is defined in the XML document itself.

 

The base XML document is based on the SOAP schema and must use SOAP namespaces and encoding in the document. You can find the XML Schema Definition (XSD) for the basic SOAP request structure at http://www.w3.org/2001/12/soap-envelope and the encoding at http://www.w3.org/TR/2000/NOTE-SOAP-20000508/encoding-2000-04-18.xml. The root element of the document is soap:Envelope, which has at least two elements: soap:Header and soap:Body.

 

The header does not play as prominent a role as the body does. The header is not required, but the body is. It does not have the same level of structured requirements as the body. However, you can define the header requirements in a Web Services Definition Language file, or WSDL (which we will examine later), and make it a prerequisite for a properly constructed request.

 

But for now, we will look at WSDL-less requests for simplicity:

 

$client = new SoapClient (

     null,

     array (

           'location'    => 'http://localhost/soap/server.php',

           'uri'        => 'http://test-uri/'

     )

);

 

echo $client->getServerDate();

 

This code is setting up a WSDL-less SOAP request. The first parameter in the SoapClient constructor is the URL of the WSDL to use. Because this example does not have a WSDL, you set that value as null. But by doing that, you must provide the endpoint for the SoapClient to call, which you do in an array of options in the second parameter. That value is specified in the location key. But what about that uri key? You use that key to specify the XML namespace for the actual SOAP call XML structure.

 

The method that you call, in this case doCall(), does not exist in the SoapClient class. It is handled via __call(), which lets you act upon the SoapClient object as if it were the remote object itself.

 

When you execute the code, you get the following XML document (reformatted for clarity):

 

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope

     xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

     xmlns:ns1="http://test-uri/"

     xmlns:xsd="http://www.w3.org/2001/XMLSchema"

     xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"

     SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

     <SOAP-ENV:Body>

           <ns1:getServerDate/>

     </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

 

To handle the request, you create an endpoint that instantiates the SoapServer class. You then specify the response URI as well as a list of functions that will be responsible for handling any requests that are made.

 

Following is a basic SOAP server implementation that will handle the request you previously defined:

 

function getServerDate()

{

     return date('r');

}

 

$server = new SoapServer(

     null,

     array(

           'uri'   => ''http://test-uri/'>

     )

);

 

$server->addFunction('getServerDate');

$server->handle();

 

Like SoapClient, the first parameter is a WSDL. However, you are currently running in WSDL-less mode, so you define the uri as one of the options. The URI provides the namespace for the body response. When using functions instead of classes, you must individually include all the functions that will be used to respond to the client.

 

The server generates a response similar to this (again, formatted for clarity):

 

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope

     xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

     xmlns:ns1="http://test-uri/"

     xmlns:xsd="http://www.w3.org/2001/XMLSchema"

     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

     xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

     <SOAP-ENV:Body>

           <ns1:getServerDateResponse>

                 <return xsi:type="xsd:string">Wed, 10 Jul 2013 07:24:45 -0500</return>

           </ns1:getServerDateResponse>

     </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

 

Note that the response is defined in a *Response node under the body node. This is largely uninteresting, however, because it happens behind the scenes. But if you need to see what is occurring, you can use a little-used setting on the client:

 

$client = new SoapClient (

     null,

     array (

           'location'    => 'http://localhost/soap/server.php',

           'uri'        => 'http://test-uri/',

           'trace'       => 1

     )

);

 

This setting lets you use another function called getLastResponse(), which will output the XML document that was received from the server. This is useful for debugging.

 

echo htmlspecialchars($client->__getLastResponse());

 

Although functions are easier to implement for smaller web services, they also become more complicated as the API requirements grow. You can add a simple class by defining the class and then using the setClass() method on the SoapServer instance:

 

class SoapEndpoint {

 

     public function getServerDate()

     {

           return date('r');

     }

}

 

$server = new SoapServer(

     null,

     array(

           'uri'   => 'http://test-uri/'>

     )

);

 

$server->setClass('SoapEndpoint');

$server->handle();

 

If you were to run your client code against this server, the code would operate exactly as it previously did. You could continue this track, but it would result in increasing complexity to the point of nonsense. You can do much to configure the SOAP objects programmatically, but one of the benefits of SOAP is that it is supposed to document and manage a lot of this on its own.

 

Kevin Schroeder

Kevin Schroeder has a memory TTL of 10 years, and so he has been working with PHP for longer than he can remember. He is a member of the Zend Certification Advisory Board and is a Magento Certified Developer Plus. He has spoken at numerous conferences, including ZendCon, where he was twice the MC. When his head isn’t in code (if code is poetry, then it is Vogon poetry), Kevin is writing music, having been a guitarist since hair bands were cool (and having survived their welcomed demise). He has recorded two albums, Coronal Loop Safari and Loudness Wars. Kevin’s wisdom is dispensed to his loyal followers on Twitter at @kpschrade and on his blog at www.eschrade.com, where he speaks in the first person.


MC Press books written by Kevin Schroeder available now on the MC Press Bookstore.

Advanced Guide to PHP on IBM i Advanced Guide to PHP on IBM i
Take your PHP knowledge to the next level with this indispensable guide.
List Price $79.95

Now On Sale

The IBM i Programmer’s Guide to PHP The IBM i Programmer’s Guide to PHP
Get to know the PHP programming language and how it can--and should--be deployed on IBM i.
List Price $79.95

Now On Sale

You Want to Do What with PHP? You Want to Do What with PHP?
This book for the creative and the curious explores what’s possible with PHP.
List Price $49.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • Mobile Computing and the IBM i

    SB ASNA PPL 5450Mobile computing is rapidly maturing into a solid platform for delivering enterprise applications. Many IBM i shops today are realizing that integrating their IBM i with mobile applications is the fast path to improved business workflows, better customer relations, and more responsive business reporting.

    This ASNA whitepaper takes a look at mobile computing for the IBM i. It discusses the different ways mobile applications may be used within the enterprise and how ASNA products solve the challenges mobile presents. It also presents the case that you already have the mobile programming team your projects need: that team is your existing RPG development team!

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

    DDL SystemsDownload the technical whitepaper on MANAGING YOUR IBM i WIRELESSLY and (optionally) register to download an absolutely FREE software trail. This whitepaper provides an in-depth review of the native IBM i technology and ACO MONITOR's advanced two-way messaging features to remotely manage your IBM i while in or away from the office. Notify on-duty personnel of system events and remotely respond to complex problems (via your Smartphone) before they become critical-24/7. Problem solved!

    Order your copy here.

  • DR Strategy Guide from Maxava: Brand New Edition - now fully updated to include Cloud!

    SB Maxava PPL 5476PRACTICAL TOOLS TO IMPLEMENT DISASTER RECOVERY IN YOUR IBM i ENVIRONMENT

    CLOUD VS. ON-PREMISE?
    - COMPREHENSIVE CHECKLISTS
    - RISK COST CALCULATIONS
    - BUSINESS CASE FRAMEWORK
    - DR SOLUTIONS OVERVIEW
    - RFP BUILDER
    Download your free copy of DR Strategy Guide for IBM i from Maxava today.

     

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • 2020 IBM i Marketplace Survey Results

    HelpSystems

    This year marks the sixth edition of the popular IBM i Marketplace Survey Results. Each year, HelpSystems sets out to gather data about how businesses use the IBM i platform and the IT initiatives it supports. Year over year, the survey has begun to reveal long-term trends that give insight into the future of this trusted technology.

    More than 500 IBM i users from around the globe participated in this year’s survey, and we’re so happy to share the results with you. We hope you’ll find the information interesting and useful as you evaluate your own IT projects.

  • AIX Security Basics eCourse

    Core Security

    With so many organizations depending on AIX day to day, ensuring proper security and configuration is critical to ensure the safety of your environment. Don’t let common threats put your critical AIX servers at risk. Avoid simple mistakes and start to build a long-term plan with this AIX Security eCourse. Enroll today to get easy to follow instructions on topics like:

    • Removing extraneous files
    • Patching systems efficiently
    • Setting and validating permissions
    • Managing service considerations
    • Getting overall visibility into your networks

     

  • Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.

    Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    HelpSystemsIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • IBM i Resources Retiring?

    SB HelpSystems WC GenericLet’s face it: IBM i experts and RPG programmers are retiring from the workforce. Are you prepared to handle their departure?
    Our panel of IBM i experts—Chuck Losinski, Robin Tatam, Richard Schoen, and Tom Huntington—will outline strategies that allow your company to cope with IBM i skills depletion by adopting these strategies that allow you to get the job done without deep expertise on the OS:
    - Automate IBM i processes
    - Use managed services to help fill the gaps
    - Secure the system against data loss and viruses
    The strategies you discover in this webinar will help you ensure that your system of record—your IBM i—continues to deliver a powerful business advantage, even as staff retires.

     

  • Backup and Recovery Considerations for Security Data and Encrypted Backups

    SB PowerTech WC GenericSecurity expert Carol Woodbury is joined by Debbie Saugen. Debbie is an expert on IBM i backup and recovery, disaster recovery, and high availability, helping IBM i shops build and implement effective business continuity plans.
    In today’s business climate, business continuity is more important than ever. But 83 percent of organizations are not totally confident in their backup strategy.
    During this webinar, Carol and Debbie discuss the importance of a good backup plan, how to ensure you’re backing up your security information, and your options for encrypted back-ups.

  • Profound.js: The Agile Approach to Legacy Modernization

    SB Profound WC GenericIn this presentation, Alex Roytman and Liam Allan will unveil a completely new and unique way to modernize your legacy applications. Learn how Agile Modernization:
    - Uses the power of Node.js in place of costly system re-writes and migrations
    - Enables you to modernize legacy systems in an iterative, low-risk manner
    - Makes it easier to hire developers for your modernization efforts
    - Integrates with Profound UI (GUI modernization) for a seamless, end-to-end legacy modernization solution

     

  • Data Breaches: Is IBM i Really at Risk?

    SB PowerTech WC GenericIBM i is known for its security, but this OS could be more vulnerable than you think.
    Although Power Servers often live inside the safety of the perimeter firewall, the risk of suffering a data leak or data corruption remains high.
    Watch noted IBM i security expert Robin Tatam as he discusses common ways that this supposedly “secure” operating system may actually be vulnerable and who the culprits might be.

    Watch the webinar today!

     

  • Easy Mobile Development

    SB Profound WC GenericWatch this on-demand webinar and learn how to rapidly and easily deploy mobile apps to your organization – even when working with legacy RPG code! IBM Champion Scott Klement will demonstrate how to:
    - Develop RPG applications without mobile development experience
    - Deploy secure applications for any mobile device
    - Build one application for all platforms, including Apple and Android
    - Extend the life and reach of your IBM i (aka iSeries, AS400) platform
    You’ll see examples from customers who have used our products and services to deliver the mobile applications of their dreams, faster and easier than they ever thought possible!

     

  • Profound UI: Unlock True Modernization from your IBM i Enterprise

    SB Profound PPL 5491Modern, web-based applications can make your Enterprise more efficient, connected and engaged. This session will demonstrate how the Profound UI framework is the best and most native way to convert your existing RPG applications and develop new modern applications for your business. Additionally, you will learn how you can address modernization across your Enterprise, including databases and legacy source code, with Profound Logic.

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.

    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).

  • 5 New and Unique Ways to Use the IBM i Audit Journal

    SB HelpSystems ROBOT GenericYou must be asking yourself: am I doing everything I can to protect my organization’s data? Tune in as our panel of IBM i high availability experts discuss:


    - Why companies don’t test role swaps when they know they should
    - Whether high availability in the cloud makes sense for IBM i users
    - Why some organizations don’t have high availability yet
    - How to get high availability up and running at your organization
    - High availability considerations for today’s security concerns

  • Profound.js 2.0: Extend the Power of Node to your IBM i Applications

    SB Profound WC 5541In this Webinar, we'll demonstrate how Profound.js 2.0 enables you to easily adopt Node.js in your business, and to take advantage of the many benefits of Node, including access to a much larger pool of developers for IBM i and access to countless reusable open source code packages on npm (Node Package Manager).
    You will see how Profound.js 2.0 allows you to:

    • Provide RPG-like capabilities for server-side JavaScript.
    • Easily create web and mobile application interfaces for Node on IBM i.
    • Let existing RPG programs call Node.js modules directly, and vice versa.
    • Automatically generate code for Node.js.
    • Automatically converts existing RPGLE code into clean, simplified Node.js code.

    Download and watch today!

     

  • Make Modern Apps You'll Love with Profound UI & Profound.js

    SB Profound WC 5541Whether you have green screens or a drab GUI, your outdated apps can benefit from modern source code, modern GUIs, and modern tools.
    Profound Logic's Alex Roytman and Liam Allan are here to show you how Free-format RPG and Node.js make it possible to deliver applications your whole business will love:

    • Transform legacy RPG code to modern free-format RPG and Node.js
    • Deliver truly modern application interfaces with Profound UI
    • Extend your RPG applications to include Web Services and NPM packages with Node.js

     

  • Accelerating Programmer Productivity with Sequel

    SB_HelpSystems_WC_Generic

    Most business intelligence tools are just that: tools, a means to an end but not an accelerator. Yours could even be slowing you down. But what if your BI tool didn't just give you a platform for query-writing but also improved programmer productivity?
    Watch the recorded webinar to see how Sequel:

    • Makes creating complex results simple
    • Eliminates barriers to data sources
    • Increases flexibility with data usage and distribution

    Accelerated productivity makes everyone happy, from programmer to business user.

  • Business Intelligence is Changing: Make Your Game Plan

    SB_HelpSystems_WC_GenericIt’s time to develop a strategy that will help you meet your informational challenges head-on. Watch the webinar to learn how to set your IT department up for business intelligence success. You’ll learn how the right data access tool will help you:

    • Access IBM i data faster
    • Deliver useful information to executives and business users
    • Empower users with secure data access

    Ready to make your game plan and finally keep up with your data access requests?

     

  • Controlling Insider Threats on IBM i

    SB_HelpSystems_WC_GenericLet’s face facts: servers don’t hack other servers. Despite the avalanche of regulations, news headlines remain chock full of stories about data breaches, all initiated by insiders or intruders masquerading as insiders.
    User profiles are often duplicated or restored and are rarely reviewed for the appropriateness of their current configuration. This increases the risk of the profile being able to access data without the intended authority or having privileges that should be reserved for administrators.
    Watch security expert Robin Tatam as he discusses a new approach for onboarding new users on IBM i and best-practices techniques for managing and monitoring activities after they sign on.

  • Don't Just Settle for Query/400...

    SB_HelpSystems_WC_GenericWhile introducing Sequel Data Access, we’ll address common frustrations with Query/400, discuss major data access, distribution trends, and more advanced query tools. Plus, you’ll learn how a tool like Sequel lightens IT’s load by:

    - Accessing real-time data, so you can make real-time decisions
    - Providing run-time prompts, so users can help themselves
    - Delivering instant results in Microsoft Excel and PDF, without the wait
    - Automating the query process with on-demand data, dashboards, and scheduled jobs

  • How to Manage Documents the Easy Way

    SB_HelpSystems_WC_GenericWhat happens when your company depends on an outdated document management strategy?
    Everything is harder.
    You don’t need to stick with status quo anymore.
    Watch the webinar to learn how to put effective document management into practice and:

    • Capture documents faster, instead of wasting everyone’s time
    • Manage documents easily, so you can always find them
    • Distribute documents automatically, and move on to the next task

     

  • Lessons Learned from the AS/400 Breach

    SB_PowerTech_WC_GenericGet actionable info to avoid becoming the next cyberattack victim.
    In “Data breach digest—Scenarios from the field,” Verizon documented an AS/400 security breach. Whether you call it AS/400, iSeries, or IBM i, you now have proof that the system has been breached.
    Watch IBM i security expert Robin Tatam give an insightful discussion of the issues surrounding this specific scenario.
    Robin will also draw on his extensive cybersecurity experience to discuss policies, processes, and configuration details that you can implement to help reduce the risk of your system being the next victim of an attack.

  • Overwhelmed by Operating Systems?

    SB_HelpSystems_WC_GenericIn this 30-minute recorded webinar, our experts demonstrate how you can:

    • Manage multiple platforms from a central location
    • View monitoring results in a single pane of glass on your desktop or mobile device
    • Take advantage of best practice, plug-and-play monitoring templates
    • Create rules to automate daily checks across your entire infrastructure
    • Receive notification if something is wrong or about to go wrong

    This presentation includes a live demo of Network Server Suite.

     

  • Real-Time Disk Monitoring with Robot Monitor

    SB_HelpSystems_WC_GenericYou need to know when IBM i disk space starts to disappear and where it has gone before system performance and productivity start to suffer. Our experts will show you how Robot Monitor can help you pinpoint exactly when your auxiliary storage starts to disappear and why, so you can start taking a proactive approach to disk monitoring and analysis. You’ll also get insight into:

    • The main sources of disk consumption
    • How to monitor temporary storage and QTEMP objects in real time
    • How to monitor objects and libraries in real time and near-real time
    • How to track long-term disk trends

     

     

  • Stop Re-keying Data Between IBM I and Other Applications

    SB_HelpSystems_WC_GenericMany business still depend on RPG for their daily business processes and report generation.Wouldn’t it be nice if you could stop re-keying data between IBM i and other applications? Or if you could stop replicating data and start processing orders faster? Or what if you could automatically extract data from existing reports instead of re-keying? It’s all possible. Watch this webinar to learn about:

    • The data dilemma
    • 3 ways to stop re-keying data
    • Data automation in practice

    Plus, see how HelpSystems data automation software will help you stop re-keying data.

     

  • The Top Five RPG Open Access Myths....BUSTED!

    SB_Profound_WC_GenericWhen it comes to IBM Rational Open Access: RPG Edition, there are still many misconceptions - especially where application modernization is concerned!

    In this Webinar, we'll address some of the biggest myths about RPG Open Access, including:

    • Modernizing with RPG OA requires significant changes to the source code
    • The RPG language is outdated and impractical for modernizing applications
    • Modernizing with RPG OA is the equivalent to "screen scraping"

     

  • Time to Remove the Paper from Your Desk and Become More Efficient

    SB_HelpSystems_WC_GenericToo much paper is wasted. Attempts to locate documents in endless filing cabinets.And distributing documents is expensive and takes up far too much time.
    These are just three common reasons why it might be time for your company to implement a paperless document management system.
    Watch the webinar to learn more and discover how easy it can be to:

    • Capture
    • Manage
    • And distribute documents digitally

     

  • IBM i: It’s Not Just AS/400

    SB_HelpSystems_WC_Generic

    IBM’s Steve Will talks AS/400, POWER9, cognitive systems, and everything in between

    Are there still companies that use AS400? Of course!

    IBM i was built on the same foundation.
    Watch this recorded webinar with IBM i Chief Architect Steve Will and IBM Power Champion Tom Huntington to gain a unique perspective on the direction of this platform, including:

    • IBM i development strategies in progress at IBM
    • Ways that Watson will shake hands with IBM i
    • Key takeaways from the AS/400 days

     

  • Ask the RDi Experts

    SB_HelpSystems_WC_GenericWatch this recording where Jim Buck, Susan Gantner, and Charlie Guarino answered your questions, including:

    • What are the “hidden gems” in RDi that can make me more productive?
    • What makes RDi Debug better than the STRDBG green screen debugger?
    • How can RDi help me find out if I’ve tested all lines of a program?
    • What’s the best way to transition from PDM to RDi?
    • How do I convince my long-term developers to use RDi?

    This is a unique, online opportunity to hear how you can get more out of RDi.

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Inside the Integrated File System (IFS)

    SB_HelpSystems_WC_GenericDuring this webinar, you’ll learn basic tips, helpful tools, and integrated file system commands—including WRKLNK—for managing your IFS directories and Access Client Solutions (ACS). We’ll answer your most pressing IFS questions, including:

    • What is stored inside my IFS directories?
    • How do I monitor the IFS?
    • How do I replicate the IFS or back it up?
    • How do I secure the IFS?

    Understanding what the integrated file system is and how to work with it must be a critical part of your systems management plans for IBM i.

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • How to Meet the Newest Encryption Requirements on IBM i

    SB PowerTech WC GenericA growing number of compliance mandates require sensitive data to be encrypted. But what kind of encryption solution will satisfy an auditor and how can you implement encryption on IBM i? Watch this on-demand webinar to find out how to meet today’s most common encryption requirements on IBM i. You’ll also learn:

    • Why disk encryption isn’t enough
    • What sets strong encryption apart from other solutions
    • Important considerations before implementing encryption

     

     

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Fight Cyber Threats with IBM i Encryption

    SB PowerTech WC GenericCyber attacks often target mission-critical servers, and those attack strategies are constantly changing. To stay on top of these threats, your cybersecurity strategies must evolve, too. In this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

     

     

     

  • 10 Practical IBM i Security Tips for Surviving Covid-19 and Working From Home

    SB PowerTech WC GenericNow that many organizations have moved to a work from home model, security concerns have risen.

    During this session Carol Woodbury will discuss the issues that the world is currently seeing such as increased malware attacks and then provide practical actions you can take to both monitor and protect your IBM i during this challenging time.

     

  • How to Transfer IBM i Data to Microsoft Excel

    SB_HelpSystems_WC_Generic3 easy ways to get IBM i data into Excel every time
    There’s an easy, more reliable way to import your IBM i data to Excel? It’s called Sequel. During this webinar, our data access experts demonstrate how you can simplify the process of getting data from multiple sources—including Db2 for i—into Excel. Watch to learn how to:

    • Download your IBM i data to Excel in a single step
    • Deliver data to business users in Excel via email or a scheduled job
    • Access IBM i data directly using the Excel add-in in Sequel

    Make 2020 the year you finally see your data clearly, quickly, and securely. Start by giving business users the ability to access crucial business data from IBM i the way they want it—in Microsoft Excel.

     

     

  • HA Alternatives: MIMIX Is Not Your Only Option on IBM i

    SB_HelpSystems_WC_GenericIn this recorded webinar, our experts introduce you to the new HA transition technology available with our Robot HA software. You’ll learn how to:

    • Transition your rules from MIMIX (if you’re happy with them)
    • Simplify your day-to-day activities around high availability
    • Gain back time in your work week
    • Make your CEO happy about reducing IT costs

    Don’t stick with a legacy high availability solution that makes you uncomfortable when transitioning to something better can be simple, safe, and cost-effective.

     

     

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    SB HelpSystems SC 5413Robot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    SB HelpSystems SC 5413Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.

  • ACO MONITOR Manages your IBM i 24/7 and Notifies You When Your IBM i Needs Assistance!

    SB DDL Systems 5429More than a paging system - ACO MONITOR is a complete systems management solution for your Power Systems running IBM i. ACO MONITOR manages your Power System 24/7, uses advanced technology (like two-way messaging) to notify on-duty support personnel, and responds to complex problems before they reach critical status.

    ACO MONITOR is proven technology and is capable of processing thousands of mission-critical events daily. The software is pre-configured, easy to install, scalable, and greatly improves data center efficiency.