If you are unable to create a new account, please email support@bspsoftware.com

 

How to change the path of publishing package in FM into other environment

Started by inu, 03 Nov 2016 04:49:04 AM

Previous topic - Next topic

inu

Hi Team,

My package is always published into dev environment. i want to publish the package into prod environment.

Please share the steps...




Regards,
Inam

MFGF

Quote from: inu on 03 Nov 2016 04:49:04 AM
Hi Team,

My package is always published into dev environment. i want to publish the package into prod environment.

Please share the steps...




Regards,
Inam

1. Export the package (and its reports if needed) from Dev via a deployment export.
2. Move the deployment file from the Dev to the Prod server
3. Import the deployment on the Prod server.

MF.
Meep!

inu

Quote from: MFGF on 03 Nov 2016 06:18:32 AM
1. Export the package (and its reports if needed) from Dev via a deployment export.
2. Move the deployment file from the Dev to the Prod server
3. Import the deployment on the Prod server.

MF.

Yes MF. i know that , but my PM told me  not to migrate from dev to prod.

Regards,
Inam

MFGF

Quote from: inu on 03 Nov 2016 06:28:44 AM
Yes MF. i know that , but my PM told me  not to migrate from dev to prod.

Regards,
Inam

What is the reasoning behind this?
Meep!

inu

Quote from: MFGF on 03 Nov 2016 06:36:28 AM
What is the reasoning behind this?

He might be thinking that , reports will move , that will create issue to the users.


Regards,
inam

MFGF

Quote from: inu on 03 Nov 2016 09:23:28 AM
He might be thinking that , reports will move , that will create issue to the users.


Regards,
inam

So why not just deploy the package without the reports? Why would someone give you a task then tell you how not to do it, when what they are telling you not to do is the approved, tried, trusted mechanism? Why haven't you questioned the instruction and clarified the misunderstanding as to why it should not be done in this way?

If someone said to you "I need you to knit a scarf. Don't use knitting needles" you would push back and question why knitting needles should not be used, wouldn't you? What's the difference in this case? Why should deployment archives not be used to move your packages? The reason you have stated above doesn't stand up to scrutiny.

MF.
Meep!

Michael75

QuoteHe might be thinking that , reports will move , that will create issue to the users.

Not a problem unless, of course, the practice at Inu's site is to place reports within a package. I've always understood this to be bad practice, precisely because of the problems it creates with content promotion.


MFGF

Quote from: Michael75 on 03 Nov 2016 10:58:47 AM
Not a problem unless, of course, the practice at Inu's site is to place reports within a package. I've always understood this to be bad practice, precisely because of the problems it creates with content promotion.

Indeed! It's also easy to temporarily move the reports elsewhere if needed.
Meep!

inu

Quote from: MFGF on 03 Nov 2016 11:43:13 AM
Indeed! It's also easy to temporarily move the reports elsewhere if needed.

Yeah, MF. I found that query from this forum only...I removed that...
How to resolve this issue, or should i use detail filter for such a hectic issue.


Regards,
Inam