Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Transaction Object and Data Source in Web Deployment

  1. How-to
0
Votes
Undo
  1. CJ Lai
    CJ Lai
  2. PowerServer 2020 or older (Obsolete)
  3. Thursday, 27 August 2020 16:55 PM UTC

All

I am a bit confused and don't seem to have a good way to solve this. I hope you may be able to help.

What's troubling me is how I can set up a deployment profile with one transaction object to have two different data sources?

I have to use the 'Package' method to deploy my app from local to a remote server (the server does not have FTP set up)

What's happening is when I package up my local (with data source as DEV_db) and unpackage it to the remote server, I have to manually go in the server's AEM to change the data source to UAT_db for those transaction objects. 

Is there a way to get around the manual update in my case?

Thanks

 

Powerserver Skips Function Call
Obsolete Application Entries in AEM
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 August 2020 17:25 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # Permalink

Hi CJ;

  What your doing now is the proper procedure when you use the PS package route yet have different DataSource names on the next target PS.

Regards ... Chris

Comment
CJ Lai
  1. CJ Lai
  2. Thursday, 27 August 2020 20:18 PM UTC
Thank you, Chris, for the info.
  1. Helpful
There are no comments made yet.
Responses (1)


There are replies in this question but you are not allowed to view the replies from this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.