Installing Rich Media Edition server for Rich Media Edition fix pack 06Added by IBM | Edited by IBM on February 23, 2016 | Version 4 (Show original)
|Before you can use assets from Rich Media Edition server, you must install and configure the Rich Media Edition server. You can install Rich Media Edition server on the same server as the portal or on a separate server.
Before you can set up Rich Media Edition server integration, ensure that you complete these steps:
- Install IBM® WebSphere® Portal V188.8.131.52 or IBM Web Content Manager V184.108.40.206 with Combined fix pack 06 or later.
- Obtain the installation media, either physical or electronic, for Rich Media Edition server. For more information about getting the media, see Getting the Rich Media Edition software.
These instructions describe the general steps that are required to set up the Rich Media Edition server with the optimal default configuration for integration with Web Content Manager. For detailed instructions on theRich Media Edition server configuration, see the Rich Media Edition server product documentation.
Start the Rich Media Edition server setup program, and follow the wizard panels to install the server.
- Access the Rich Media Edition server installation program.
- cd linux_install_root/mediabeacon/bin
- Windows: Run the MediaBeacon64.exe file.
Start the Rich Media Edition server console.
Specify the temporary product license information.
- Read and accept the license agreement.
- Choose a shared files directory to store digital assets, such as images, videos, and documents. The default folder is named MBAssets.
- Select a custom port number and web address to use to access assets.
You can change this setting later.
- Select Disable E-mail for the email notifications setting.
You can enable notifications later.
- Enter an administrator password.
This password is used to log in to the Rich Media Edition server with the manager account. Record the password for future reference. You can change this setting later.
- Specify the HTML5 video support settings.
- Select a performance option for the server.
You can change this setting later.
- Click Done to complete the installation.
Disable sharing on startup and stop the Rich Media Edition server.
- Access the IBM Temporary License from the mediabeacon_license_key.txt file in the root folder of your installation media.
Note: The IBM Temporary License provides a 30-day temporary license. After installation and configuration are complete, there are extra steps to configure your permanent license.
- In the Product License window, enter the name to associate with this license and the license key as specified in the IBM Temporary License.
- Click Enter License.
- On the License window, click Activate.
- On the Activation screen window, click Activate Now.
Set up pre-configured workspaces and default users in Rich Media Edition server.
- In the Rich Media Edition server console, click Admin.
- Clear the Enable sharing on Rich Media Edition server startup check box.
- Click Stop MediaBeacon.
Install a database server for use with Rich Media Edition server.
This configuration ensures better integration with Web Content Manager. Perform these steps on the Rich Media Edition server.
- Stop the Rich Media Edition server, and close the Rich Media Edition server console.
- Ensure that you defined a shared files directory for digital assets. The default folder is named MBAssets. The folder is typically defined during installation, but if you prefer, you can change the folder location after installation.
- Stop both the Rich Media Edition server and program.
- Delete any folders in the MBAssets folder that begin with m.
Examples of typical folders include m-archive-userinfo, m-layouts, and m-themes. For a new installation, it is likely that there are no folders yet.
- Delete the temporary directory for the Rich Media Edition server program.
- Linux: /root/.mediabeacon
- Windows: C:\Users\Administrator\Appdata\local\MediaBeacon
Note: By default, the Appdata folder is a hidden folder. To see this folder, change your folder options to show hidden files and folders.
- Copy the contents of the mediabeacon_install_root/MediaBeacon/etc/custom directory into the MBAssets directory.
Start the Rich Media Edition server console.
Click the Enterprise tab.
Configure Rich Media Edition server to use the external database server.
To enable communication with the portal server, you must configure Rich Media Edition server to use a remote database. The embedded database that is provided with Rich Media Edition server cannot be used. See the Rich Media Edition server documentation for more information about supported external databases.
Rich Media Edition server uses a separate database than the portal server. You can use the same installation of database software to manage the databases, or you can use separate installations.
If you intend to use an existing database installation with the Rich Media Edition server, use one of the following options before you configure Rich Media Edition server to use the database:
- Clean out all non-system tables in the existing database.
- Plan to use a new database for Rich Media Edition server data.
In the Authentication field, specify the type of authentication to use with the Rich Media Edition server.
- Select External database.
- In the Database type field, select the type of database server that you are using.
- Enter the access information for the database.
- Click Verify to confirm that Rich Media Edition server can connect to the database.
Update the authentication information file for your authentication type.
When a user in the portal wants to access an asset from Rich Media Edition server, the portal logs in to the server with that user's credentials. For this reason, both servers must use the same credentials when they communicate with each other. You can ensure that the credentials match in two ways:
- Both servers can share a single LDAP directory.
- You can define the same users and passwords in both servers.
Select the appropriate authentication method:
If you are using an LDAP directory with your portal to manage users and groups, you can use the same LDAP directory with your Rich Media Edition server.
- Select the type of LDAP directory that you are using with the portal.
IBM Tivoli Directory note: If you select IBM Tivoli Directory Server, ensure that you also select Ignore LDAP group information.
- Enter the access information for the LDAP directory.
If you are not using an LDAP directory to manage users and groups, select Standard. With this setting, you must manually create the same users from the portal in Rich Media Edition server.
To work with users and groups in Rich Media Edition server, access the Rich Media Edition server web interface, and select Admin -> Setup.
Important: For each user, the short name and password on the Rich Media Edition server must match the short name and password for the same user on the portal server.
- Edit the appropriate file, which is in the mediabeacon_install_root/etc directory.
Update the section bean with the ID of principalStore and add or change the defaultGroupName property.
- IBM Tivoli® Directory Server: auth-ibmds-nogroups.xml
- Oracle Internet Directory: auth-oid.xml
- No LDAP directory: auth-standard.xml
Enable communication with service-oriented architecture (SOA) applications, such as the portal.
<property name="defaultGroupName"><value>Content Users</value></property>
Authorize the portal to communicate with the Rich Media Edition server.
Communication between the portal and Rich Media Edition server takes place through a SOAP interface. SOAP is a specification for the exchange of structured information in a decentralized, distributed environment.
- Select External SOA applications.
- Click Change Remote Password, and enter a password for remote applications to use when they access Rich Media Edition server. WebSphere Portal uses these credentials to contact the Rich Media Edition server.
- In the Port field, specify the port number for remote applications to use when they access Rich Media Edition server.
On the Enterprise tab, click Apply to save your changes.
Restart the Rich Media Edition server.
- Click Applications.
- Click Add, and then enter the IP address for the portal server.
Complete the license registration.
- Click the Admin tab.
- Click Stop MediaBeacon, and then click Start MediaBeacon.
- Verify that the server started successfully.
In the Rich Media Edition server console, click Start MediaBeacon to start the server.
Disable the extended view in Rich Media Edition server for the Content Administrators and Content Users groups.
- From a web browser, log in to the Rich Media Edition server.
This URL is specified on the Sharing tab of the Rich Media Edition server console.
- Log in with the user manager, and specify the administrator password that you entered during the setup process.
If you changed this password after setup, the password is specified in the Admin Password field on the Admin tab in the console.
- Click the Content Users tab in the browser to change the view.
- In the widget entitled Using Temporary License, scroll down and click Click to permanently activate WCM_RME MB.
- In the Rich Media Edition server console, click Stop MediaBeacon on the Admin tab.
- Close the Rich Media Edition server console.
- Reopen the Rich Media Edition server console.
- Click Activate and then Activate Now to complete the registration process.
Parent topic: Setting up Rich Media Edition server integration for Rich Media Edition
Previous topic: Installing Rich Media Edition server for Rich Media Edition fix pack 08
Next topic: Upgrading Rich Media Edition
Getting the Rich Media Edition software
- In a browser, log in to the Rich Media Edition server with a user ID that has administrator access, such as the manager ID.
Example URL: http://www.example.com:55555/gwtmain/GwtMain.html
- Click Admin -> Setup -> Groups.
- Click Content Administrators -> Permissions -> Edit.
- In the list of privileges, select No for the Enable Full Extended View field.
- Click Done, and save your changes for the group.
- Click Content Users, and repeat the steps to disable the extended view for the Content Users group.