As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
One of my team members has used iWay for many years, and writes all of our education curriculum for the product. He offers the following in response to your question. Maybe this will get you pointed in the right direction.
The Migration of the repository specifically the Service Providers they created for an application can be migrated a couple of ways. First, if they created an iWay Integrated Application where the Service Provider is being used, then the Test Application can be migrated to a Prod environment by creating a Prod Template under Management Applications. Then they can deploy the application to the Prod template which has the IP address and Port number assigned to the template. I would assume they are migrating more components then just the Service Provider. Also, for the future, the iWay Server Repository is giving way to the iWay Integrated Applications and the registry will not be emphasized. Another way would be to migrate just the individual components to a Production environment. Under the Tools section of the iWay Web Console they can select Archive along the left, this will allow you to create a zip file which can be copied to the production environment and then imported into the Prod server.
One of my team members has used iWay for many years, and writes all of our education curriculum for the product. He offers the following in response to your question. Maybe this will get you pointed in the right direction.
The Migration of the repository specifically the Service Providers they created for an application can be migrated a couple of ways. First, if they created an iWay Integrated Application where the Service Provider is being used, then the Test Application can be migrated to a Prod environment by creating a Prod Template under Management Applications. Then they can deploy the application to the Prod template which has the IP address and Port number assigned to the template. I would assume they are migrating more components then just the Service Provider. Also, for the future, the iWay Server Repository is giving way to the iWay Integrated Applications and the registry will not be emphasized. Another way would be to migrate just the individual components to a Production environment. Under the Tools section of the iWay Web Console they can select Archive along the left, this will allow you to create a zip file which can be copied to the production environment and then imported into the Prod server.
Many Thanks!
Btw, I have another question, as to 'Data Store Type'(Server->Providers->Services Provider),it's Oracle instead of default File System, How to migrate the data that was stored in database from Test dev to Prod env?
.
1) Version: iWay 7.0.2 (iWay Integration Suite) 2) Platform: Linux