In the past web blog we went through the overview of the KM transports where we came across KM transport categories, transport methodologies. Here we go with the link for a quick reference KM transports: Part I. As what was devised, lets stick with the flow and explore more about KM transport for config in this blog. Software development components in a project are always subject to transport from one landscape to other during its life cycle. KM is no exception. KM can be transported across landscapes by two parts namely configuration and content. Configuration would include the services like subscription, ratings, the commands that you configured if any, the layouts you have set and many more. In this web blog we would see one methodology of transporting KM configuration across landscapes. First we need system administrator previlege for any transport. After logging into the portal with an appropriate user, lets goto System administration >> System Configuration >> Knowledge Management >> Content Management. Then you would probably see a screen similar to the one below, 
Click on “Mode” and select the advanced mode. Now click on “actions” >> “Export” >> “start”. Refer following screenshot for clearifications, 
Now we have an ambiguity here. In many of the implementations chances are people would have not made many configuration changes at all. It doesn’t mean that they didn’t need those configuration changes. Obviously when portal (EP package) got shipped from SAP it is a raw product which may or may not be needed to configure according to the client’s business needs. In case if no configuration changes has been made, refer to my previous gopala.krishnan2/blog which recommends some configuration that any organization might need. It is not imperative but you might find them interesting. So at this point I have to conclude suggesting that config transport is done only if there is a config change. Having said that, I assume that some config changes have taken place and we are transporting those config objects only. In that case, whatever config changes we made it would have been only from the default path, System administration >> System Configuration >> Knowledge Management. So this is the place where you start the transport too, which you already did ( by selecting “actions” >> “Export” >> “start” which is nothing but starting the export server). After you clicked on “start” you would have seen a server icon at the top of Menu bar (see below ) which itself shows that the export server is up and running, 
Now we go individually to each of the component and select them and then add it to the export queue. For example if we have changed something in “Commands”, we go into “Commands” and then to one of the three categories (namely UI Command groups, UI Commands, UI Commands with Selection) where your modified object is and select it. Then click on “Actions” menu item again. Then click “Export “>> “Add “>> “Topic”. Clicking “Topic area” would add all of the objects in that category. Clicking “Complete configuration” would add all of the current landscapes configuration to your export package. I would suggest you to stick with select “Topic”. The same way if you made some changes with the layout set, then you have to goto “Layouts” and then go deep into the corresponding component and select that single component you changed and add it to the export packge’s list. Please refer the screenshot below for further clearifications, 
I strongly recommend that the individual component is selected rather than the whole group, because not doing so will disturb the delicacy of the whole portal. Supposing that you selected “Topic area” instead of “Topic”, then you run into the risk of selecting components that might have been played around by any of your team colleagues. (you cant blame them! They would have made a temperory change for some testing reason, but its only you who do the transport exporting it to a more refined landscape like Q or production itself!). Supposing you select “Complete Configuration”, then you run into the risk of exporting parameters that are unique for one single landscape. Typical examples are the host names like “http:host1EPX:50000irj” can be exported for some properties in the destination landscape that has host name like “http:host2EPQ:50000irj”, then global services that are supposed to be pointing to EPQ in the destination system will point to EPX which is not so correct. The screenshot shows how individual components are selected, 
The screenshot below shows how they are added to export package list, 
Please select only “Topic” until you are sure to use other options. Then select these two options as per your requirements. I don’t have any recommendation for them because it really depends on the case. 
After you are done selecting all the components, finalize it as seen below. Goto “actions” >> “export” >> “finalize”. 
Then give a name for the transport package and check if all you components are listed. Then click “OK”. 
Download the file to your local drive. 
Now you are done exporting the package. I really want to focus the import as a separate blog. So lets see it separate. ( I know I promised to have it in same blog, but you can see this long running length ! ) But before winding up here is my 2 cents, When you want to select a component in the same category, don’t type its name and search for it. Just select “ALL” for the “object per page” dropdown box. Then you can select whatever you want and add them to the export list. Refer the screenshot below, 
Click on “Mode” and select the advanced mode. Now click on “actions” >> “Export” >> “start”. Refer following screenshot for clearifications, Now we have an ambiguity here. In many of the implementations chances are people would have not made many configuration changes at all. It doesn’t mean that they didn’t need those configuration changes. Obviously when portal (EP package) got shipped from SAP it is a raw product which may or may not be needed to configure according to the client’s business needs. In case if no configuration changes has been made, refer to my previous gopala.krishnan2/blog which recommends some configuration that any organization might need. It is not imperative but you might find them interesting. So at this point I have to conclude suggesting that config transport is done only if there is a config change. Having said that, I assume that some config changes have taken place and we are transporting those config objects only. In that case, whatever config changes we made it would have been only from the default path, System administration >> System Configuration >> Knowledge Management. So this is the place where you start the transport too, which you already did ( by selecting “actions” >> “Export” >> “start” which is nothing but starting the export server). After you clicked on “start” you would have seen a server icon at the top of Menu bar (see below ) which itself shows that the export server is up and running, Now we go individually to each of the component and select them and then add it to the export queue. For example if we have changed something in “Commands”, we go into “Commands” and then to one of the three categories (namely UI Command groups, UI Commands, UI Commands with Selection) where your modified object is and select it. Then click on “Actions” menu item again. Then click “Export “>> “Add “>> “Topic”. Clicking “Topic area” would add all of the objects in that category. Clicking “Complete configuration” would add all of the current landscapes configuration to your export package. I would suggest you to stick with select “Topic”. The same way if you made some changes with the layout set, then you have to goto “Layouts” and then go deep into the corresponding component and select that single component you changed and add it to the export packge’s list. Please refer the screenshot below for further clearifications, I strongly recommend that the individual component is selected rather than the whole group, because not doing so will disturb the delicacy of the whole portal. Supposing that you selected “Topic area” instead of “Topic”, then you run into the risk of selecting components that might have been played around by any of your team colleagues. (you cant blame them! They would have made a temperory change for some testing reason, but its only you who do the transport exporting it to a more refined landscape like Q or production itself!). Supposing you select “Complete Configuration”, then you run into the risk of exporting parameters that are unique for one single landscape. Typical examples are the host names like “http:host1EPX:50000irj” can be exported for some properties in the destination landscape that has host name like “http:host2EPQ:50000irj”, then global services that are supposed to be pointing to EPQ in the destination system will point to EPX which is not so correct. The screenshot shows how individual components are selected, The screenshot below shows how they are added to export package list, Please select only “Topic” until you are sure to use other options. Then select these two options as per your requirements. I don’t have any recommendation for them because it really depends on the case. After you are done selecting all the components, finalize it as seen below. Goto “actions” >> “export” >> “finalize”. Then give a name for the transport package and check if all you components are listed. Then click “OK”. Download the file to your local drive. Now you are done exporting the package. I really want to focus the import as a separate blog. So lets see it separate. ( I know I promised to have it in same blog, but you can see this long running length ! ) But before winding up here is my 2 cents, When you want to select a component in the same category, don’t type its name and search for it. Just select “ALL” for the “object per page” dropdown box. Then you can select whatever you want and add them to the export list. Refer the screenshot below, - SAP Managed Tags:
6 Comments
