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; } } }

License, hostname and LSCS

Binettoid

Hi I have a new 7.2.1 dev environment with everything on the same Win2k3 box, including LiveSite Runtime CS and DS. I have a few problems:

a) I have tried to submit content and it works fine but never gives me the dialog to choose Publish Livesite Content or to choose Dev or Prod, despite both being defined in my odnodes.xml.

b) I don't see any LSCS projects created, despite tagging and submitting files from both component-guide and my own dev branch, for which I have created custom rules.

c) Assuming b) to be an issue with datadeploy, I have installed my license file (seems I forgot for OD as it kinda works for 30days without) but it fails with "Hostname" does not match "hostname" - a case mismatch - although when I look at my computer properties my hostname is "Hostname" (mixed case).
(when I run the od licinfo java it also reports "hostname" (all lower case) )

N.B. the kb article that seems to be about changing hostname for OD does not display on the support site a throws an error - kb 55838 - try it yourself.

Please can someone help?
What do i need to do to get the PLC, Dev and Prod dialog working?
Are my assumptions correct about b) and c) and what am I doing wrong?
Many thanks.

Find more posts tagged with

Comments

ISCBorisB

the kb article that seems to be about changing hostname for OD does not display on the support site a throws an error - kb 55838 - try it yourself

Few articles dealing with OD Licensing (55838 including) had been at some point consolidated into KB #60357

Binettoid

Hey thanks, Boris.

Sadly, this article seems to be a loose amalgam of several other people's observations as findable via your search engine of choice.
It doesn't describe how OD gets your hostname, how to change it, or why it should still report "hostname" when the computer name is changed to "VeryDifferentHostname2" in the windows computer name fields. (Obvious solution is that it is stored in a file somewhere but I can't find it)

I've installed OD several times and been able to change my hostname to the one on my license files (often "Hostname" rather than "hostname") but somehow this time OD still "sees" the old hostname regardless.

I've even written my own java test to retrieve my hostname and it reports "Hostname" - as appears in my license file - rather than "hostname" - as OD reports.

Why don't we just generate a new license file for "hostname"? I hear you ask - well as most of you will be aware, support accounts (even premium ones) tend not to give you all you've been promised until you ask for it, and ours does not yet allow us to do this.

Any advice or help on this topic is much appreciated.

ISCBorisB

...solution is that it is stored in a file somewhere but I can't find it

Chances are, this is stored somewhere in registry. If I were you I would try to search for the "wrong"
casing there. Host is all over the place though, it will take time. Try in CurrentControlSet first, it
should have something like iwod or perhaps iwodadmin folder. May be you'll get lucky.

In any case, this is just a trouble shooting suggestion, I certainly do not know what exactly is causing the problem.

jbonifaci

a) I have tried to submit content and it works fine but never gives me the dialog to choose Publish Livesite Content or to choose Dev or Prod, despite both being defined in my odnodes.xml.

b) I don't see any LSCS projects created, despite tagging and submitting files from both component-guide and my own dev branch, for which I have created custom rules.

What does your available_models.xml file look like?

Is the PLC workflow configured as a submit workflow for your branch?

The only way you get a choice when submitting is if more than one submit workflow is configured for your branch (combination of available_templates.cfg and available_models.xml).

My guess is that only the default submit workflow is configured and that your files are only getting submitted to staging, not running through the PLC workflow.

As soon as you configure the PLC workflow for your branch, you will see both the workflow selection and then the PLC instantiation screen (which are the two selections you are talking about).

Let me know if that helps or if you have any other questions.

Thanks!
~Jeff

Binettoid

Thanks Jeff, you are spot-on.
I worked this out, tested submitting content to LSCS using the CLT worked, and tried to modify the available_models.xml in the install folder - the only place I could find it - but it had no effect.
I got help with this from support, who told me to do this from within the UI and lo and behold, this fixed the problem and all my rules and deployment started working as expected. (prolly worth mentioning they suggested applying the PLC for a regex of .* which broke template and component submission ;-)
No idea why this was not set up OOTB - isn't PLC supposed to be? Sure it was on my 7.1 platform. We did install the WFmodelling toolkit so perhaps that did something?
Reassuring to know that somebody out there uderstood my issues - thanks again Jeff.