Executing the DPE installer is fairly straightforward, and can be left to its defaults, generally speaking. If there are dependencies missing, it will fetch them for you. An example of what this may look like follows.
.png?cb=e4f71a4ecc28752ae2b288358989c01d)
Note that some dependencies are missing. We are going to use the installer to fetch them for us.
.png?cb=5f85fbac81400e245e2cff10d47e4740)
.png?cb=4399f2b26ebff318637d606d43d4096b)
.png?cb=88cf338a2fc33a4051d2836fcd7d3616)
.png?cb=f6d66d56c4a177087a80669478729efa)
.png?cb=4fb7cd82aaf4209c0cc5e53ed0cf9427)
Expect that this may take some time to complete.
.png?cb=ae7d1121e99b5a660ab19e1ebad999f6)
.png?cb=d65eddbac601e447c388d8c71e171564)
We are using dpeuser for this portion of the installation.
.png?cb=72ddba7ebe82472359f49309cb608d6c)
.png?cb=a8328a422d78dc0032400fe99bdc3ced)
We are using the normal SQL sign-on for this (the same which is used for DigaSystem's database access).
.png?cb=fbe057daecd08bfe5943088d7605d7ea)
.png?cb=244f5f5b735170c26fcd73a35d534a62)
.png?cb=096d5fecd6bc1ae9b5f239ccd6633501)
.png?cb=fe66b3fa6a013cfca860738605679e19)
.png?cb=9947f5ec4cc45583ab4d0f6b0a933b8b)
.png?cb=b732040b2d736d178baa8dcdf774d2da)
After the installation is complete, copy the licenses (features.xml and features.xml.signature) into the path specified. Observe the path in the example screenshot.
.png?cb=8eaa29c8bfe88df8ceb71ba619d07b22)