Deployment
*********************************************************************************************************************
THIS DOCUMENT IS NOT RELEASED IN MDK 3RD EDITION!!!
*********************************************************************************************************************
In this section, we will:
Migration of SyncBO Definition
The SyncBOs created in a development system needs to be imported to a production
system. Smart Synchronization provides a tool to export and import SyncBOs,
which is called SyncBO Migration Tool.
Creating Export Package for SyncBOs
For exporting SyncBO definition, twooptions are available:
- Creating a transport request (Transport action: Export)
- Creating an export file (Transport action: Download)
In this section, the second option is described.
Procedure
The following describes the steps required to generate the SyncBO definition
file:
- Start the transaction merep_mig
- Select Download for the transport action and uncheck Test run
- Enter SyncBO ID in the Selections for SyncBO name section
- Set a flag on Mapping in the SyncBO definition objects section
- (Optional) Set a flag on Exit source in the SyncBO definition objects section
if any custom logic is added to the SyncBO(s)
- Choose the Execute icon from the application bar or F8
- Assign RFC destination(s)
When importing the SyncBO definition, a similar dialog will appear to enter
the RFC destination(s) and the RFC destination(s) assigned here can be changed.
- Choose the Continue icon
- Enter a download filename
- Choose Open to execute the download
Importing SyncBO definition
For importing SyncBO definition, 2 options are available:
- Importing from a transport request (Transport action: Import)
- Importing from an export file (Transport action: Upload)
In this section, the second option is described.
Procedure
The following describes the steps required to import the SyncBO definition
file:
- Start the transaction merep_mig
- Select Upload for the transport action and uncheck Test run
- Choose the Execute icon from the application bar or F8
- Enter a upload filename
- Choose Open to execute the import
- Confirm or modify RFC destination(s)
The RFC destination(s) should be the one(s) defined in the transaction sm59.
- Choose the Continue icon
Generating SyncBOs Imported
When the SyncBOs are imported to a system, the sychronizer for each SyncBO
needs to be generated. Smart Synchronization provides a tool to generate multiple
SyncBOs at the one time. The RFC destination needs to be defined before starting
the generation.
Procedure
- Start the transaction merep_scengen
- Select all the SyncBOs imported, for example, with the prefix SAP_EXM*
- Choose the Copy icon or Enter
- Confirm results
Smart Synchronization Configurations in Production System
The following steps are typically required to set up Smart Synchronization
in a production system:
- Create necessary RFC destinations in sm59
- Import SyncBO definition (Refer to Importing SyncBO definition)
- Generate all the imported SyncBOs (Refer to Generating SyncBOs Imported)
- Creating Mobile Groups and Mobile IDs (Refer to Creating Mobile Group, Creating
Mobile ID described in Basic Operations for Synchronization Test)
- Setting and/or modifying default values and filtering criteria for the SyncBOs
if necessary (Refer to Assigning Values to “Default” Fields and
Assigning Filtering Criteria)
- Confirming that the Receiver, Sender and Handler of Smart Synchronization
are enabled in the Profile Dialog
- Enabling the SyncBOs (Refer to Enabling a SyncBO described in Basic Operations
for Synchronization Test)
- Running the Replicator for the SyncBOs (Refer to Running the Replicator
described in Basic Operations for Synchronization Test)
- Scheduling the job for the Replicator to update the Replica DB of Smart
Synchronization (Refer to Scheduling Replicator Job)
Scheduling Replicator Job
The Replicator can be scheduled to run regularly for download and timed 2-way
SyncBOs. The frequency of the scheduled job will typically depend on how often
the business objects in the backend are updated. Master data, for example, may
not be updated so frequently. In this case, the Replicator may be scheduled
to run once a week. On the other hand, some transactional data may be updated
more frequently, and thus, the Replicator may need to be run twice a day, for
example.
Procedure
The first step is to create variants for the SyncBOs:
- Start the transaction se38
- Enter the program: MEREP_REPLICATOR_START
- Choose the Execute icon or F8.
- Enter SyncBO ID
- Choose the Save icon or Ctrl + S
- Enter a variant name and description
- Choose the Save icon or Ctrl + S
- Repeat the steps 1-7 for all the SyncBOs for which the Replicator will be
run (Download and Timed 2-way SyncBOs).
The next step is to schedule the job:
- Start the transaction sm36
- Enter a Job name
- Enter the Job class: A
- Choose the Start Condition button
- Choose the Date/Time button
- Enter the Scheduled start Date and Time
- Choose the Period values button
- Choose the cycle
- Choose the Save or Ctrl + S
- Choose the Save or Ctrl + S again
- Choose the Check icon or Enter
- Choose the ABAP program button
- Enter program name: MEREP_REPLICATOR_START
- Select a Variant created in the previous steps
- Choose the Save or Ctrl + S
- Choose the Save or Ctrl + S again to release the job
- Repeat the steps 1-16 for the target SyncBOs
Application Deployment
The client application is typically downloaded automatically from an Web Application
Server when being accessed for the first time. To enable this, the application
needs to be registered and stored in the Web Application Server.
Smart Sync applications need to be uploaded
and assigned
to users in the Web Console. They will then automatically be deployed to
the respective users on next synchronization. During application deployment,
the meta-data XML file will be parsed and the required data structures be created.
This would not happen, if the application is deployed directyl to the file system
using the export functionality
of the MDK Plug-In for Eclipse.