Scheduling Automatic Transport Upload – uPerform On-Premise Manuals

This section will cover the procedures related to scheduling the automatic transport upload.

Activating a Standard SAP Exit to Process an ANCILE Transport Collector

Although an ANCILE standard SAP exit is provided and is activated at installation, the actual collection of transport information is controlled by activating the collection option on the ANCILE Solutions - Change Tracking Utility.

After the transport data has been collected, a batch job that can be scheduled to run periodically, will review the data, attempt to determine which transactions may be changed, and transmit this information to uPerform provided the Activate transmit notifications option was selected. You can opt to not activate the transmission and send them manually.

NOTE:

Transmitting this information to uPerform will require information related to the location of the uPerform XAPI, the Credential ID, and a password. For more information, refer to the Managing Content manual. To enable screen change notifications when uPerform is configured to use Single Sign-On, configuration changes are required in both uPerform and Tivoli Access Manager. For more information, refer to the Administration manual.

Start the transaction using transaction code /n/RWD/chg0.
Perform one of the following:

If You Want To

Then

Automatically collect transports

Select Activate transport collection process.

Automatically transmit notifications

Select Activate transmit notifications.

Complete the following fields under uPerform API Credentials:

Field	Description
Connector location	The IP address of the server on which uPerform is installed. Example: http://[applicationserver]/xapi/uperform/transactionchange/
Credential ID	The integration name for the uPerform connection. Example: appwatcher The credential ID cannot be the same as a user ID that already exists in uPerform.
Password	Enter a password.
Password Confirmation	Re-enter the password.
Project	Enter the OID of the project that contains the documentation for your system. Example: http://[projectserver]/gm/cabinet-1.25.201

Click Save.

Editing Watch Filters Options to Specify Changes to Be Collected

Start the transaction using transaction code /n/RWD/chg0.
Click the Watch filters tab.

Perform one or more of the following:

If You Want To	Then
Display transaction changes related to a Program	Select the Program - (prog) checkbox.
Display transaction changes related to source or text	Select the Reports source/text - (rep*) checkbox.
Display transaction changes related to a screen	Select the Screen - (dynp) checkbox.
Display transaction changes related to codes	Select the Tcode - (trans) checkbox.

Optionally, perform one or more of the following:

If You Want To

Then

Automatically delete transport data after a specific timeframe

Select the Auto delete transport data after checkbox.
Specify the number of days in between auto delete.
Example: 30

Regardless of the time period specified, transport data will be deleted regardless if files have been processed for tcode changes.

Automatically delete notification data after a specific timeframe

Select the Auto delete notification data after checkbox.
Specify the number of days in between auto delete.
Example: 30

Regardless of the time period specified, notification data will be deleted regardless if files have been processed for notification.

Scheduling a Post Transport Job to Determine and Transmit Changes to uPerform

Start the transaction using transaction code /n/RWD/chg0.
Click Schedule post transport job.
Perform one or more of the following:

If You Want To

Then

Schedule the job in an SAP system with BASIS level = or > 7.30

Go to Step 12.

Schedule the job in an SAP system with BASIS level < 7.30

Go to Step 4.

As required, complete the following fields:

Field	Description
Connector location	The IP address of the server on which uPerform is installed. Example: http://[applicationserver]/xapi/uperform/transactionchange/
Credential ID	The integration name for the uPerform connection. Example: appwatcher The credential ID cannot be the same as a user ID that already exists in uPerform.
Password	Enter a password.
Password Confirmation	Re-enter the password.
Project	Enter the OID of the project that contains the documentation for your system. Example: http://[projectserver]/gm/cabinet-1.25.201

Click Continue.
Click Continue.
Click Immediately.
Click Continue.
Click Continue. Optionally, click Period to run the job periodically or click Sunday/Holiday to set restrictions.
Click Complete.

NOTE:

The batch transport job is created in the SAP system and will run at the specified period.
Go to Step 15.

Perform one or more of the following:

If You Want To	Then
Submit the job immediately for a one- time execution	Click Execute immed. Go to Step 15.
Schedule the job to run periodically	Click Schedule. Go to Step 13.

Perform one or more of the following:

If You Want To	Then
Submit the job immediately for a one-time execution	Select the start date and time. Click Schedule once. Go to Step 15.
Schedule the job to run periodically	Click Schedule periodically. Go to Step 14.

Select a period interval and then click .
The message Report /RWD/CSH_BATCH_HTTP_UPLOAD will display to confirm the job is scheduled.

Viewing Processed Data

Start the transaction using transaction code SP01.
Click Execute.
Click the checkbox next to the Spool no. you want to display.
Click Display contents.
Scroll through the messages to view the processing activity.

Working Directly With Collected Transport and Transaction Code Data

Start the transaction using transaction code /n/RWD/chg0.
Click Transports/Notifications.

Perform one or more of the following:

If You Want To	Then
View All Held transactions collected by the exit	Click All Held Transport. Click the line item you want to view. Click Details.
View all extracted transaction codes identified in the transports	Click All Extracted Tcodes. Click the line item you want to view. Click Details.
Manually send available transactions	Go to Step 4.
Reset any previously processed transport	Go to Step 7.

Click Send to uPerform.

NOTE:

If there are any available transactions, a dialog box will display showing which transports, if any, have available transactions to send to uPerform.
Select the checkbox next to the transport you want to send to uPerform.
Click Continue.
Click Request to display the transports.
Uncheck the Processed checkbox.
Click Save.
Click Continue.
Click Continue.

NOTE:

At this point, the collected transport will be in its initial state. You can then submit the batch job and re-process the transport for the transaction that can be sent to uPerform.

Creating a Backup File

NOTE:

A process transport job must be run and in the system prior to creating a backup file.

Start the transaction using transaction code /n/RWD/chg0.
Click Transports/Notification.
Click Request.
Click the checkbox next to Processed.
Select the Backup File.

Perform one or more of the following:

If You Want To	Then
Backup the file location	Enter a backup location. Click Backup.
View all extracted transaction codes identified in the transports	Click Restore. Navigate to the file location. Click Open.
Manually send available transactions	Click Delete.