Created a domain using the script that is using several hosts. The pack and unpack command has been used to install the domain on the remote servers.
The pack command:cd $FMW_HOME/oracle_common/common/bin
./ -domain=/u02/config/domains/workshop_domain
The new created jar file was copied on the remote server and the unpack command run:cd $FMW_HOME/oracle_common/common/bin
./ -domain=/u02/config/domains/workshop_domain
Starting the node manager failed due to the DemoIdentity Java KeyStore file missing. This one was always generated in the previous WebLogic Sofware version.

Errors from the node manager log file:weblogic.nodemanager.common.ConfigException: Identity key store file not found: /u02/config/domains/workshop_domain/security/DemoIdentity.jks
at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(
at weblogic.nodemanager.server.SSLConfig.access$000(
at weblogic.nodemanager.server.SSLConfig$
at Method)
at weblogic.nodemanager.server.SSLConfig.(
at weblogic.nodemanager.server.NMServer.(
at weblogic.nodemanager.server.NMServer.getInstance(
at weblogic.nodemanager.server.NMServer.main(
at weblogic.NodeManager.main(

Starting from WebLogic, the unpack command does not generate the DemoIdentity.jks keystore file anymore. The DemoIdentity JKS file needs to be created manually or the Node manager changed to non SSL. After making sure the java set in the path is the one used by the WebLogic Domain run:cd /u02/config/domains/workshop_domain/security
java utils.CertGen -certfile democert -keyfile demokey -keyfilepass DemoIdentityPassPhrase -noskid
java utils.ImportPrivateKey -certfile democert.pem -keyfile demokey.pem -keyfilepass DemoIdentityPassPhrase -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePassPhrase -alias demoidentity
After this the Node Manager can be started successfully.

Thumbnail [60x60]
Pascal Brand