Activities after upgrade to a new version

Owned by CrossALM
Apr 30, 2024
3 min read

General Information

Please read the release notes (version history) to find out which bugs are fixed, which new features are provided and which manual upgrade steps are needed, if there are any.

Timing

You can install a new version into your system at any time without any risk. Of course you should do it at a time where nobody is working with the Cross Connector.

There is no need to restart the Jira app if only the SAP side got updated. Every odata call is using a new session with the new solution, if the import of the delivery transport request is successfully done including all post-activities.

Compatibility

Our versions are backward compatible: That means a newer version should work with configurations done for an older version. Sometimes new features and options are getting available. Therefore you have to adjust your configuration if you want to use these new features and options.

Our versions are connected and tested: That means if you are upgrading the SAP side, you also have to upgrade to the connected Jira version. If you are upgrading the Jira side, you also have to upgrade to the connected SAP version. If you are not upgrading the other side, there is a risk, that something is not working as expected and that you are facing strange error messages.

Reactivate or check OData Service

Usually there is no need to repeat the installation steps. However, if you are facing strange issues, you should:

/IWFND/ERROR_LOG

  1. Check for error messages in the error log.

/IWFND/MAINT_SERVICE

  1. Verify that the SICF node of the odata service /XALM/CC5_TR_SRV is still active.

  2. Verify that a valid system alias LOCAL is assigned to service /XALM/CC5_TR_SRV .

  3. /IWFND/MAINT_SERVICE → Goto → Cleanup of Model Cache → Cleanup Cache for all Models.

  4. /IWFND/MAINT_SERVICE → Service /XALM/CC5_TR_SRV → Service Implementation → Cleanup Cache. (Alternatively transaction /IWBEP/REG_SERVICE can be used to open Service Implementation.)

/IWFND/GW_CLIENT

  1. Verify that the odata service can be executed successfully. For instances you could request the meta data.