YAML file parse errror

[sorenlloyd]

I have created a YAML file via the discover process and am now deploying, after replacing the necessary FIX ME property values.

I am now getting a parse error which is odd as i have not edited these lines. Any advice?

        1. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 337 position 8: mismatched input '172.30.76.13' expecting {NAME, LIST_ITEM_OP}
        2. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 341 position 8: extraneous input '172.30.76.14' expecting {<EOF>, NAME, LIST_ITEM_OP}
        3. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 344 position 8: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        4. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 348 position 8: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        5. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 352 position 8: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        6. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 356 position 4: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        7. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at l
ine 388 position 0: extraneous input '\n' expecting {<EOF>, NAME, LIST_ITEM_OP}
        8. WLSDPLY-09014: deployApps was unable to load the model from /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/dis
covered_domain.yaml due to a translation error: Unable to parse model from file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments
/dev2/discovered_domain.yaml : The YAML parser encountered 7 error(s) while parsing /opt/app/nfs/build_and_deploy/weblogic-deployment/environm
ents/dev2/discovered_domain.yaml

Here are the lines in question....

    336     UnixMachine:
    337         172.30.76.13:
    338             NodeManager:
    339                 NMType: Plain
    340                 ListenAddress: 172.30.76.13
    341         172.30.76.14:
    342             NodeManager:
    343                 NMType: Plain
    344                 ListenAddress: 172.30.76.14
    345         172.30.76.15:
    346             NodeManager:
    347                 NMType: Plain
    348                 ListenAddress: 172.30.76.15
    349         172.30.76.16:
    350             NodeManager:
    351                 NMType: Plain
    352                 ListenAddress: 172.30.76.16
    353         172.30.76.17:
    354             NodeManager:
    355                 NMType: Plain
    356                 ListenAddress: 172.30.76.17
    357     SecurityConfiguration:
    358         NodeManagerPasswordEncrypted: 'fdkfkjdsks'
    359         NodeManagerUsername: s2GdxQrWpL
    360         CredentialEncrypted: 'dfsdflsdjfkl'
    361         EnforceValidBasicAuthCredentials: false
    362         Realm:
    363             myrealm:
    364                 Adjudicator:
    365                     DefaultAdjudicator:
    366                         DefaultAdjudicator:
    367                 AuthenticationProvider:
    368                     DefaultAuthenticator:
    369                         DefaultAuthenticator:
    370                     DefaultIdentityAsserter:
    371                         DefaultIdentityAsserter:
    372                             ActiveType: [ AuthenticatedUser, 'weblogic-jwt-token' ]
    373                 Authorizer:
    374                     XACMLAuthorizer:
    375                         XACMLAuthorizer:
    376                             PolicyDeploymentEnabled: true
    377                 CertPathProvider:
    378                     WebLogicCertPathProvider:
    379                         WebLogicCertPathProvider:
    380                 CredentialMapper:
    381                     DefaultCredentialMapper:
    382                         DefaultCredentialMapper:
    383                 PasswordValidator:
    384                     SystemPasswordValidator:
    385                         SystemPasswordValidator:
    386                 RoleMapper:
    387                     XACMLRoleMapper:
    388                         XACMLRoleMapper:
    389 resources:
    390     JDBCSystemResource:

[kaifricke]

Hello,

WDT has it's own YAML parser. If I interpret the grammar file correctly, names can not start with an integer:

NAME : ID_START ID_CONTINUE* WS? | '\'' QUOTED_ID_START QUOTED_ID_CONTINUE* '\'' WS? | '"' QUOTED_ID_START QUOTED_ID_CONTINUE* '"' WS? ;

fragment ID_START : [_] | [A-Z] | [a-z] | '!' ;

If you have gotten those machine names from a discovery process, I assume Weblogic allows them and it's a WDT limitation.

-Kai

[rakillen]

The problem with the resulting model is that the dotted addresses are not in quotes. By doing these changes to each UnixMachine entry, I was able to get the model to load and operate:

        '172.30.76.13':
            NodeManager:
                NMType: Plain
                ListenAddress: '172.30.76.13'

The discovery tool should be doing this automatically, and we'll look into fixing that. Let's leave this issue open to track that.

[sorenlloyd]

Thanks, I'll try and fix it with another edit

[sorenlloyd]

So i made the edit but I am still getting the same error. Any suggestions?

New YAML section...

    335             Notes: This is a system generated default migratable target for a server. Do not delete manually.
    336     UnixMachine:
    337         '172.30.76.13'
    338             NodeManager:
    339                 NMType: Plain
    340                 ListenAddress: '172.30.76.13'
    341         '172.30.76.14'
    342             NodeManager:
    343                 NMType: Plain
    344                 ListenAddress: '172.30.76.14'
    345         '172.30.76.15'
    346             NodeManager:
    347                 NMType: Plain
    348                 ListenAddress: '172.30.76.15'
    349         '172.30.76.16'
    350             NodeManager:
    351                 NMType: Plain
    352                 ListenAddress: '172.30.76.16'
    353         '172.30.76.17'
    354             NodeManager:
    355                 NMType: Plain
    356                 ListenAddress: '172.30.76.17'
    357     SecurityConfiguration:
    358         NodeManagerPasswordEncrypted: 'weblogic113'
    359         NodeManagerUsername: s2GdxQrWpL
    360         CredentialEncrypted: 'weblogic'
    361         EnforceValidBasicAuthCredentials: false
    362         Realm:
    363             myrealm:
    364                 Adjudicator:
    365                     DefaultAdjudicator:
    366                         DefaultAdjudicator:
    367                 AuthenticationProvider:
    368                     DefaultAuthenticator:
    369                         DefaultAuthenticator:
    370                     DefaultIdentityAsserter:
    371                         DefaultIdentityAsserter:
    372                             ActiveType: [ AuthenticatedUser, 'weblogic-jwt-token' ]
    373                 Authorizer:
    374                     XACMLAuthorizer:
    375                         XACMLAuthorizer:
    376                             PolicyDeploymentEnabled: true
    377                 CertPathProvider:
    378                     WebLogicCertPathProvider:
    379                         WebLogicCertPathProvider:
    380                 CredentialMapper:
    381                     DefaultCredentialMapper:
    382                         DefaultCredentialMapper:
    383                 PasswordValidator:
    384                     SystemPasswordValidator:
    385                         SystemPasswordValidator:
    386                 RoleMapper:
    387                     XACMLRoleMapper:
    388                         XACMLRoleMapper:

New Error Message

        1. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 337 posi
tion 8: mismatched input ''172.30.76.13'' expecting {NAME, LIST_ITEM_OP}
        2. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 341 posi
tion 8: extraneous input ''172.30.76.14'' expecting {<EOF>, NAME, LIST_ITEM_OP}
        3. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 344 posi
tion 8: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        4. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 348 posi
tion 8: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        5. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 352 posi
tion 8: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        6. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 356 posi
tion 4: extraneous input ' ' expecting {<EOF>, NAME, LIST_ITEM_OP}
        7. WLSDPLY-18018: Parse error for file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml at line 388 posi
tion 0: extraneous input '\n' expecting {<EOF>, NAME, LIST_ITEM_OP}
        8. WLSDPLY-09014: deployApps was unable to load the model from /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_doma
in.yaml due to a translation error: Unable to parse model from file /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.
yaml : The YAML parser encountered 7 error(s) while parsing /opt/app/nfs/build_and_deploy/weblogic-deployment/environments/dev2/discovered_domain.yaml

[rakillen]

The colons are missing from the machine name lines:

    337         '172.30.76.13'
    338             NodeManager:
    339                 NMType: Plain
    340                 ListenAddress: '172.30.76.13'

should be:

    337         '172.30.76.13':
    338             NodeManager:
    339                 NMType: Plain
    340                 ListenAddress: '172.30.76.13'

(for all UnixMachine entries)

[rakillen]

Fix was made to allow digit as the first character in identifier. Discovery was working correctly, quotes are not required around identifiers or values containing dot.