To clarify: By trunk I mean 'latest version' from trunk. Also the m1 release contains pdfs of the wiki docs, does that suffice as enough of an archive?
-Ben Dewey -----Original Message----- From: Ben Dewey [mailto:[email protected]] Sent: Thursday, July 09, 2009 12:20 AM To: '[email protected]' Subject: Archiving M1 Install/Interop WIKI Documentation (was: RE: BREAKING CHANGE (RE: [jira] Updated: (STONEHENGE-67) Setup .NET Client/BS/OPS to get Active BS/OPS from config service)) Ping... > Mentors, > What's the best way to archive the install guides for the M1 release? Or > should the CWiki only pertain to the trunk? -Ben Dewey -----Original Message----- From: Ben Dewey Sent: Tuesday, June 30, 2009 7:29 AM To: [email protected] Subject: RE: BREAKING CHANGE (RE: [jira] Updated: (STONEHENGE-67) Setup .NET Client/BS/OPS to get Active BS/OPS from config service) I should be able to test this patch tonight and report back. In the meantime, Avantika, if you want to take a look at the Install Guide and Interop Guide on the CWiki and start drafting what changes need to be made to these documents. Mentors, What's the best way to archive the install guides for the M1 release? Or should the CWiki only pertain to the trunk? PHP Guys, The patch contains scripts to create the Service/ClientToBs/BsToOps/DbConfig Tables. Should we remove the PHP scripts that do the same? -Ben Dewey ________________________________________ From: Drew Baird (Volt) [[email protected]] Sent: Tuesday, June 30, 2009 12:18 AM To: [email protected] Subject: FW: BREAKING CHANGE (RE: [jira] Updated: (STONEHENGE-67) Setup .NET Client/BS/OPS to get Active BS/OPS from config service) (From Avantika and Drew) This is the patch for the new config service for dotnet. Here are some instructions for testing this patch: 1) Start with a clean directory for StockTrader 2) Apply this patch (Stonehenge-67-FINAL) to the dotnet folder in StockTrader 3) In the zip file attached, there is a .ico and .snk file. Put in the .snk file into every folder of Config_service. There is also a new folder in common called ConfigClient - put the .snk file in there too. The .ico file needs to go into the ConfigServiceConsoleHost folder in Config_Service. 4) Go to SetupActions and open SetupActions solution. Update the App.config to reflect the pathname for the dotnet folder. Run the solution to create the necessary tables in the database. 5) Once this is completed, run BuildDotNet.cmd [Remember to build trade_client from the IDE since the build command has issues there.] 6) Run as administrator the RunServices.bat 7) Open up localhost\trade to test the services. All configuration changes can be made from the database. Avantika and I are testing the patch for the config service. Applying the patch is tedious. However, this is a breaking change and needs at least one more person to test. Please let me know (Ben?) when you have tested this and I can commit. See https://issues.apache.org/jira/browse/STONEHENGE-67 for more information. Thanks! Drew and Avantika -----Original Message----- From: Avantika Agrawal (JIRA) [mailto:[email protected]] Sent: Monday, June 29, 2009 11:47 AM To: [email protected] Subject: [jira] Updated: (STONEHENGE-67) Setup .NET Client/BS/OPS to get Active BS/OPS from config service [ https://issues.apache.org/jira/browse/STONEHENGE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avantika Agrawal updated STONEHENGE-67: --------------------------------------- Attachment: Stonehenge-67-FINAL.patch Also, the .snk files need to be added to the new folders. > Setup .NET Client/BS/OPS to get Active BS/OPS from config service > ------------------------------------------------------------------ > > Key: STONEHENGE-67 > URL: https://issues.apache.org/jira/browse/STONEHENGE-67 > Project: Stonehenge > Issue Type: New Feature > Reporter: Avantika Agrawal > Attachments: Stonehenge-67-FINAL.patch, test-67.patch > > > Once the config service is created, hook up the .NET Client/BS/OPS to find > the endpoints from the database > i.e. configuration should happen from the database rather than the config > files - replicating the functionality of the PHP implementation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
