Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Before you start, contact us on the email solutions@crossalm.com to get the Transport Requests containing the additional enhancements for this process.

 

After importing the transport request you will need to activate the oData-Service that is responsible for accepting the calls coming from your Jira instance.

 

 

For this, open transaction /n/IWFND/MAINT_SERVICE and search the entry /XALM/CC5_TR_SRV

Result:

 

Now, for properly maintaining the service we have to make sure that the oData ICF node is activated and the correct system alias is maintained.

 

Activating oData ICF node

Simply selected the entry ODATA and choose Activate from the drop down

You should get the following confirmation message

When the traffic light next to the entry is green the service is active

 

Maintain System Alias

Click on Add System Alias

Create a New Entry

Create the following entry:

Service Doc. Identifier

Sap System Alias

/XALM/CC5_TR_SRV_0001

LOCAL SM

The other field are not needed

 

Validate

 

To check whether the oData-Service is working correctly, open transaction /n/IWFND/GW_CLIENT

Insert /sap/opu/odata/XALM/CC5_TR_SRV as request URI

When you hit Execute (F8) you should get a successful feedback with return code 200 from your system

When you click on Entity Sets the option REQUESTCollection has to be available

Selection the option appends it to the URI making it /sap/opu/odata/XALM/CC5_TR_SRV/REQUESTCollection

When executing this call you should receive a list of all transport requests that have been created via this service. (This list will be empty initially)

 

  • No labels