Automatic Deploying of Portal Configuration from Staging to Production Environment

Hello,
I'm anlyzing the opportunituy to write an automatic procedure that synchronize
our WebLogic Portal production environment with the staging one. These two environments
are physically separated.
I have found the BEA Propagation Tool. However it seems that is not possible to
define a procedure that is really totally automatic.
Firts of all, it is necessary to hava an manual operator that selects the objects
that have to be propagated and after starts the propagation process.
Besides it is necessary to have database connections beetween the progation tool
and both the environments.
What I'm looking for is a solution that
1. analyze the staging environment
2. export some files that contain both code, configuration and data (code, LDAP
and DB data)
3. import these files into the second enviroment
has someone deal with this problem?
Thans in advance
Ciao

Manish,
to answer your questions -
1. You can find the exact date and time for these refreshes/maintenance schedule on your production pod. Just go to 'Training & Support' in your production. There will be a calendar in which you can see the maintenance schedule. The details are quite accurate. to be sure of the time I would suggest you get in touch with the Service/Support rep at Oracle.
2 & 3) Oracle CRM On Demand provides a Migration Tool that can be used to migrate configuration changes from on POD to another. This can be between Staging --> Production and vice versa. Although, I would recommend that you go through the migration tool bookshelf and understand in detail the use of this tool. There are limited configurations that can be migrated. So it would be wise to create a plan based on what changes you are looking to migrate.
Note: Reports are copied on the Staging after the refresh only from Prod to Staging. This does not happen from Staging to Production. Reports will have to be created in Production and will be copied on Staging on a Quarterly basis (Check your refresh schedule)
4) You can use the migration tool to migrate configuration changes from a live environment into another instance.
The migration tool can be downloaded from:
Admin --> Import and Export Tools -->Oracle Migration Tool On Demand
You can download the Migration Tool Bookshelf here:
http://docs.oracle.com/cd/E22393_01/books/OnDemMigrTool.pdf
Thanks,
Royston

Similar Messages

Deployment of upgraded site from staging to production - error when trying to access "Content and Structure"

Hi,
We recently upgraded a site from SP 2010 to SP 2013. For moving to production, I copied over the content database to production and used the following command to to make the content database accessible in production:
Mount-SPContentDatabase -Name 'WSS_Content_SSBC' -WebApplication 'https://biprod.bljc.com'
I then change the host name of the site from staging to production host name using
$site = Get-SPSite https://stagingsite.companyname.com
$site.Rename("https://prodsite.companyname.com")
The site loads and I can see my content. But when I try to use the "Content And structure" link under "Site Settings" --> "Site administration"
I receive the following errror:
Sorry, something went wrong An unexpected error has occurred.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 3fbfcd9c-7185-10a2-6d19-8570d7f15319
Date and Time: 11/19/2014 3:38:31 PM
IN THE ULS LOG, THIS IS ONE OF THE ERRORS:
Application error when access /_layouts/15/sitemanager.aspx, Error=Object reference not set to an instance of an object.
at Microsoft.SharePoint.Publishing.Internal.WebControls.ObjectSerializer.DeleteAllowed(Boolean checkPermissions)
at Microsoft.SharePoint.Publishing.Internal.WebControls.SmtButtonField.FormatDataValue(Object dataTextValue, Boolean encode)
at System.Web.UI.WebControls.BoundField.OnDataBindField(Object sender, EventArgs e)
at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)
at System.Web.UI.Control.DataBindChildren()
at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)
at System.Web.UI.WebControls.GridView.CreateRow(Int32 rowIndex, Int32 dataSourceIndex, DataControlRowType rowType, DataControlRowState rowState, Boolean dataBind, Object dataItem, DataControlField[] fields, TableRowCollection rows, PagedDataSource pagedDataSource)
at System.Web.UI.WebControls.GridView.CreateChildControls(IEnumerable dataSource, Boolean dataBinding)
at Microsoft.SharePoint.WebControls.SPGridView.CreateChildControls(IEnumerable dataSource, Boolean dataBinding)
at System.Web.UI.WebControls.CompositeDataBoundControl.PerformDataBinding(IEnumerable data)
at System.Web.UI.WebControls.GridView.PerformDataBinding(IEnumerable data)
at System.Web.UI.WebControls.DataBoundControl.OnDataSourceViewSelectCallback(IEnumerable data)
at System.Web.UI.WebControls.DataBoundControl.PerformSelect()
at System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound()
at System.Web.UI.WebControls.GridView.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
BTW, don't know if this applies but production is load balanced and staging is not.
Thansk,
Sherazad
Sherazad

Hi Sherazad,
As the Content and Structure is enabled by the SharePoint Publishing feature, I recommend to deactivate and re-activate the publishing feature with the command below to see if the issue still occurs:
Disable-SPFeature –identity Publishing -URL <sitecollection url>
Enable-SPFeature -Identity Publishing -url <sitecollection url> -Force
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

What is the best practice to deploy the SharePoint site from test to production environment?

We are beginning to start a new SharePoint 2010 and 2013 development projects, soon developing new features, lists, workflows, customizations to the SharePoint site, customization to list forms and would like to put good practice (that will help in deployment)
in place before going ahead with development.
What is the best way to go about deploying my site from Development to Production?
I am using Visual Studio 2012 and also have Designer 2013...
I have already read that this can be done through powershell, also through visual studio and also via designer. But at this point I am confused as to which are best practices specifically for lists, configurations; workflows; site customizations; Visual studio
development features; customization to list forms etc. You can also provide me reference to links/ebook covering this topic.
Thanks in advance for any help.

Hi Nachiket,
You can follow below approach where the environments has been built in similar fashion
http://thesharepointfarm.com/sharepoint-test-environments/
if you have less data then you can use http://spdeploymentwizard.codeplex.com/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/b0bdb2ec-4005-441a-a233-7194e4fef7f7/best-way-to-replicate-production-sitecolletion-to-test-environment?forum=sharepointadminprevious
For custom solutions like workflows etc you can always build the WSP packages and deploy across the environments using powershell scripts.
Hope this helps.
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful
Hi, can you answer me specifically with regards to the foll:-
lists
configurations
workflows
site customizations like changes to css/masterpage
Visual studio webparts
customization to list forms
Thanks.

Promote Endeca Configurations from stgaing to Production

How to promote the Search Configuration xmls(Rules, keyword Redirects, Thesaurus etc) from staging to production? Emgr_Update doesn't seem to help in 3.1.2 version, one of the documentations says its no longer public.
Basically we want the similar behaviour as 'get_ws_settings' in Oracle Endeca Commerce, Tools and Frameworks 3.1.2(workbench version, no Experience Manager).
Please help. Thanks

Have you looked at the Configuration Migration Utility? That allows you to create a zip file and basically package the workflow definition and move it from content server to content server.

OWB propagation from development to production environment

Our department is in need to implement overall security around our production data warehouse.
One issue that seems to bother our management is having only one OWB Designer where developers would have to be responsible enough to use snapshots and export mappings to mdl files. Management would like to have development and production OWB Designer Repository where production designer would always be in sync with what is deployed in prd database. Also prd OWB Designer Repository would be like a source safe so we have to always get a mapping from prd designer move it dev designer and when done propagate changes back to prd designer and then deploy to prd database.
Would this be a good approach?
Any input on how to handle propagation from development to production environment, and if you are aware of "best practices" when it comes to OWB environment is appreciated.
Best Regards,
Vlasta

Hi,
Copy whole catalog and rpd from dev to prob.
If you want to copy specific report go to OracleBIData\web\catalog\samplesales\root\shared\sample+sales(group folder name)
You can copy reports under folders and dashboards in _portal in Sample sales group folder...both file and .atr file.But you may miss security applied on those dashboards.
http://www.rittmanmead.com/2008/04/28/migration-obiee-projects-between-dev-and-prod-environments/
Best practice is to copy whole catalog and rpd (or) Copy shared and system folders and their .atr files from OracleBIData\web\catalog\samplesales\root so that you will not miss security and you will not over ride users folders which may contain some data created by them.
Thanks,
Srikanth

Configuring SharePoint Apps in Production Environment

SharePoint 2013 Environment. We are trying to configure SharePoint APPS in production environment. It is a medium server farm with two W.F.E's load balanced.
We have the following two DNS entires with two different wildcards pointing to the SharePoint FQDN.
contoso.com
contosoapps.com
Since we are planning to use https, In the DNS we have assigned a random ip address to just the apps domain. Created a new web application with no host header and assigned this IPAddress to this web application by changing the binding (for both http and
https) on both the servers.
When I click on the app, the redirect does not work and displays page not found error. Any help?
V

You said you created a new web app with no host header. Did you also create a root level site collection in the web app? You don't actually use the site collection but it needs to be there. Also make sure that https is the default zone
on that web app. Apps normally only use the default zone for redirecting to the address and if you are using https it won't work unless that is the default zone.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

No automatic deployment for Portal Application Standalone DC?

Hi Experts,
     I created a Portal Application Standalone DC under NWDI track.
     I checked in the code and activate my request, the log showed that this DC had beed sucessfully built. BUT, I can not find this portal application had beed deployed. it seems that EP DC can not be deployed automatically
    I searched SDN and there are some topics about this problem, it seems that EP DC can not be deployed automatically, we need to deploy the DC manually, is it right?
   Thanks!
segement of my build log:
[pppacker] WARNING: Could not determine correct package of package folder for entity (portalapplication-api/Class, src.api/)
[pppacker] Packed   0 files for entity (portalapplication-api/Class, src.api/)
[pppacker] Packed   3 files for entity (portalapplication-core/Class, src.core/)
     [timer] Portal Application libraries packaging finished in 0.389 seconds
createApplication:
      [echo] create PAR..
       [jar] Building jar: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/t/80B8A4CDC19F36C272AD330774CF8FF0/com.hcm.isr.newtemplate.par
createPublicParts:
      [echo] Public Part: API
[pppacker] Packing public part 'API'
[pppacker] Packed   0 files for entity Portal API (Portal API)
[pppacker] Packed 1 entity for public part 'API'
     [timer] Public part packaging finished in 0.114 seconds
createDeployArchive:
      [echo] Creating portalapp-dd.xml
       [cda] Preparing archive for deploy unit "default"
       [cda]   deployment type: "J2EE"
       [cda]   explicit modules:
       [cda]     /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/t/80B8A4CDC19F36C272AD330774CF8FF0/com.hcm.isr.newtemplate.par
       [cda]
       [cda] Creating Ant build file: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/DCs/test/isrformtemp/_comp/gen/default/logs/buildDeployArchive.xml
       [cda]
       [cda]
       [cda] Creating descriptor META-INF/application.xml ...
       [cda]
       [cda] Creating descriptor META-INF/application-j2ee-engine.xml ...
       [cda] Adding module "com.hcm.isr.newtemplate.par" with container type "PortalRuntimeContainer".
       [cda]
       [cda] Collecting modules...
       [cda] Adding module 'com.hcm.isr.newtemplate.par' from current development component
       [cda] Ant build file creation finished in 0.119 seconds
packDeployArchive:
[srcpacker] Creating source archive
[srcpacker] No sources available for packing, no archive will be created.
     [timer] Source archive creation finished in 0.008 seconds
    [dcinfo] Creating deploy archive info
    [jarsap] Info: JarSAP version 20060908.1630
    [jarsap] Info: JarSAPProcessing version 20070423.1630 / JarSL version 20070906.1830
    [jarsap] Building: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/DCs/test/isrformtemp/_comp/gen/default/deploy/test~isrformtemp.sda with compression
     [timer] JarSAP finished in 0.461 seconds

The Standalone DC has a deployable result (opposed to the Module DC) and should thus be deployed when an activity is successfully activated. Is automatic deployment perhaps disabled?

Coping Portal objects from Test to production on different Domains

I want to know if anyone besides my company uses separate domain environments to do development, QA, and production. How did you get around the object owner issues that come from this level of security. Did you have to Export OID objects from one environment, and import them into the other environments to get a common GUID? Do you use a common user to do development? I would like to hear some common/best practice advise if you have any.
For those that want to understand the issues here is a little example:
For this example, I am going to call my company Acme (I like this name). Acme uses a Sneaker method of security (Sneaker method means - To move data from one level to another, you must put in on a diskette, tape, or CD and put your sneakers on the floor and walk it to another location to install it.). While this is the most secure method out there to day, it makes working in development EXTREMELY difficult. Completely isolated environments require special concerns. I wanted to know if anyone out there does this now, and how they manage these issues.
Domains:
www.Acme.com
www.QAAcme.com
www.DevAcme.com
When you do development on your site you login as a portal developer JSmith, or KJones, of BRight on the www.devacme.com domain. You build your Portal objects and custom stuff. Now you want to move it to QA, so they can test it and promote it to Production. You build your transport sets. You export using your UNIX script and get your file. You burn the file and the UNIX script to CD.
You then take the CD to the www.QAAcme.com domain Portal server and login to that system as Oracle / OrcAdmin (God mode). You run the Import script as you normally would. <Error> This doesn't work completely because your user Jsmith is different on this domain and doesn't carry the same GUID in OID. While privileges and spelling are identical, the GUID's in OID differ and the domain names dont match. (Problem - Separate domains and OID identities - objects without matching owner GUID's will not import.)
When you check your stuff you realize that some or most of your work is missing, and all of the security that you placed on the objects is not working correctly either. Because domains are different, any OID users which you assigned permissions to are now not working at all. You will have to redo all the permissions work on this domain just like you did on the other domain. (Problem - there is no easy way to change domain names associated to OID users or group accounts, even if the names are EXACTLY the same. Permissions do not move over for users so assigning item level security is a waist of time since you will have to manually do all that work over again.)
To correct then problems above, you go and export OID user objects like OrclAdmin, IAS_Admin, and a few others. You import these identities on each domain. Now what? Do you give developers 1 identity to do their work? Pass out the Admin passwords on Dev to all the developers to do as they please? Do you build a Dev User for each Developer you have and manage those ID's outside of your normal routine?
This should draw a somewhat clear picture. There are more issues besides these. I left those out of this talk for now.
If you have questions please let me know. I would like to hear input on this. Right now, I don't have any easy solutions, just a lot of extra work. Thank you in advance for any input.
Frank

Hi Frank,
A very interesting question, which I never tried nor seen. Anyway, maybe I can try to give you a hand...
I believe the major problem doesn't seem to be the GUID but rather the privileges of the users / groups within the Portal. I'm assuming that you really want that the users and groups privileges be assigned to the three Portals, 'cause you wanna test them or something like that... otherwise it would be a lot easier to assign them only to the Production machine - also what the Portal documentation encourages you to do (and never take them with the Portal Export / Import... ie, the Portal ACLs).
In overview, what I think it might work, would be something like:-
1. Export all the OID users / groups to LDIF files.
2. Change the domains in the LDIF files to the Target Portal.
3. Import all the OID users / groups to the Target Portal.
4. Export with the Portal Export to a Transport Set.
5. Export the Transport Set to a DMP.
6. Import the DMP.
7. Backup the Portal Target at this stage - ALWAYS!
8. Before merging the DMP file the WWUTL_SEC_TX_PERSON$ and WWUTL_SEC_TX_GROUP$ tables need to be changed - DN (security is taking IDs of the users/groups internally to the Portal - so this should be fine).
9. Merge the Transport Set within the Portal UI.
Till point 8 it should be easy to be done... and you may check the Portal Configuration Guide over the 10.4.8 Migrating Users and Groups - http://download.oracle.com/docs/cd/B14099_19/portal.1014/b19305/cg_imex.htm
On step 8 do something like the following:-
-- groups (dn)
update WWUTL_SEC_TX_GROUP$
set dn=replace( dn, 'dc=dev_domain,dc=com', 'dc=prod_domain,dc=com' )
update WWUTL_SEC_TX_GROUP$
set dn_hash = wwsec_api_private.get_dn_hash( dn )
-- users (dn)
update WWUTL_SEC_TX_PERSON$
set dn=replace( dn, 'dc=dev_domain,dc=com', 'dc=prod_domain,dc=com' )
update WWUTL_SEC_TX_PERSON$
set dn_hash = wwsec_api_private.get_dn_hash( dn)
If you do have the opportunity to test this, I'd be much appreciated in knowing whether you've achieved to get this sorted out. And even if there is something I may be missing then you may come back with your questions as I'll try to answer them to my best knowledge.
Alternatively, you can use the cloning notes within the Metalink website, what they do is a schema database export / import and there it IDs with be there. The only downside is that the export / import will do everything and Portal Export / Import is more flexible, ie, you may not be interested in bringging the whole Portal, but just a couple of pages or Page Groups.
I hope it helps...
Cheers,
Pedro.
PS - I hope all the above makes sense, but if not, just let me know (or detail me what do you want where I've failed to understand you).

Deploying jsp into testing/staging/developement/production environment

Hi,
I have a jsp, say header.jsp. It has,say 2links. All these links have different URL's based on the environment this jsp is deployed.
Snippet of JSP deployed for Test enviroment:
test_env=hostname:portnumber
contextroot=webappln
        <TD><A href="https://test_env/webappln/querystring">products</A></TD>
        <TD><A href="https://test_env/webappln/querystring">services</A></TD>
        prod_env=hostname:portnumber
contextroot=webappln
Snippet of JSP deployed for Production enviroment:
        <TD><A href="https://prod_env/webappln/querystring">products</A></TD>
        <TD><A href="https://prod_env/webappln/querystring">services</A></TD>
        Problem: For system testing, we need to deploy the code in test/staging and developement servers before it goes into production. Right now i have only one JSP. If i follow my lame procedure, i have to create 3 JSP's for each environement and deploy it in three diff env.Is there a better way?. How to eliminate the duplicate and redundant code in jsp. If the URL's change, need to change at 3 places.Its a big maintenece mess too.
Insted of making three different jsp's for each environment, i want to use single jsp and dynamically figure out the enviroment and generate the urls appropriately. That way we need to maintain only one JSP. No matter where its deployed(test/stage/dev) the URL's are dynamically generated.
Snippet of JSP which dynamically generate web resource URL's based on the Env
        //Determine the environment type
        //Generate URL's with proper hostname, port # and context root and set place holder
       <TD><A href="https://{place holder}/querystring">products</A></TD>
       <TD><A href="https://{place holder}/querystring">services</A></TD>
        Any pointers of how to implement the above case. Any help greatly appreciated.
Thanks,
DHM

Check the action part of the html form tag. On problem I see is in the dev environment you had file.jsp under /jsp but in the production you have it under /dir. This could just be a typo.

Deployment from DEV to Production environment

Hi,
What are the best possible ways to deploy the visual web parts and Pages from development environment to Production environment.
As I am very much new to Sharepoint, I would like to have the safest methods to do the deployment into production. Please also suggest the prerequisites.
I have a solution with number of visual web parts in the development environment which is working fine. Need to move the Visual web parts to production (Existing site). So please suggest the safest methods.
Thanks and Regards,
Satish
Sathiish Reddy

Hi Satish,
From your description, my understanding is that you want to deploy your solution from development environment to production environment with a safest method.
These links below about moving content from environment to another environment could be helpful to you:
SharePoint 2013 Dev/Test/Production environment - Moving content
http://sharepoint.stackexchange.com/questions/78483/sharepoint-2013-dev-test-production-environment-moving-content
How to deploy webpart on production (not debugging) server?
http://sharepoint.stackexchange.com/questions/17779/how-to-deploy-webpart-on-production-not-debugging-server
you could also have a look at this link below about SharePoint Content Deployment Wizard:
How do you deploy your SharePoint solutions?
http://stackoverflow.com/questions/9543/how-do-you-deploy-your-sharepoint-solutions
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Migrating Trading Partner from test to Production environment

Hi,
My Production environment has configuration for two trading partner.
I need to migrate one more trading partner from test environment to (the existing) production environment.
I see Agreement level export, TP level export, Config level export options in Oracle B2B.
Can you please suggests as to which is the fastest and most accurate way to migrate new trading partner configuration?
Regards,
Ravi Shah

There is nothing as preferred option. However you can keep few things in mind.
1. Agreement Export - Preferred option , if you would like to export only specific Trading Partner and Agreement details.
2. Repository Export - For full repository export.
3. Trading Partner Export - This option do not keep any TP in mind while taking the export, hence you may not information about Delivery channel and Agreement. This provides information about Trading partner profiles and Supported Document defition of the trading partner.
Let me know.

Migration from development to production environment for SAP Netweaver BI

All,
When I created a SAP Netweaver BI connection using BeX query in BW development environment, the system is defaulted to the BW development environment. Since the system textbox can't be modified to use a variable to point to production environment, can you share how you migrate your SWF file to production environment and ensure that it points to the BeX production query?
Thanks for sharing ....

After some more searching, I found this link: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f005a4ca-d4fd-2c10-adb8-8ec24383cb97

Configuration Tasks in a Production Environment

Do I have to configure SSL for Oracle Apps ? Use Oracle Wallet Manager to do so?
Also do we have to generate Server ids for security purpose in a production environment ?
These steps are stated as an initial task after installing Oracle Apps ?
Is there a document for Post Install Tasks after installation of EBS 12 ?
Thanks
RK

Refer to the following note to configure SSL in R12.
Note: 376700.1 - Enabling SSL in Release 12
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=376700.1
Is there a document for Post Install Tasks after installation of EBS 12 ?Refer to the installation manual and the release note Metalink note. You can also apply all recommended patches (Check Patches & Updates tab in Metalink for more details).

Does Node UUID get propagated from Staging to Production

Hi,
We have the following requirement -
We have a folder which contains list of articles in Content Repository.
The requirement is to select the articles from the folder, and display it in a certain order.
Preferred solution is XML based, where we just specify the list of items in the order in which they are to appear.
We did think of a solution where, we will list down all the UID of the nodes that should appear in the portlet in the same order in XML. And in the JSP retrieve the node based on the UUID and display all its relevant properties.
However I just had one concern on this. The custom will always manipulate the XML on Staging and then propagate onto production. So in that case, the Node UUID that is obtained from Admin Console in Staging - Once propagated does it remain same?
So will the Staging XML with Staging values of NODE UID's have tp be manipulated to point to Production UID's or
Does the UUID value in staging get propagated to PRODUCTION. SO that the same XML can be used across. Or is a new SET of UID's are created for PROD env.

Hi Deepak,
Thanks for your inputs.
You mentioned that we create a property in the content type that specifies the order.
If I understand it clearly, if we create 2 properties 1. to-be-published (boolean) and 2. posted-date
and instruct the person doing content management that
1. Select the items using the to-be-published property (Content selector will select all nodes on the basis of this property)
2. The items will be sorted on the basis of posted-date (Descending order)
Pls. confirm, if this can be the approach.
Alternatively,
As end user was insisting a XML based approach, how about creating a property - Post-Id (User will have to specify a unique ID) and in the XML just specify the ID. But what I dont get here is, how will the nodes get retrieved in first place.
Thanks,
Lilly

Transport ALE Configuration from Development to Production System

Hello All,
We have created ALE-IDOC scenario in the development system and its working fine. Now we want to transport it to the Production / Quality system. How can we transport the settings like logical systems, port definition, partner profiles, distribution model , RFC destinations from one system to another system??
Because the client numbers are different for development , quality and production systems.. Do we need to transport the logical system and client assignment using STMS or create directly in the target system??
Thanx in advance...

The issue with transporting the ALE distribution model is that the source and target logical system names change between the dev, test and prod environments.
Assume an ECC6 and PI landscape with dev/test/prod called E6D/E6T/E6P and PID/PIT/PIP with all systems using client 100. By default (SAP recommendation) the logical system name for E6D client 100 is E6DCLNT100 and its PI partner in the dev landscape will be PID client 100 with logical system name PIDCLNT100. In test the logical system names will be E6TCLNT100 and PITCLNT100 and in prod E6PCLNT100/PIPCLNT100.
So, when a distribution model is set up in dev with a source system of E6DCLNT100 sending messages to a target system PIDCLNT100 everything works nicely. This assumes that the PIDCLNT100 logical system partner in WE20/WE21 is mapped to a port which maps to an RFC destination pointing to client 100 of PID.
When this model is transported to the test system it won't work because the logical system names are wrong.
It is possible to create a logical system name called PISERVER in SALE and then map that, via WE20/WE21 to point to the corresponding PI instance. Thus in E6D, WE21 would map logical system PISERVER to the RFC destination for PIDCLNT100 but in E6T the mapping would link to RFC destination PITCLNT100 and in E6P to PIPCLNT100. In this way any ABAP programming trying to use the ALE distribution model would send messages to PISERVER and would be transportable.
However, setting up the source system in the same way appears to be impossible. When attempting to generate partner profiles, transaction BD82 stubbornly insists that the source system for which it will build profiles MUST be the logical system name defined for the execution client in SCC4. Theoretically, mapping similar to that for PISERVER could be performed for ECC6SERVER and the ALE distribution model could be built to send messages from ECC6SERVER to PISERVER but BD82 won't honour this source system.
This appears to make it impossible to transport an ALE Distribution Model. Can anybody provide a process to overcome this apparent architectural limitation?

Automatic Deploying of Portal Configuration from Staging to Production Environment

Similar Messages

Maybe you are looking for