nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD for TS6.5Base to TS6.7.1Base deployment

djo2112

Has anyone done this successfully?

I keep receiving the standard 'not an allowed deployment path' error when attempting to do this. Exact error: LIB: 2008-01-22 16:05:12 Receiver-ERROR: ERROR: [z:\technology_services\main\release_mgmt\workarea\tsadmin_wa] is not an allowed deployment path.

Should I be specifying the OS path mapping ie. Y:\... or should I be sticking to IWServer mapping \\IWSERVER\... when specifying source and target areas?

I have changed the odbase on the 6.7.1 server to allow the OS directory.

I am pasting my OD xml in hopes the experts will have mercy on me and critique me.

The "Z:" referred to below is an OS drive mapping on the TS6.5 base server.

-Dave

[html]

[/html]

Find more posts tagged with

Comments

nipper

This error says that the OD receiver is not allowed (od_rcvr.xml, I think) to write to this folder.

Check the receiver config.

djo2112

Hi "Nipper",

OK, so do I need an odrcvr.xml in the etc folder as well? This is running on the base OD server.

-Dave

nipper

Yea there is a file on the receiver, where the files are to be deployed, that specifies the valid locations for OD to write to.

Also, make certain you either reset or restart OD after you change this, you can run iwodserverreset on the receiver.

djo2112

OK.

Created an odrcvr.xml in the etc folder and allowed the full path.

Same 'not allowed' error.

-Dave

nipper

OK.

Created an odrcvr.xml in the etc folder and allowed the full path.

Same 'not allowed' error.

-Dave

Did you reset or restart the OD receiver ?

djo2112

iwodcmd serverreset

nipper

Now I am also rather confused of what you are really trying to do. It appears you are taking the latest edition and deploying it to the same branch, into the tsadmin_wa workarea.

Note, I did not realize you are deploying to and from the same server. You do not need the odrcvr.xml file, that is defined in odbase.xml. But that should be Y: unless you have Y: mapped to Z:

Andy

djo2112

Hey Andy,

I want to us OpenDeploy from a TS6.5 to a TS6.7.1 server so I am deploying to different servers.

I am thinking that I have incorrectly defined localNode host="MyLocalHost". I do not believe this should be the localhost but the server I intend to move to.

Appreciate your help.

-Dave

nipper

So I *think* I know what is going on.

Server A run TS 6.5, B runs 6.7.1.

You are trying to deploy on B form a mounted drive from A to TS.

I think you will be better running it on A to server B. The destination should be Y: and it needs to be writable by OD

Adam Stoller

Hi "Nipper",

OK, so do I need an odrcvr.xml in the etc folder as well? This is running on the base OD server.

-Dave

If you have an ODBASE server installed on both ends - then you need an odbase.xml on both ends.

If you have an ODBASE server on one end and a ODRECEIVER on the other end (doubtful if they're both TS servers) - then you would need an odbase.xml on one end and an odrcvr.xml on the other.

You do NOT need an odrcvr.xml on an ODBASE server.

djo2112

So I *think* I know what is going on.

Server A run TS 6.5, B runs 6.7.1.

You are trying to deploy on B form a mounted drive from A to TS.

I think you will be better running it on A to server B. The destination should be Y: and it needs to be writable by OD

I need to go from A to B - your assumption is correct. The only reason the destination was Z: because Y: was taken by the host server so I mapped the destination TS server (B) to Z:

-Dave

djo2112

I wanted to post my solution in case someone else wants to do this. You can use OD to deploy from TS base server to a different TS base server as long as you do a few things. I did it this way because I needed to make sure I was getting the EAs (Extended Attributes) from the branch and I didn't want to use any of the migration tools. This means, I didn't need any editions or other work areas in the branch.

a) Your base receiver's odbase.xml must contain a node for the senders allowedHosts:

[html]

[/html]

Don't forget to iwodcmd serverreset after changing the odbase.xml file.

b) Use the "iwStore" for a source destination and "targetTeamsite" for a target destination in your .xml for OpenDeploy. Here's a working example I used:

[html]

[/html]

Hope this helps.
-Dave

Adam Stoller

For what it's worth - you don't need the useReplicationFarm attribute for the target element if you are using the replicationFarmLink element.

djo2112

When I was driving home, I thought about that too...
Thanks for taking the time to comment - it's always appreciated!
-Dave

niniti

I created seoparate thread for my question.

Thanks