Current, real data is valuable for testing, validation, and user-acceptance purposes. The content copy tool allows you to copy content from your production AMS-hosted AEM 6.x environment to a staging or development environment for such testing.
The content to copy is defined by a content set. A content set consists of a list of JCR paths that contain the mutable content to be copied from a source environment to a target environment within the same Cloud Manager program. The following paths are permitted in a content set.
We provide this tool to help you migrate your SonarQube database from one database vendor to another. For example, if you've been using your SonarQube instance with Oracle and want to migrate to PostgreSQL, the SonarQube DB Copy Tool will help. DB Copy is preferred for database migration because it does SonarQube-specific checks, ensures data consistency, and outputs meaningful logs.
Because this step is about copying data from source to target, the overall performance makes a difference. Make sure you execute this on a powerful machine that has fast network access to both database servers.
Here is an example of a copy from an Oracle to a Postgres database. Note that each parameter is on one line and there are \ (backslash) characters to continue the command. While this works on most shell command-line interpreters, it is not necessarily the case. Use only one line and remove backslashes in that case.
2008-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution-NonCommercial 3.0 United States License. SONARQUBE is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners.
I am having difficulties with using the copy tool when on move(the object is a component). It just does not do it. i can copy when click+CRTL and the buttons on top.
Am using sketchup web on Chrome (have also tried safari+deleting cookies) with OS X El captain.
Also tried changing the shortcut to others but no avail so have left it at Shift+C
The Copy Data tool eases and optimizes the process of ingesting data into a data lake, which is usually a first step in an end-to-end data integration scenario. It saves time, especially when you use the service to ingest data from a data source for the first time. Some of the benefits of using this tool are:
After you launch copy data tool, you will see two types of the tasks: one is built-in copy task and another is metadata driven copy task. The built-in copy task leads you to create a pipeline within five minutes to replicate data without learning about entities. The metadata driven copy task to ease your journey of creating parameterized pipelines and external control table in order to manage to copy large amounts of objects (for example, thousands of tables) at scale. You can see more details in metadata driven copy data.
The tool is designed with big data in mind from the start, with support for diverse data and object types. You can use it to move hundreds of folders, files, or tables. The tool supports automatic data preview, schema capture and automatic mapping, and data filtering as well.
You can preview part of the data from the selected source data store, which allows you to validate the data that is being copied. In addition, if the source data is in a text file, the Copy Data tool parses the text file to automatically detect the row and column delimiters, and schema.
The Copy Data tool monitors and learns your behavior when you are mapping columns between source and destination stores. After you pick one or a few columns from source data store, and map them to the destination schema, the Copy Data tool starts to analyze the pattern for column pairs you picked from both sides. Then, it applies the same pattern to the rest of the columns. Therefore, you see all the columns have been mapped to the destination in a way you want just after several clicks. If you are not satisfied with the choice of column mapping provided by Copy Data tool, you can ignore it and continue with manually mapping the columns. Meanwhile, the Copy Data tool constantly learns and updates the pattern, and ultimately reaches the right pattern for the column mapping you want to achieve.
When copying data from SQL Server or Azure SQL Database into Azure Synapse Analytics, if the table does not exist in the destination store, Copy Data tool supports creation of the table automatically by using the source schema.
You can filter source data to select only the data that needs to be copied to the sink data store. Filtering reduces the volume of the data to be copied to the sink data store and therefore enhances the throughput of the copy operation. Copy Data tool provides a flexible way to filter data in a relational database by using the SQL query language, or files in an Azure blob folder.
You can run the copy operation once or on a schedule (hourly, daily, and so on). These options can be used for the connectors across different environments, including on-premises, cloud, and local desktop.
A one-time copy operation enables data movement from a source to a destination only once. It applies to data of any size and any supported format. The scheduled copy allows you to copy data on a recurrence that you specify. You can use rich settings (like retry, timeout, and alerts) to configure the scheduled copy.
1. Trying to fix the issue introduced by 1.5.5 - when destination account has removed the default-consent form already, an error saying "Copy Reminder or Visibility fails for template xxx" appears. Now, as long as the end user didn't toggle the remove option, the tool won't hit the same error.
Regarding this Copy tool, does it only copy the template and layout between the accounts? or it can copy all the account settings between accounts? and can they copy between different environment? for example, can I copy the accounts between DEV env and PTE env?
This tool only copies Template and Layout, and can copy across environments. For export/import settings across accounts, OneSpan Sign introduced the out-of-the-box capability at the BackOffice since SaaS version 11.28(Release Note here, and search "export")
thanks for the information. so in current on-prem v11.25, there is no export/import setting function until v11.28. but in v11.25, it can use copy tool to copy the template and layout between the accounts across environments, correct?
When you use the tool to copy templates from a sandbox to production account, the SANDBOX watermark appeared to be on the documents. Is there anyway to remove this? Or do the layouts need to be saved to maintain the fields and the documents need to be deleted and uploaded to the template again?
When I use the file, I am receiving an error that the number of uploaded files does not match number of documents specified in the package. I have checked all the templates to the files in the folder and there is one copy of each file. If I re-use a file from one template to another, do I need to have multiple copies of the file in the folder as well?
Why would I receive this message?
before copying the layout & template, we'd like to backup the source account setting first ( or just backup the existing layout and templates) in case something goes wrong. so what do you suggest to backup the account setting?
But if you want to back up all existing templates, you can (1)in sender UI (2)create a new template, chosen the template from each of the original template (3)give this backup a different name, so that you can distinguish them when you run the tool.
basically you saying duplicate the templates/layouts, and copy the original ones when selected. actually, in our exercises, we normally copy all to the destination, otherwise, we need to let the admin know which ones need to copy (I guess in the tool, it lists the name of layout/templates to choose), right?
Yes, in the copy tool, I first queried the API Keys of all senders, then pulled templates and layouts using each individual's API Key. If you want to do the same, you need to do the same:
(1)get sender's API Key:
GET /api/account/senders/senderId/apiKey
after copying, the Owner said he can't see this layout unless he clicked "show share", then he can see it. I use API call to queried the Owner account and found the layout is in the owner's account. so do you have an idea why the owner can't see it even it's already there?
By the way, I have a suggestion for improvement, every time when I finish one copy, i can't continue to the next, i have to close the tool and re-launch it again. if can go back to step 1 after finishing 1 copy will be much easy.
Hi Duo,
Thank you for this nice tool. I've started to get error when i clicked the "invite senders" button in process 2 option 1. I am using the latest version v1.5.2
Please see the error log:
Fail to invite sender: , Reason: "messageKey":"error.internal.default","technical":"Unrecognized field \"kmsTenantId\" (Class com.silanis.esl.api.model.Account), not marked as ignorable\n at [Source: io.undertow.servlet.spec.ServletInputStreamImpl@13bfe14e; line: 1, column: 557] (through reference chain: com.silanis.esl.api.model.Sender[\"account\"]->com.silanis.esl.api.model.Account[\"kmsTenantId\"])","message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team.","code":500,"name":"Unhandled Server Error"
This was working just fine last month. I believe some api changes causing the issue.
Thanks,
Ali