SAP Enable Now – Streamlining the Producer install – Testing tips
?In my previous article I discussed part 2 of streamlining the Producer install, completing the refresh of the folder structure and workarea. Your takeaway should be an understanding of the installation process.
?In this article, I will cover testing tips as part of streamlining the Producer install. It builds on the two previous articles, and I suggest that you read both before continuing. Here are the links.
Testing overview
?When you are designing a workarea, proposing changes to an existing workarea, or trouble shooting problematic workareas, you may need to alternate between two or more existing configurations during the testing phase. An example of this would be comparing alternative baseline installs for Enable Now users that require different content installed.
?You could open Producer and manually pull the content down from the server, delete what is not required, and save it to the server to create a new configuration of the workarea, but if you need to revert back to the original, you will have to undo the changes following the same manual processes. This is both time consuming and prone to errors.
?Instead of doing this manually, you could create multiple configurations and switch between them as needed. This assures you that the configuration is structured properly, and it requires only a few steps to complete.
Creating multiple configuration files
?If you do not have multiple configuration files to work with, we need to discuss the process for creating them. The first step is to create a proposed workarea from scratch following the steps outlined in the two previous articles. You may skip this step if you already have a desirable workarea.
?The next step is to create a second configuration file. You do this by searching for the %localappdata% text string previously discussed. We then open the CloudWA folder, locate the configuration file and make a duplicate of it. This copy should have a meaningful name appended to it. For this example, I will append _V1 to the copy.
?Next, open Producer and it will open with the folders and content that are defined in the original configuration file. Make the structural changes by adding and deleting the local folders, not those on the server. Save this and exit Producer. This is your newly created second configuration version.
?Return to the CloudWA folder and repeat the process of copying the active configuration file. This time we will append V2 to the new copy. You now have 3 configuration files. One that is active, a copy of the active file V2 and the original _V1 file. Depending on your needs, you can create several more versions of the configuration file.
领英推荐
Switching between multiple configuration files
?With Producer closed, go to the folder containing your configuration files. Delete the original configuration file. Select the configuration file version you want to use. In this example I will select the V1 file. Make a copy of the configuration file and rename it by removing the V1. You are now ready to open Producer where it will use the structure defined by the _V1 file as the active version is identical to it.
?When you are finished using this version of the structure, you can go back to the configuration file folder and repeat the delete, copy, rename process using the _V2 file. Open Producer again and perform the assessment of the structure. When you finish, exit out of Producer. Repeat this process as many times as needed to validate your multiple configurations.
Summarizing the process
?It is important to note that each time you launch Producer it will incorporate the structure defined in the configuration file. Switching between configuration files allows you to quickly experience a different structure without having to manually rebuild it and without losing the original version.
?Your takeaway should be an understanding of how to create alternative configuration files, how to switch between them, and how Enable Now uses the configuration file. This is likely reserved for the administrator and lead content developer roles who are engaged in assessing and creating the various structural workareas.
What’s next?
?In my next article I will cover reporting objects being edited. When working amongst a group of content creators, this is an important and efficient method of tracking work in process.
If you like what I wrote please take the time to share it, as others may find it interesting, if not amusing. Let’s not be just consumers of information or share only the works of others. Your voice matters, and I’m sure you have good ideas that could help others. Try being a thought leader and not just a follower.
To those of you who take the time to read my efforts I sincerely thank you. I would be remiss if I didn’t remind you that this is a two-way conversation so put your comments in and let’s have a volley of ideas, so we all continue our intellectual growth.
Mr. Gray is a seasoned business strategist experienced in PMO stand up, digital and business transformation, process development, and best practice guidance. He has developed industry-leading methods for staff modeling, project deployment, financial performance, team onboarding, and business readiness. Mr. Gray is a problem solver at heart and a sharer of knowledge by choice. He has authored more than one hundred and fifty thought provoking articles which are all available on Linked-In.
If Mr. Gray makes you think then he considers the effort worthwhile.
Your PMI Guy can be found on LinkedIn at: https://www.dhirubhai.net/in/yourpmiguy/
Follow me on LinkedIn
And on Twitter at: https://twitter.com/YourPMIGuy