Exception: <type 'exceptions.AttributeError'> when Adding deployment plan

[PhilippeAndro]

logs.zip

Hi,

When I use WDT 4.3.0 , I have an error that breaks the tool. I don't want to add the wars so I flagged with -skip_archive. I have the same problem with the -remote flag.
The deployment plan file is reachable as you can see at the end of the log. Why did the tool wants to archive deployment plan as I don't want the wars.

There is an error with the MaxRequestParamterCount too.
That works with my current 3.2.1 version.

Thanks for you help,
Philippe

[robertpatrick]

@PhilippeAndro thanks for the issue.

I have resolved the discover issue that was inadvertently introduced in WDT 4.0 when we added SSH support. What the Discover Domain Tool does with the -skip_archive and -remote options is documented in the 4th paragraph of the Discover Domain Tool docs. My fix will also add to the documentation to try to make it clearer as to what each option does with regards to files that would normally be archived. In short:

• -skip_archive: leaves the file paths from the domain in the model in both offline and online mode. The user is sort of on their own to fix up the model as needed to create or update a new domain.
• -remote: puts the archive path locations into the model and prints out TODOs to help the user understand what archive items were skipped--this flag is only valid in online mode. We assume that the user will want to populate the archive file themselves to complete the model of the discovered domain. If not, you can use -skip_archive instead.

As for this log entry:

####<Jan 13, 2025 3:04:36 PM> <INFO> <Discoverer> <_get_model_name_and_value> <WLSDPLY-06106> <Unable to add MaxRequestParamterCount from location /Server/srvBanApn10/WebServer/NO_NAME_0 to the model: Failed to convert the wlst attribute name and value for the model at location (model_folders = ['Server', 'WebServer'],  'name_tokens' = {'DOMAIN': 'base_domain','WEBSERVER': 'NO_NAME_0','SERVER': 'srvBanApn10'}): The wlst attribute MaxRequestParamterCount is not defined for the model folder /Server/WebServer>

This is not really an error but we understand it is annoying and may cause this setting to not be added to the model. Richard has already committed a fix for this issue late last week. He has one more issue that we are trying to resolve. Once that is done, we plan to cut a 4.3.1 release that addresses these issues.

[PhilippeAndro]

Thanks for your help.
I'm waiting for 4.3.1 release.

[robertpatrick]

Fixed in release 4.3.1