

For example, E920.Įxpand the shared node and open OneWorld Client Installs\ThirdParty. On the deployment server, open Windows Explorer and navigate to your JD Edwards EnterpriseOne solution's shared folder. To create a Visual Studio runtime library package feature: Note the string 12.0 in the path even though it is for Visual Studio 2013. For example, the Runtime Libraries installer for the 2013 compiler release is:Ĭ:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\redist\1033\vcredist_x86.exe The x86 indicates that this installs 32-bit runtime libraries-which is exactly what JD Edwards EnterpriseOne needs because the JD Edwards EnterpriseOne programs on the Development Client are 32-bit programs. The Deployment Server should have a copy of the compatible vcredist_x86.exe. Create a package feature for the Microsoft Visual C++ compiler runtime libraries to leverage this facility. The JD Edwards EnterpriseOne package build feature makes it possible to distribute third party applications with the deployment of a client package.

Assuming Microsoft makes a new service pack available or requires an update for its Microsoft Visual C++ compiler and it is installed on your JD Edwards EnterpriseOne Microsoft Windows build machines, you must do the following:Įnsure that all JD Edwards EnterpriseOne Microsoft Windows build machines, both servers and workstations, have the identical compiler service pack release levels installed.ĭistribute the new Microsoft Visual C++ runtime libraries to all Microsoft Windows machines that are receiving packages built by Microsoft Visual C++ and do not have a compiler installed.

When you build new packages using the Microsoft Visual C++ compiler, you must ensure that all machines receiving these packages have the corresponding runtime libraries installed. Please refer to the Oracle Certifications to identify supported versions of the Microsoft Windows platform compiler for the JD Edwards EnterpriseOne Client. Note: All references to Microsoft Visual C++ refer to the defined JD Edwards EnterpriseOne minimum technical requirement Microsoft Windows platform compiler.
