Layer7 API Management

 View Only

Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance 

Jun 11, 2015 11:36 AM

IMPORTANT: This document has been retired, in favour of the official product documentation which lists the update files and upgrade paths. Please check the version of your documentation to ensure it's accurate for your upgrade scenario. Here is an example of said documentation with a file listing for Gateway version 9.3: List of Update Files - CA API Gateway - 9.3 - CA Technologies Documentation

Background

The CA API Gateway is designed around two major components: The Platform and the Application. The Platform consists of the server that runs the API Gateway appliance and the dependency applications and tools that are located on it. This includes (but is certainly not limited to) the Linux kernel, OpenSSL, and MySQL. The Application is the Java component of the API Gateway. It is made up by the Oracle Java Development Kit (JDK) as well as the Java programs that comprise the API Management product suite. These two components are designed to be updated separately to allow systems administrators to upgrade the Platform without upgrading the Application. This ensures that the API Gateway remains compliant with security protocols and is protected against common threats.

 

Fully upgrading an API Gateway appliance involves upgrading both the Platform and the Application. This document will prescribe any patches necessary for upgrading from one specific version to another specific version within the 8-series of the API Management suite. This includes versions 8.0.0, 8.1.0, 8.2.00, and 8.3.00.

 

The documentation for performing an actual upgrade is contained within the CA Technologies Documentation. Please consult the documentation for installing these updates.

 

Important: The official product documentation for upgrading to the target version of API Gateway will soon be including the details of what files are needed and which ISO images they are found in, and much more. Once that migration of information is complete, this community document may be retired in favor of the official product documentation. For now, this document will be maintained until it is confirmed that all necessary information exists in the official product documentation.

 

Prerequisite files

The two tables below reflect lists of files to download for upgrading the API Gateway appliance. Select the existing Source Version and desired Target Version and download the applicable files via the links in the third column. For example: An administrator wishes to upgrade from version 8.0.0 to 8.2.00. This involves downloading the 8.2.00 Application Update as well as three Platform Updates: Trust Store Update, 8.1.0, and 8.2.00.

 

The patches should be applied in the order specified in the Update column. Additionally, all applicable Platform Updates should be applied before the required Application Update. For example: Patches for an upgrade from 8.0.0 to 8.2.00 should be applied in the following order:

  1. Trust Store Update
  2. Platform 8.1.0
  3. Platform 8.2.00
  4. Application 8.2.00

 

Downloading the files

Since the migration to CA Support Online from the Layer 7 Support Portal, the links have changed, there are no longer any direct links to the files in the tables below. The Application Updates and the Platform Updates are all included in the associated ISO file which contains all the relevant files to upgrade from the previous version.

 

For quick reference, the high-level instructions from the documentation are as follows:

  1. Log in to CA Support Online.
  2. Point to Download Center and then choose Download Products.
  3. On the Download Center page:
    1. Select My Products and then choose your product from the drop-down list (if not already displayed).
    2. Select the release number.
    3. The Gen level is '0000' for base releases and '01' for service pack releases.
    4. Click Go to see the DVD disk images for the release.
  4. Review the Release Notes to see a listing of the contents of each disk image.
  5. Download the appropriate image(s) to your hard drive and open it using a tool capable of extracting ISO images.
  6. Locate the necessary patch files in the disk image and copy them to a temporary location on your hard drive.
  7. Copy the patch files to the CA API Gateway appliance using the SCP command. The recommended directory is /home/ssgconfig, but another directory may be used

 

The instructions above are provided with more details on how to patch an appliance on the product documentation page. Be sure to choose the version of documentation applicable to your target version of the API Gateway. You can change the version of documentation by clicking the versions button on the upper-right side of the page.

Application updates

Source VersionTarget VersionApplication Update
8.0.08.1.08.1.0
8.0.08.2.008.2.00
8.0.08.3.008.3.00
8.0.08.4.008.4.00
8.0.09.0.009.0.00
8.0.09.1.009.1.00
8.1.08.2.008.2.00
8.1.08.3.008.3.00
8.1.08.4.008.4.00
8.1.09.0.009.0.00
8.1.09.1.09.1.00
8.2.008.3.008.3.00
8.2.008.4.008.4.00
8.2.009.0.009.0.00
8.2.009.1.009.1.00
8.3.008.3.018.3.01
8.3.008.4.008.4.00
8.3.009.0.009.0.00
8.3.009.1.009.1.00
8.3.018.4.018.4.01
8.3.019.1.009.1.00
8.4.008.4.018.4.01
8.4.009.0.009.0.00
8.4.009.1.009.1.00
8.4.019.1.009.1.00
9.0.009.1.009.1.00

 

Platform Updates

Source VersionTarget VersionPlatform Update
8.0.08.1.08.1.0
8.0.08.2.00

Trust Store Update

8.1.0

8.2.00

8.0.08.3.00

Trust Store Update

8.1.0

8.2.00

8.3.00

8.0.08.4.00

Trust Store Update

8.1.0

8.2.00

8.3.00

8.4.00

8.0.09.0.00

Trust Store Update

8.1.0

8.2.00

8.3.00

8.4.00

9.0.00

8.0.09.1.00

Trust Store Update

8.1.0

8.2.00

8.3.00

8.4.00

9.0.00

9.1.00

8.1.08.2.008.2.00
8.1.08.3.00

8.2.00

8.3.00

8.1.08.4.00

8.2.00

8.3.00

8.4.00

8.1.09.0.00

8.2.00

8.3.00

8.4.00

9.0.00

8.1.09.1.00

8.2.00

8.3.00

8.4.00

9.0.00

9.1.00

8.2.008.3.008.3.00
8.2.008.4.00

8.3.00

8.4.00

8.2.009.0.00

8.3.00

8.4.00

9.0.00

8.2.009.1.00

8.3.00

8.4.00

9.0.00

9.1.00

8.3.008.3.018.3.01
8.3.008.4.008.4.00
8.3.009.0.00

8.4.00

9.0.00

8.3.009.1.00

8.4.00

9.0.00

9.1.00

8.3.018.4.018.4.01
8.3.019.1.00

8.4.01

9.1.00

8.4.008.4.018.4.01
8.4.009.0.009.0.00
8.4.009.1.00

9.0.00

9.1.00

8.4.019.1.00

9.1.00

9.0.009.1.009.1.00

Note: Versions 8.3.01 and 8.4.01 of the Platform Update must skip 9.0.00, as laid out in the above table.

Statistics
0 Favorited
4 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

May 15, 2018 07:45 PM

Hi Sebastian. Good catch! I'll update this to say that it is outdated now and will no longer be updated (unless of course we decide to change that again), as these are included in the upgrade prerequisites of the Gateway now.

Mar 23, 2018 04:50 AM

THis list is outdated. Can it be updated or marked as outdated?

Jun 21, 2016 12:37 PM

Hi richardb80,

 

I apologize, but I'm not sure what this comment means. Can you please elaborate or clarify?

 

Sincerely,

 

Dustin Dauncey

Support Engineer, Global Customer Success

Email: CATechnicalSupport@ca.com

Phone: +1 800 225 5224

Outside of North America - ca.com/us/worldwide.aspx

CA API Management Community: ca.com/talkapi

Jun 21, 2016 12:37 PM

Hi richardb80,

 

I apologize, but I'm not sure what this comment means. Can you please elaborate or clarify?

 

Sincerely,

 

Dustin Dauncey

Support Engineer, Global Customer Success

Email: CATechnicalSupport@ca.com

Phone: +1 800 225 5224

Outside of North America - ca.com/us/worldwide.aspx

CA API Management Community: ca.com/talkapi

Jun 20, 2016 07:28 AM

L7 map ca24fae6190ff38e93e701bb2a5ea819

 

Van: alexanderenableu

Verzonden: maandag 20 juni 2016 12:21

Aan: Richard Bovens

Onderwerp: Document marked as helpful on Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance

 

CA Communities <https://communities.ca.com/?et=watches.email.outcome>

 

 

Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance

 

alexanderenableu<https://communities.ca.com/people/alexanderenableu?et=watches.email.outcome> marked Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance<https://communities.ca.com/docs/DOC-231156367?et=watches.email.outcome> as helpful.

Jun 20, 2016 07:26 AM

Iso 68634e9cd03c8c9c10b20bf2aa5e4db0

 

Van: alexanderenableu

Verzonden: maandag 20 juni 2016 12:21

Aan: Richard Bovens

Onderwerp: Document marked as helpful on Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance

 

CA Communities <https://communities.ca.com/?et=watches.email.outcome>

 

 

Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance

 

alexanderenableu<https://communities.ca.com/people/alexanderenableu?et=watches.email.outcome> marked Patches required for upgrading the 8-series and 9-series of the CA API Gateway appliance<https://communities.ca.com/docs/DOC-231156367?et=watches.email.outcome> as helpful.

Jun 13, 2016 01:48 AM

Hi Bill,

 

Today I saw the support e-mail of our supplier. It has to do with the account setup and they are working on this so we get access again ASAP. Meanwhile, we can request updates to be sent or we can download them from the supplier.

Thanks for answering my question so quickly!

 

Regards,

Richard

Jun 10, 2016 12:04 PM

Hi Richard. Were you logged in at the time?

Jun 10, 2016 09:35 AM

This is likely an issue with how your account on CA Support Online(CSO) is setup. You can open a support case with our Customer Care team to have them look into getting that resolved.

Jun 10, 2016 01:54 AM

Hi,

 

Just followed the instructions. When I click Download center, the option Download products is grayed out for me. So I can't see if there are patches or platform updates.

Did I do something wrong here?

 

Regards,

Richard

Jun 06, 2016 03:49 PM

Hello HunterBond,

 

You can sign up the Proactive Notifications & Hypers page when signed in to the CA Support Online system. Note that if you were already receiving product announcements / upgrade notices while you were in the now-defunct Layer 7 Support Portal, then you should still be on the list to receive them since the migration to CA Support Online.

 

I hope that helps answer your question.

 

Sincerely,

 

Dustin Dauncey

Support Engineer, Global Customer Success

Email: API-Support@ca.com

Phone: +1 800 225 5224

Outside of North America - ca.com/us/worldwide.aspx

CA API Management Community: ca.com/talkapi

Jun 06, 2016 03:16 PM

How do get included on patchng notification list

Apr 01, 2016 02:57 PM

IAM-SSO,

 

The two more platform patches you are referencing have dates in the names, which means that they are Platform Security Patches (as opposed to the standard Platform Patch). Platform Security Patches are not required to be installed (from a functionality perspective) in order to upgrade your Gateway. Since the Platform Security Patches aren't required for an upgrade, we have intentionally not included them in this list.

 

Regards,

Azad

Apr 01, 2016 09:54 AM

Hello Dustin,

regarding the platform update, on the support download site, beside the "Layer7_PlatformUpdate_64bit_v9.0.00.L7P", there are two more platform patches: "Layer7_PlatformUpdate_64bit_v9.X-01-06-2016.L7P" and "Layer7_PlatformUpdate_64bit_v9.X-01-28-2016.L7P".

When upgrading/installing patches, we should install these files also? If so, can you please update the tables to include it?

 

Thank you

Regards

Mar 16, 2016 11:36 AM

Hello Dustin,

thank you for your answer. It is very explanatory.

 

Best regards

Mar 15, 2016 05:28 PM

I have added a link to this communities post to the v8.x "Upgrade CA API Gateways" topic in Docops. This is the parent topic to all the upgrade instructions, so it is as early as you can get. This information has also been retrofitted into the v8.x Release Notes, to ensure it gets the widest coverage.

 

Thanks.

Carl

Mar 14, 2016 04:08 PM

Hi Hallett_German,

 

Thank you for the feedback. We will consider making this document more visible and perhaps referenced directly in our product documentation hosted on CA DocOps.

 

When you say "earlier in the upgrade procedure", however... can you please clarify that for me? For example, what upgrade procedure were you following at the time where you feel this document should have been moved earlier in the procedure? I'm not quite sure I follow what is meant by this statement, so any clarification would be appreciated.

 

Sincerely,

 

Dustin Dauncey

Support Engineer, Global Customer Success

Email: API-Support@ca.com

Phone: +1 800 225 5224

Outside of North America - ca.com/us/worldwide.aspx

CA API Management Community: ca.com/talkapi

Mar 14, 2016 03:58 PM

Hi IAM-SSO,

 

I apologize for the delayed response. If you are going from 8.2 to 9.0.00, for example, you can do so with simply the 9.0.00 API Gateway application update, as you do not need to go from 8.2 to 8.3 to 8.4 and then to 9.0. That is why you only see one file as needed to get to 9.0.00.

 

It is a good idea, we will consider updating this to reflect the service pack versions as well such as 8.3.01.

 

No, unfortunately this type of document does not exist for OAuth / OTK, nor MAG, nor API Developer Portal. The other products have a more straight-forward upgrade path though, and are well documented in the product documentation. For example, for API Developer Portal, upgrading to v3.5 (our latest version at this moment), the instructions start at this page and continue in the sub-pages: Upgrade the API Portal to Version 3.5 - CA API Developer Portal - 3.5 - CA Technologies Documentation

 

I hope the above helps answer your questions. Please let me know if you need any further assistance.

 

Sincerely,

 

Dustin Dauncey

Support Engineer, Global Customer Success

Email: API-Support@ca.com

Phone: +1 800 225 5224

Outside of North America - ca.com/us/worldwide.aspx

CA API Management Community: ca.com/talkapi

Mar 13, 2016 11:16 AM

I am reviewing the API Gateway Docs as part of our internal APM bookclub. This Document should be more prominent and earlier in the upgrade procedure.

Mar 01, 2016 03:35 AM

Hello Dustin,

in the Application Updates table, for upgrading from 8.3 to 9.0 there is specified only one file needed to patch. Is that correct or is missing the 8.4 version?

Also, can be included the 8.3.01 version and the future service packs for 8.4 and 9.0?

 

Do you know if exists something similar that includes OAuth, MAG and API Portal and describes the compatibility between components and some quick reference for the upgrading process?

 

Thank you

Jan 12, 2016 12:39 PM

Hi AtulRaut,

 

I sincerely apologize for the delay in responding to your comment.

 

To answer the question, the order/sequence in which the patches should be applied (specific to platform updates) is the order you see above starting from the top and proceeding to the bottom. So for example, the row that has a source version of 8.2.00 and a target version of 9.0.00 has the patches in order for 8.3.00 , 8.4.00, and 9.00 -- and that is the same order it needs to be applied in. In other words, the 8.4.00 platform update / patch requires that the platform version already be at 8.3.00 prior to upgrading to 8.4.00.

 

Now, regarding both application and platform updates... the order should be platform and then application, as best practice. So in other words, if you're doing an upgrade from v8.2.00 to 9.0.00 in both platform and application, you would want to patch the platform from v8.2.00 to v9.0.00 (in sequence and meeting the prerequisites) first, and then the application from v8.2.00 up to v9.0.00 (in sequence and meeting the prerequisites) last.

 

I hope that helps explain the sequence of patching.

 

Sincerely,

 

Dustin Dauncey

Support Engineer, Global Customer Success

Email: API-Support@ca.com

Phone: +1 800 225 5224

Outside of North America - ca.com/us/worldwide.aspx

CA API Management Community: ca.com/talkapi

Jun 12, 2015 02:46 PM

Do you think it is useful to add the sequence in which these patches should be applied (Platform and then Application)? I think it would be helpful for someone who is patching for the first time. Also can we add if database upgrade is needed for any of the upgrade paths?

Related Entries and Links

No Related Resource entered.