Mike,
   Thank you for the great answer. Much appreciated.

-Cory
On 02/24/2015 04:11 PM, Michael Blakeley wrote:
> For http-server-name I would have expected either of those to work. It's just 
> that one is hardcoded while the other uses roxy's properties feature. Use 
> properties wherever you might want to use different values in different 
> environments: local, dev, staging, prod.
>
> For password, depending on your configuration I think there may be multiple 
> different passwords at work. There's your admin username and password, which 
> have to be set in properties so that roxy can authenticate itself with 
> MarkLogic:
>
>      user=admin
>      password=...
>
> But then you might also have a `users/user` structure in the config XML, 
> which would need a password too. That one could come from your properties or 
> you could hardcode it in the XML. In this example the password comes from 
> properties, but there are other bits like role-name that are hardcoded.
>
>    <users xmlns="http://marklogic.com/xdmp/security";>
>      <user>
>        <user-name>@ml.app-name-user</user-name>
>        <description>A user for the @ml.app-name application</description>
>        <password>@ml.appuser-password</password>
>        <role-names>
>          <role-name>@ml.app-role</role-name>
>          <role-name>some-role</role-name>
>        </role-names>
>        <permissions/>
>        <collections/>
>      </user>
>    </users>
>
> -- Mike
>
>> On 24 Feb 2015, at 12:51 , cyanline llc <[email protected]> wrote:
>>
>> Geert, Mike,
>>    Thank you for the response. I will indeed post the data to github's
>> issues. If you don't mind, I do have one more question. You see, I
>> thought the ml-config.xml that is generated with 'ml new' and its
>> variables+values, need to be replaced. In other words, taking the line
>> that says
>>
>> <http-server-name>@ml.app-name</http-server-name>
>>
>>    with
>>
>> <http-server-name>myFirstSearchApp</http-server-name>
>>
>> But, what I think I am beginning to realize is that the @ value is a
>> symlink to a value in my env.properties file, which is why having
>>
>> <password>securepw!</password>
>>
>>    didn't work, but having in my dev.properties file
>>
>> password=securepw!
>>
>>    did work.
>>
>>    Am I correct in assuming the above?
>>
>> Thank you again,
>> Cory
>>
>> On 02/24/2015 01:38 PM, Geert Josten wrote:
>>> Hi Cory,
>>>
>>> Sharing the snippets of the captured ml-config that you copied over would
>>> help. You can open a ticket for that on github, as suggested by Mike..
>>>
>>> Kind regards,
>>> Geert
>>>
>>> On 2/24/15, 6:58 PM, "Michael Blakeley" <[email protected]> wrote:
>>>
>>>> I suspect that both messages are related to properties that are
>>>> referenced in the config XML but not defined.
>>>>
>>>> The first message looks like an empty appserver name. Check the config
>>>> XML for http-server and xdbc-server elements. They should have an
>>>> http-server-name or xdbc-server-name that won't be empty. If it's a
>>>> variable reference, you may need to add it to your local.properties file.
>>>> It could also be a reference to an appserver name: in that case you'd
>>>> probably have to debug it from that long stack trace in the ErrorLog.txt
>>>> file.
>>>>
>>>> The second message looks like a blank password. Check the config XML for
>>>> a 'user' element in the security namespace, and make sure it has a
>>>> password element that will be filled in. If it's a variable reference,
>>>> you may need to add it to your local.properties file.
>>>>
>>>> Hope that helps. If not, you might consider opening an issue at
>>>> https://github.com/marklogic/roxy/issues
>>>>
>>>> -- Mike
>>>>
>>>>> On 24 Feb 2015, at 09:29 , cyanline llc <[email protected]> wrote:
>>>>>
>>>>> Hello All,
>>>>>    I'm having issues getting the 'ml local bootstrap' command to run
>>>>> successfully. My goal is to use roxy's ml command to collect the
>>>>> settings from an existing db and server, and then deploy it.
>>>>>
>>>>>    The collections seemingly goes well. Then I copy/merge the relevant
>>>>> contents from the produced .xml into the default ml-config.xml file that
>>>>> is generated with the command 'ml new'.
>>>>>
>>>>>    Initially I was having authentication troubles running 'ml local
>>>>> bootstrap' - creating a local.properties file fixed that. Next, I am
>>>>> running into the following error:
>>>>>
>>>>> Bootstrapping your project into MarkLogic 7 on localhost...
>>>>> ERROR: XDMP-AS: (err:XPTY0004) $appserver-name as xs:string -- Invalid
>>>>> coercion: () as xs:string
>>>>> See MarkLogic Server error log for more details.
>>>>> ERROR: ... Bootstrap FAILED
>>>>>
>>>>>    Being unable to fix that, I tried just replacing ml-config.xml with
>>>>> the entire, unmodified ml-config-dev.xml (file produced from collection
>>>>> command). Bootstrapping this file produces the following error:
>>>>>
>>>>> Bootstrapping your project into MarkLogic 7 on localhost...
>>>>> ERROR: XDMP-LEXVAL: sec:password("") -- Invalid lexical value ""
>>>>> See MarkLogic Server error log for more details.
>>>>> ERROR: ... Bootstrap FAILED
>>>>>
>>>>>    Unfortunately, I am unable to make much from the error logs. All it
>>>>> seems to do is list all of the variables in my xml config file as
>>>>> error:variable, error:value, etc. Is it telling me I have an error on
>>>>> every  variable it lists?
>>>>>
>>>>>    Any resources or pointers would be greatly appreciated.
>>>>>
>>>>>    Thus far I have been using the following 2 resources the most:
>>>>>
>>>>>    1.
>>>>> http://grtjn.blogspot.nl/2014/10/capturing-marklogic-applications-with.ht
>>>>> ml
>>>>>    2.
>>>>> http://blog.davidcassel.net/2013/08/capturing-an-app-building-application
>>>>> -with-roxy/
>>>>>
>>>>> Thank you,
>>>>> Cory
>>>>> _______________________________________________
>>>>> General mailing list
>>>>> [email protected]
>>>>> http://developer.marklogic.com/mailman/listinfo/general
>>>> _______________________________________________
>>>> General mailing list
>>>> [email protected]
>>>> http://developer.marklogic.com/mailman/listinfo/general
>>> _______________________________________________
>>> General mailing list
>>> [email protected]
>>> http://developer.marklogic.com/mailman/listinfo/general
>> _______________________________________________
>> General mailing list
>> [email protected]
>> http://developer.marklogic.com/mailman/listinfo/general
>>
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general

_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to