In this blog we will see how we can configure File Transfer Protocol (FTP) on Windows 2016 for EnterpriseOne Media Object.
Media Object Configuration Overview:
The media object configuration requires three pieces:
- FTP server configuration
- FTP Server Manager setting
- P98MOQUE update
By default, media objects are stored on the deployment server running a Windows operating system. Unless the Unix, Linux, or AS400 server hosting the HTML Web Server is able to map a network drive using Windows Networking to the deployment server with read/write authority, FTP protocol should be used to store and retrieve media objects.
Follow the instructions below to add the FTP Server component to the deployment server. These instructions are based on the Windows operating system but may change as Microsoft has new releases. However, the steps will be similar.
1. FTP on Windows Server (example with 2016):
- Open Windows Server Manager, then click “Add Roles and features”
- Select the FTP Server under Server Roles then click on Install
- Installation in progress.......
- Installation completed.
There is no Default FTP Site already created (only Default Web Site) hence a FTP site will need to be created for the next steps.
Follow the instruction below to set up a Media Object directory on the FTP server :
- On Windows Server Manager \ Dashboard , Click on Tools and then IIS
- Internet Information Services (IIS) Manager
- On the Left pane, Click on 'Sites' then click on 'Add FTP Site'
- Enter the FTP Site Name and Physical Path then click on Next
Note : When setting up the Physical Path in FTP, the media object directory cannot be at the root of the FTP physical path. For example, the file directory path D:\mediaobj is not correct, it should be c:\"folder path"\mediaobj where folder path is the directory that contains the mediaobj folder. An example directory path would be D:\JDEdwards\E920\mediaobj. Now, when creating your FTP physical path, select a folder above the mediaobj folder as the root. An example is shown in the Physical Path row in the screen shot below. We are navigating to the parent folder JDEdwards in the FTP configuration. This is the physical path where the FTP connection will start when E1 connects to the FTP server. Therefore, to the FTP connection, there is no JD Edwards folder in the path, as this is the directory it starts at. This correlates directly to the P98MOQUE section below, where the specific path is inserted.
- Select the options depending on your requirement. Here we are creating FTP Site with No SSL option then click on Next
- On Authentication and Authorization information screen, Select the below options.
Under Authentication and Authorization information - Read and Write permission should be there for the user provided in Server Manager for the FtpUser entry. Also verify that this user in jas.ini has read and write permissions for the Physical Path in FTP setup.
Note: Here we have created a E1FTPUser which has the Read and Write permission for the FTP Path.
- Click Finish to finish the configuration
- FTP Site Created
- Now Select the FTP Site then click on Manage FTP Site > Advanced Settings
- Make sure Physical Path is pointing to E1 Root Directory and note the FTP Binding Port :21
2. FTP Configuration in E1 Server Manager :
With tools release 8.97 and higher it is no longer necessary to use the MO QUEUE folder path in the jas.ini, which was required in previous releases. The configuration now comes from the web.xml file and is automatically configured. As for the port and share settings, they are now incorporated in Server Manager. To access these settings:
- After logging into Server Manager, locate the EnterpriseOne HTML Server link under Managed Instances and select it.
- On the left navigation bar, Select Advanced for the view type, locate Web Runtime under the Configuration header and select it.
- Under Web Runtime, you will see the Web Runtime - Media Object setings
- Enter the FTP User and Password
- Synchronize the changes
- Restart the Web-server
Testing the FTP Connection from Linux :
Install ftp rpm using yum install ftp command
Then follow the below steps to test the ftp connection from Linux OS
FTP connection working fine from Linux !
Testing the FTP connection from Windows :
You can use WinSCP to test the FTP connection from Windows.
Follow the below configuration to test the FTP connection using WinScp
FTP connection working fine from Windows as you can see the FTP folder structure successfully.
3. P98MOQUE Update
Our default installation for Media Object (MOBJ) attachments places the files on the Oracle JD Edwards EnterpriseOne (E1) Windows Deployment server under the \\SERVERNAME\(E1 Application Release)\MEDIAOBJ\ folder or \\SERVERNAME\JD Edwards\(E1 Application Release)\MEDIAOBJ\; where the E1 Application Release would be E900, E910, and so on.
The path to Media Object files is configured using P98MOQUE Media Objects Queues application. The Media Object Queue Path requires the user to enter the directory path used when connecting through the FTP connection. It is important to note that the path still follows the windows path as shown below and not the formatting for an FTP connection.
Note: Defining any of the P98MOQUE paths to be a local drive (c:\) is not supported and there should be no "/" nor "ftp" entries added into the P98MOQUE. The P98MOQUE is setup with the same path as you would use when setting up Windows networking except instead of following the windows directory path, it follows the path setup using FTP, ex: \\servername\E920_1\mediaobj\HTMLUpload.
Testing the Media Object Connection
- Login into web client
- Open P01012
- Try to attach the media object
- Below shows the successful retrieval of the attache media object from FTP location.