Skip to content
Snippets Groups Projects
Commit 50c910fd authored by SAM CARPENTER's avatar SAM CARPENTER
Browse files

Working with Test and Prod first docs pass

parent be1d42e5
No related branches found
No related tags found
1 merge request!68Working in Multiple Organizations
...@@ -6,7 +6,7 @@ Here are some recommended best practices for designing and working with integrat ...@@ -6,7 +6,7 @@ Here are some recommended best practices for designing and working with integrat
* [Naming Conventions](docs/best-practices/naming.md) * [Naming Conventions](docs/best-practices/naming.md)
* [AWS S3 as a Flat file alternative](docs/best-practices/flat-file-alternative.md) * [AWS S3 as a Flat file alternative](docs/best-practices/flat-file-alternative.md)
* [Cloud Data Integration (CDI) vs. Cloud Application Integration (CAI)](docs/best-practices/cai-vs-cdi.md) * [Cloud Data Integration (CDI) vs. Cloud Application Integration (CAI)](docs/best-practices/cai-vs-cdi.md)
* [Migrating Assets between Organizations](docs/best-practices/asset-migration.md) * [Working With the Test and Prod IICS Orgs](docs/best-practices/multiple-orgs.md)
* [Email Alerting](docs/best-practices/email-alerting.md) * [Email Alerting](docs/best-practices/email-alerting.md)
* [Firewall Expectations](docs/best-practices/firewallexpectation.md) * [Firewall Expectations](docs/best-practices/firewallexpectation.md)
* [SSH / SFTP Authentication](docs/best-practices/SSH_SFTP_auth.md) * [SSH / SFTP Authentication](docs/best-practices/SSH_SFTP_auth.md)
# Asset Migration # Working in Multiple Organizations
The UW Madison IICS instance has two "orgs", Test (representing experimental assets and pieces of integrations that are still in production) and Prod (representing the assets used for active production integrations). Keeping this distinction is a responsibility we share with the Integrators that use IICS, and this page will contain all relevant information on what you should do to maintain the purpose of each org.
## Building Integrations in Test
When building an Integration's initial assets in IICS, it should always be built in Test first. This will make sure that assets representing the more experimental and exploratory parts of development aren't making the Prod org unintuitive to navigate and maintain.
Once an Integration's functionality has been confirmed, it can freely be moved to Production.
## Asset Migration
When moving IICS assets from one org to another (most commonly from Test to Production), there are several methods that can be used, each described below. When moving IICS assets from one org to another (most commonly from Test to Production), there are several methods that can be used, each described below.
## Import and Export ### Import and Export
IICS has built in functionality for the export and import of assets between organizations. Please refer to the [Informatica Knowledge Base Article](https://knowledge.informatica.com/s/article/523654?language=en_US) on the subject. IICS has built in functionality for the export and import of assets between organizations. Please refer to the [Informatica Knowledge Base Article](https://knowledge.informatica.com/s/article/523654?language=en_US) on the subject.
## IICS Assets Tool ### IICS Assets Tool
Enterprise Integration has created a tool to synchronize assets between Test and Production, located at [This Repository](https://git.doit.wisc.edu/interop/iics/iics-assets/-/tree/master). Please contact the DoIT Integration Team at [integration-platform@doit.wisc.edu](mailto:integration-platform@doit.wisc.edu) if you would like to access it. Enterprise Integration has created a tool to synchronize assets between Test and Production, located at [This Repository](https://git.doit.wisc.edu/interop/iics/iics-assets/-/tree/master). Please contact the DoIT Integration Team at [integration-platform@doit.wisc.edu](mailto:integration-platform@doit.wisc.edu) if you would like to access it.
## Editing Production Integrations
Once an Integration has been moved to Production, that does not necessarily mean it has been completed for good. A combination of maintenace, unforseen bugs, and new requirements may result in an Integration and its assets requiring edits even after its listed completion.
In this case, you should do all required edits on the assets within the Test Org first, before mirroring these changes in Prod (either through a manual export or by manually editing the assets to match).
If this is unviable, then at minimum the user should create a copy of the asset they wish to edit before making any edits, as to ensure the original remains in the case of any errors being introduced in the edits.
# Logging Into IICS # Logging Into IICS
Use these links to log into the shared IICS orgs. Use these links to log into the Shared IICS Orgs.
IICS uses NetID Login for authentication. IICS uses NetID Login for authentication.
Test IICS uses the NetID Login QA environment, which is connected to production credentials. Test IICS uses the NetID Login QA environment, which is connected to production credentials.
...@@ -24,3 +24,7 @@ Before a user can log in, they must be added to IICS. ...@@ -24,3 +24,7 @@ Before a user can log in, they must be added to IICS.
For a guide on requesting access to IICS for your business unit, refer to our [Onboarding Guide](on-boarding-to-iics.md). For a guide on requesting access to IICS for your business unit, refer to our [Onboarding Guide](on-boarding-to-iics.md).
For a guide on provisioning access to IICS to members of your business unit, refer to our [Manifest User Documentation](manifest-users.md) For a guide on provisioning access to IICS to members of your business unit, refer to our [Manifest User Documentation](manifest-users.md)
## Test or Prod?
If deciding which Org to work with for your current project, reference our documentation on [Working With the Test and Prod IICS Orgs](docs/best-practices/multiple-orgs.md).
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment