#IBM CLIENT ACCESS 7.1 WINDOWS 10 SOFTWARE#
Starting with V6R1 System i Access for Windows, IBM phased out using the Excel Software Development Kit (Excel SDK) for the Excel data transfer add-in and replaced it with a new add-in based on Microsoft’s Component Object Model (COM). Over the last two releases, IBM i Access for Windows users have had to modify their client setups to make the Excel data transfer add-in work with Excel 2007 and Excel 2010. 2. IBM i Access for Windows Excel data transfer capabilities need tweaking when changing Excel or IBM i Access versions. It is recommending customers start using an alternative to the old Excel data transfer add-in for Excel 2013 and beyond compatibility. But IBM is changing its strategic direction for IBM I to Excel data transfer.
IBM i Access for Windows and its predecessor products have provided Excel import and export capability for companies running AS400, iSeries or Power Systems with IBM i for years, primarily through the Excel data transfer add-in that comes with the product. IBM i Access for Windows has traditionally provided capabilities to export and import DB2 UDB data to Excel spreadsheets…but that’s changing. Here are five things you need to know about the IBM i-to-Excel data transfer feature and what your shop may need to change in the near future.ġ. IBM is no longer supporting the data transfer add-in, and IBM’s stated direction is for users to run another product for Excel 2013 data transfer and future Excel integration. Recent versions of the Excel data transfer add-in aren’t compatible with Microsoft Excel 2013. This flow can be implemented manually by making HTTP requests directly to the various REST APIs (see documentation).There are changes coming if your shop is running an AS400 or iSeries or Power System with IBM i and uses the Excel data transfer function that comes with IBM i Access for Windows (AS400, iSeries) . Make sure to set authorization.introspect as the Allowed Scope. Choose a client Secret and API secret value. In the MobileFirst Operations Console, under Settings → Confidential Clients, add a new entry. Learn more in the Confidential Clients tutorial. If you attempt to make a request to the introspection endpoint without an authorization header, a 401 response is returned.įor the external resource server to be able to request a token for the authorization.introspect scope, the server needs to be registered as a confidential client via the MobileFirst Operations Console. This part happens internally when the MobileFirst lient SDK is used.īecause the introspection endpoint is an internal resource protected by the scope authorization.introspect, the resource server needs to obtain a separate token in order to send any data to it.
#IBM CLIENT ACCESS 7.1 WINDOWS 10 HOW TO#
In this tutorial, you learn how to protect an external resource server by implementing a filter that validates a MobileFirst access token.
You can protect resources on external servers by using the validation modules that are provided with Mobile Foundation. Protected resources can run on the MobileFirst Server (such as Adapters), or on external servers. Using MobileFirst Server to authenticate external resources improve this page | report issue