Bug 821

Summary: Deployment to non-default server takes 2x the time
Product: [Identity Manager] Identity Designer Reporter: Brent Thurgood <brent.thurgood>
Component: DeployAssignee: Brent Thurgood <brent.thurgood>
Status: VERIFIED FIXED QA Contact: Brady Rogers <brrogers>
Severity: Enhancement    
Priority: P5 - None Keywords: Built, Provo
Version: 2.0.0 Designer   
Target Milestone: 3.0 M2   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Brent Thurgood 2005-01-04 19:53:17 UTC 
DETAILED DESCRIPTION: Deploy a configuration to a 
server that is not the default server listed in the 
Identity Vaut. The deploy makes all non-server 
specific modification on the default server, but the 
server specific data must wait for the objects to 
synchronize from the default server to that target 
server. 

BUILD NUMBER: 
Oses/CONFIG: 
STEPS TO REPRO: 
RESULTS:
EXPECTED: 
WORKAROUNDS: Set the default server in the Identity 
vault to the DirXML server you are trying to deploy 
the DirXML configuration to.
CUSTOMER IMPACT: 


NTS entered defects should also include:
Additional debug info like screenshots, screencams, 
log files, trace files,
packet traces, memory coredump location.
Accurate customer information so that proper 
prioritizing of the defect is
possible (mainly for NTS defects)
Comment 1 Bill Street 2005-05-23 22:45:13 UTC 
Marking resolve later.
Comment 2 Bill Street 2005-08-02 17:48:16 UTC 
Reopening bugs for determination of fixing bug or adding enhancements for
Milestone 1.1.  

Bill
Comment 3 Brent Thurgood 2005-08-26 21:40:30 UTC 
Will not get to for 1.1, marking resolve later.
Comment 4 Bill Street 2007-07-09 22:52:23 UTC 
Reopening resolved/later bugs and changing to assigned/future.  Resolved/later is being removed from bugzilla.
Comment 5 Bill Street 2007-07-09 22:53:17 UTC 
marking assigned.
Comment 6 Brent Thurgood 2007-11-20 00:09:46 UTC 
Marking fixed. 

There has been a lot of work in 3.0 M2 for deploying to non-default servers. This bug was originally opened in 2005.
Comment 7 Brady Rogers 2007-11-27 23:28:24 UTC 
I believe this was fixed with bug 337280.