You can use the installation guide for details or the quick installer that comes with the package. The installation requires two parts that make PLMXL Approve work. The PLMXL Services Platform (PSP) which resides on the server side and the mobile device software of your preference.
The PLMXL Services Platform (PSP) application resides on a separate server in the corporate premises. The FSP server application runs within an Apache/Tomcat that need access from outside the corporate firewall to accept mobile device requests on http (port 80) or https (port 443). The FSP communicates via the internal corporate network with the Agile PLM server on the standard Agile port.
Windows Server 2000 or greater. Any version of Windows Server will work. The FSP can also deploy on variations of Linux.
Details can be found in the installation guide. Generally any current Intel Core 2 duo 2.5Ghz with 8GB or greater RAM will work out fine for a user population up to 100 users. More RAM will accommodate more concurrent users.
There are multiple levels of security no counting any other policies the installation site may implement. Each request is authenticated with the combination of mobile device ID, username and password:
- A “white list” of allowable IMEI or UDID devices list is managed in the FSP. Permits only sanctioned devices to receive data in Agile
- HTTP SSL (128 bit) transport for secure data transmission stateless requests
- The FSP server by its presence creates an intermediate layer which blocks any direct external access to Agile
- Agile username and password for authentication
The FSP server needs access from outside the corporate firewall to accept mobile device requests on http (port 80) or https (port 443). The FSP communicates via the internal corporate network with the Agile PLM server on the standard Agile port using RMI
Yes, SSL certificates are imported in the Tomcat application server hosting FSP. Installing the Trusted Third Party signed certificates is the responsibility of your internal IT and not part of the installation.
Yes. It supports a high availability failover clustered environment with one active node and multiple passive nodes.
Although rare and difficult, some companies are very sensitive to their Intellectual Property being intercepted in the device. The data in the device is no more susceptible than file attachments in email clients on the device. Nonetheless PLMXL Approve device apps do not store the file even in the cache.
It can be deployed in your enterprise app store or downloaded from the Apple App store. The app will work only after you configure the URL to point to your own deployed FSP and also register the Apple device UDID in the FSP admin.
They are the same. The app intelligently displays customized on each type of iOS device
It is downloaded via a URL in your Android browser. The install can be hosted on your corporate intranet or anywhere else. The app will work only after you configure the URL to point to your own deployed FSP and also register the Android device IMEI id in the FSP admin.
It is downloaded via a URL in your Blackberry browser. The install can be hosted on your corporate intranet or anywhere else. The app will work only after you configure the URL to point to your own deployed FSP and also register the Blackberry device IMEI id in the FSP admin.
Blackberry OS 5.0 or greater – Blackberry Tablet OS not Supported as of present)
Android Gingerbread 2.3.3 or greater
Apple iOS 5.0 or greater
PLMXL Approve is managed through a web based admin client. You can enable and disable user device ids, set the target Agile server, configure classes and data to be accessed on the devices. The application server itself can be brough down or up from the Apache Tomcat admin client.
Your present Agile admin should have plenty of bandwidth to manage the application. No extra resource is needed.
With a support and maintenance agreement, you get email support at firstname.lastname@example.org answered within 4 hours. You will also have a 24 X 5 (US Pacific Time) phone support.
With a support and maintenance agreement, you will receive quarterly product upgrades with new features that will seamlessly overlay your existing FSP. Users may then subsequently update their device software over time.
OTA MDM can be performed.
Yes. Hardware resources may need to be scaled to compensate.