Contents
|
An Update Sandbox is a copy of your existing Eloqua9 production environment which can be used to test your assets & configuration. In addition, this environment can be used to train your users to gain Eloqua10 user interface experience.
If you currently own an Eloqua9 sandbox or have one as part of your Eloqua10 update project, the process is as follows:
- Your Production environment & Sandbox environment will need to be linked (in Eloqua9)
- The replication script will run which will override your existing sandbox. This is now your Update Sandbox
- The Update Sandbox is migrated to Eloqua10 and an initial check is done by Eloqua to see which assets were impacted
- User testing is done on the Update Sandbox on existing assets & configuration
- Production is moved over to Eloqua10*
*Note that the replicated sandbox is not converted into a production environment. The two environments will remain separate from each other.
Please see below for a visualization of how the process will work:
If your sandbox is currently on Eloqua10 it will need to be downgraded to Eloqua9 prior to replication.If you currently do not have a sandbox and would like to purchase one, please reach out to your Account Director. The Account Director can request the update sandbox by submitting a Service Request with the Standard Support team.
Please keep in mind that your Update Sandbox will not create an exact replication of your production environment. See below for what will be replicated:
- Only replicates configuration & assets.
- It will replicate:
- All assets: emails, forms & landing pages, etc.
- All configuration: users, security groups, integration, programs, etc.
- It will not replicate:
- Contacts, accounts & data cards
- Reporting data
- You can manually upload up to 10,000 prospects, contacts & companies and up to 25,000 data cards
- It will replicate:
- Does my existing sandbox need to be on Eloqua9 for replication?
- Yes, replication only works if the production and sandbox environment are on the same Eloqua version.
- Is Sandbox Replication a BETA product?
- Yes, it is still being actively worked on by our Development Team. You can find out more by visiting http://topliners.eloqua.com/docs/DOC-3538& http://topliners.eloqua.com/community/know_it/blog/2012/12/21/sandbox-replication
- Since it is a BETA product, what are the risks?
- The risk for sandbox replication is minimal since we are not modifying the Production database. However, replication relies on a complex set of scripts which can cause a delay on the initial timeline provided. Your Partner agency should keep you posted on any sandbox issues through communication with our Standard Support team. Our Standard Support reps will work with other internal teams to resolve them.
- How long will it take to setup my Update Sandbox?
- Generally it will take a week to setup the environment. However, since this is still a BETA product it may take longer if your install has a significant amount of data. Please re-visit your Service Request ticket about specific timelines.
- What happens to my existing sandbox?
- When we begin the replication process it permanently deletes all existing data and configuration in your sandbox.
- What are some common areas to check in my Update Sandbox?
- We have come up with a list of areas to check in your Update Sandbox to ensure the migration went smoothly. Please see below in the “User Testing” section.
- My replicated Hypersites do not work, how can I fix that?
- Your replicated Hypersites will continue to refer to the Eloqua9 Production environment. This is a backend DNS configuration and one we cannot change. However, you can setup a test domain such as test.companyname.com and have your IT team complete the DNS configuration. This process is similar to when you setup your initial Hypersite. More information can be found here: http://topliners.eloqua.com/docs/DOC-5295.
- What if I do not create a test Hypersite?
- Without a Hypersite you cannot publish any landing pages or test your form submissions. It is highly encouraged that you setup a temporary Hypersite to ensure your forms are behaving as expected and there are no rendering issues with landing pages.
- What happens to my existing tracking scripts & data lookups?
- The tracking scripts and data lookups are going to continue referring to the production environment. This can be manually changed to reflect the Update Sandbox by generating a new set of tracking scripts.
- How do I access my Update Sandbox?
- Once the environment is ready, your Partner should send you a confirmation email. Users can login with their existing username & password but will need to change the Company Name field to reflect the sandbox. Please note that you will need Firefox.
- What happens to my Programs and Integration?
- As part of the replication, all of your existing programs and integration setup will be brought over. However, they will remain disabled and can be manually enabled.
- My integration calls are not firing, why is that?
- Replication will automatically disable your existing external calls and internal events. This is done so your Update Sandbox does not fire duplicate data over to your CRM System. They can be manually enabled in the Integration area.
- Will Insight work in my sandbox?
- Since the replication will not bring over any reporting data you cannot generate any meaningful reports in Insight.
- Can I send emails from my sandbox?
- No, the replicated sandbox is not meant to be used for email deployments. You can do test sends to your personal corporate domain and to Eloqua & Oracle domains.
- Will the changes in my sandbox carry over to production?
- No, any testing and configuration done in the sandbox will not carry over to production automatically. This also includes creating net new assets in the sandbox. The two environments are completely separate from each other post-replication.
User Testing in the Update Sandbox
To complete testing in your sandbox please refer to the Eloqua10 Update UAT Guide here: http://topliners.eloqua.com/docs/DOC-5244
We have had several customers who have successfully used sandbox replication before their update. For our customers testimonials please see below:
Kim Yeatman Thomson Reuters Director, Marketing Operations |
"Access to a replicated sandbox was critical to the success of our migration, and was the tipping point for our go/no-go decision. Having used E9 for over three years we were deeply embedded in that platform, and needed to ensure that critical lead and preference management processes would not be impacted by the upgrade. We integrated our replicated E9 sandbox with our Salesforce.com sandbox, then migrated the Eloqua sandbox to E10. This enabled us to test all our use-cases for lead and landing page management, and to ensure that any modifications recommended by Eloqua would work in our instance. We used the sandbox to scope out new email, landing page, form and campaign templates, enabling us to take advantage of these from day one post-migration. We also used it to develop and deliver pre-migration user training that helped to minimize productivity loss post-migration" |
|---|
