What are you trying to deploy? You can define the location in the blpackage itself.
1 of 1 people found this helpful
It depends on what you are deploying and how are you deploying.
One thing is fixed, anything you deployed is copied to a "Staging" area during the stage phase of deployment.
This location is defined by the Server Property called STAGING_DIR
For you example, if you are deploying an rpm, say you have a rpm in a blpackage and you deploy it,
during staging it will copied to a location specified by the property STAGING_DIR for the target/server,
after the install command for rpm like rpm -iv <rpm anme> will be invoked by agent deploy process.
This will install the rpm on the system, where it goes depends on the rpm itself.
Another example, you are deploying a blpackage , which has got some file assets ( with a + symbol), these will be deployed to the exact path you have specified in the Blpackage, also if that path is parameterised using proeprties, the path will be formed substituting all valued of all referenced proeprties available.
What are you asking for?
Thanks for your reply.
I can define the location in custom package but I am trying to deploy a patch.
what exactly are you looking for here? the temporary location the binaries are put during the deploy by bsa or where the payload is actually installed into on the remote system ?