discoverDomain is missing JMS resource details

[zeusbaba]

I did export WDT template using discoverDomain, from 12.1.3.0.0, it worked without issues.
However, after analysing the template, I noticed that the details of JMS resource was missing.

the original resource file contains

<foreign-server name="UMSAQJMSForeignServer">
    <default-targeting-enabled>true</default-targeting-enabled>
    <foreign-destination name="OraSDPM/Queues/OraSDPMAppDefRcvQ1">
      <local-jndi-name>OraSDPM/Queues/OraSDPMAppDefRcvQ1</local-jndi-name>
      <remote-jndi-name>Queues/OraSDPMAppDefRcvQ1</remote-jndi-name>
    </foreign-destination>
    ...

but the exported WDT template is missing foreign-destination / ForeignDestination details

ForeignDestination:
    OraSDPM/Queues/OraSDPMAppDefRcvQ1:
    OraSDPM/Queues/OraSDPMAppDefRcvErrorQ1:
    ...

as far as I know, the expected output should be

OraSDPM/Queues/OraSDPMAppDefRcvQ1:
    LocalJNDIName: OraSDPM/Queues/OraSDPMAppDefRcvQ1
    RemoteJndiName: Queues/OraSDPMAppDefRcvQ1
...

[CarolynRountree]

Could you verify the version of WDT please? At the bottom of the stdout, there should be a version number. Or in the top directory of the install is a VERSION.txt file.

[zeusbaba]

i'm using the version from 18nov2020, I did create WDT package from master branch incl this commit

[CarolynRountree]

Looks like this is related to the slashes in the names and attribute values with WLS 12.1.3. To be schedule for a work around in WDT.

[zeusbaba]

in my original issue, I included <foreign-server name="UMSAQJMSForeignServer">... entry as an example as well.
is it sufficient? or do you need the whole file?

[rakillen]

We have a model to recreate the problem now, so no need to post yours. Looking into a solution for the slash names in 12.1.3.

[ddsharpe]

Unfortunately, WLST 12.1.3 (WebLogic Scripting Tool) has known issues with the slash (/) in object names. We looked into coding around these issues in WDT but the workaround that is required would only apply to WLS 12.1.x because the workaround breaks in 12.2.1.x (the next version of WebLogic Server). And, the workaround only worked for discovering the domain, and creating domains with slashes in names was still problematic. We, also, found that the WebLogic documentation for 12.1.3 recommends that slashes not be used in object names at all.

We do not have plans to implement a workaround for slashes in the object names for WLS 12.1.x. But, the slashes in the names for version 12.2.1.x domains should work.

Do you need the discovered model to create a 12.1.3 domain? Or were you planning on upgrading to a newer version of WebLogic?

[zeusbaba]

thnx for your efforts and feedback.
the current need is to use WDT for upgrading to 12.2.1.x, and I can confirm that it works fine.
using WDT for creating 12.1.3 domain is of a lower priority in this period.

However, notice that this issue #792 is related to discoverDomain from already set up 12.1.3.
I did introspect an already set up 12.1.3 so to produce WDT template, afterwards I did many manual fixes to that template so that to use for createDomain of 12.2.1.x domain.
one of the manual fixes was about the empty ForeignDestination: values.

I can share as a feedback about WDT, the expected flow is as below:

• discoverDomain should produce a template by introspecting an already set up domain
• the produced WDT template should be usable (with minimal intervention) to create a new domain
  both steps should be version agnostic.
  it might sound like a far stretched goal, but it brings a high value for teams who need to frequently create domains of diferent versions (both 12.1.3 and 12.2.1.x)

[ddsharpe]

@zeusbaba In regards to your statement of WDT being version agnostic, the WDT development team completely agrees with you. In most cases, WDT has been very successful at accomplishing that goal from 10.3.6 through 14.1.1. There are numerous things that WDT has coded around to make that goal a reality. But, there are a couple of minor anomalies that we have found that are very difficult or even impossible to code around. As you may know, WDT uses WLST Jython as its engine for modifying or reading WLS configuration. In the case of 12.1.3, WLST offline does not handle the slash character in object names. The offline-WLST team has published the recommendation to NOT use slashes in object names in their documentation and release notes. Since the 12.1.3 product version is no longer in active support at Oracle, we were unable to get a fix or enhancement that would make slash handling possible in WLST-offline for 12.1.3. Our solution in WDT when configuration in 12.1.3 contained slashes in names was to discover as much as possible to try to create a model that required the least amount of hand editing as possible. Please note that WLST-offline and WDT offline are not able to create configurations where there are object names that contain slashes whether you hand-edit them or not.

If this issue is not related to the slash in the name, please clarify.

[ddsharpe]

No response, please reopen if still an issue.

[zeusbaba]

many thnx for helping so far, yes plz this can be closed.
apologies for my late reply (new year's period...)