TIBCO 7.3.0 Managed File Transfer Command Center Quick Start Guide
ಜಾಹಿರಾತು
ಜಾಹಿರಾತು
TIBCO® Managed File Transfer
Command Center
Quick Start Guide
Software Release 7.3.0
October 2015
Documentation Command Center Quick Start Guide
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR
BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON
FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT
LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT,
OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT
WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE OR IF THERE IS NO
SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE
LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT
TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND
AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and treaties.
No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, The Power of Now, TIBCO Managed File Transfer, TIBCO Managed File Transfer Command Center, TIBCO
Managed File Transfer Internet Server, TIBCO Managed File Transfer Platform Server, TIBCO Managed File
Transfer Platform Server Agent, and Slingshot are either registered trademarks or trademarks of TIBCO Software Inc. or its subsidiaries in the United States and/or other countries.
EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES
ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN
NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR
CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY,
BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO
ANY RELEASE NOTES AND "READ ME" FILES.
TIBCO® Managed File Transfer Internet Server with RocketStream® Accelerator is entitled TIBCO® Managed File
Transfer Internet Server in certain other product documentation and in user interfaces of the product.
Copyright © 2003-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information.
TIBCO welcomes your comments on this publication. Please address your comments to:
TIBCO Software Inc.
200 Garden City Plaza
Garden City, New York 11530 USA
Web site: http://www.tibco.com
Technical Support E-mail: [email protected]
Technical Support Call Centers:
North and South America: +1.650.846.5724 or +1.877.724.8227 (1.877.724.TACS)
EMEA (Europe, Middle East, Africa): +44 (0) 870.909.3893
Australia: +61.2.4379.9318 or 1.800.184.226
Asia: +61 2 4379 9318
When you send information to TIBCO, you grant TIBCO a non-exclusive right to use or distribute the information in any way TIBCO believes appropriate without incurring any obligation to you.
2
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Getting Started with MFT Command Center Command Center Quick Start Guide
Getting Started with MFT Command Center
This guide has been developed to walk you through the steps necessary to configure the MFT Command
Center for the first time. A brief description of the steps necessary to get the Command Center up and running is provided. The MFT Command Center is the administrative component of the MFT Internet
Server and the MFT Platform Server. In most cases the basic functionality described in this document is the same for both products. It will be noted when a function or feature is specific to a single product.
This guide explains:
1. Adding your Email Server to MFT Command Center
4. Setting up and Executing MFT Platform Server to Platform Server Transfers
5. Setting up and Managing DNI Daemons
6. Collecting Platform Server Audit Records
7. Initiate Platform Transfers Using JMS
8. Sending Data to a JMS Queue
9. Receiving Data from a JMS Queue
Once MFT Command Center is installed, it is time to access the Command Center screens.
The MFT Command Center is accessed using the following URL:
https://[DNS_HostName]:[httpsPort]/cfcc/control?view=view/admin/start.jsp
When you are prompted for a userid/password you must log in with the Administrator credentials of
admin/changeit.
3 Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Adding Your Email Server to MFT
1 Adding your Email Server to MFT
There are some minimum MFT configurations we recommend being set. Adding your email server information is one of them.
1.1 Configure your Email Server Information
The first thing we recommend you configure is the IP or Host Name and port of your email server in order to receive various email notifications from many of the MFT features that can be configured with an email address(s). To do this navigate to Administration > System
Configurations and expand the Global Settings window by clicking on the plus sign contained in the box next to the words “Global Settings” and you will see at the top of the web page the following email fields to be configured:
Fill in the Email Host Name with the IP or host name for the email server and the Sender Email
Address that will be used on all emails sent from MFT Command Center. If there is an MFT
Internet Server being administered by MFT Command Center then set the Transfer Notification
Email URL with the MFT Internet Server’s IP, Host Name, or DNS name which will be used in email messages URL references when a Transfer Notification email is sent. By default port number 25 has been defined for your email server; if your server is using a different port number simply change the value to the correct port being used. Click the Update button when you have finished.
1.2 Configure your Email URLs
Once you have configured your email server information above you will now want to expand the
Local Settings section on the System Configurations web page. You will see your local MFT server settings. Set the Email URL in this section, which defines the URL that is used in email message URL references when an email is sent. The URL typically points to the IP Name or IP
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
4
Adding Your Email Server to MFT Command Center Quick Start Guide
Address of the Internet Server. If you are working in an environment with multiple Command
Centers/Internet Servers, this may be the address on one of these other servers defined in this field. It does not have to be the local servers address.
5 Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Adding Users
2 Adding Users
In order for users to be able to use MFT Internet Server to transfer files, their User Ids must be added to the MFT Command Center database. The administrative user must have the AdministratorRight or
UpdateTransferUserRight in order to add a User.
Part of the MFT Command Center installation process adds 5 “Template Users” automatically to the database. By clicking on the Add From Existing User link a listing of those pre-existing users will be displayed. Simply click on one of the User Ids to copy the pre-existing user’s definition to a new user definition. The new user definition will have the same Available Rights and contain the same
Optional User Properties of the User Id that was selected. The only thing left to do is to create a unique User Id, add the user’s Full Name, and create a Password for him/her. Click Add when you are finished to have the new user added to the database. You may edit any of the pre-existing user definitions before clicking on the Add button if you wish. As new user definitions are added more template user definitions are available to choose from.
2.1 Adding User Account
Transfer users are MFT Internet Server client end-users who access MFT Internet Server from the web-based file transfer client screens. From the main menu, select Users > Add User.
2.1.1 Required Parameters
1. Insert a User ID that will be used to login to MFT Internet Server/Command Center.
The value cannot exceed 64 characters.
2. Full Name is used for the first and last name of the person on the account. The value cannot exceed 256 characters.
3. Insert a Password for the user to access MFT Internet Server/Command Center and then type the same password in the Confirm Password box. The value cannot exceed 32 characters.
4. Expiration Date that this user’s ID is no longer valid. MFT Command Center defaults to one year from the current date.
5. Valid Days choose which days of the week this user is able to log on to access the system. Make certain that Administrative accounts have adequate access.
6. Valid Start and End Time define the period of time during a day that the user is able to log on to access the system. The default timeframe is a 24-hour period of access.
7. Assigned Rights. When adding a user, the screen sets the default right to
“TransferRight”. Setting this right gives the user authorization to transfer files within the MFT Internet Server. If you want to authorize the user to initiate MFT Platform transfer requests, you must assign “FTTransferRight” to the user. By default the trial license will allow 50 Transfer Users and 50 OnDemand Transfer Users.
2.1.2 Authentication Parameters
1. FTP Client Authentication Method - defines the authentication method when this user accesses Internet Server through an FTP or FTPS client.
2. SSH Client Authentication Method - defines the authentication method when this user accesses Internet Server through an SSH (SFTP) client.
3. HTTPS Client Authentication Method - defines the authentication method when this user accesses Internet Server through an HTTP/HTTPS client.
4. Platform Server Client Authentication Method - defines the authentication method when this user accesses Internet Server through a Platform Server client.
5. Certificate DN - defines the distinguished name from the user's certificate.
Depending on the way that certificates are defined, this field can be used to associate a certificate with a user.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
6
7
Adding Users Command Center Quick Start Guide
2.1.3 Optional Parameters
1. Department is the department to which this user belongs. This would only be used with Delegated Administration.
2. Visibility defines the level of accessibility that other departments have to this user and applies only when using Delegated Administration. The default is private.
3. Description of the user.
4. Company Name the user works for.
5. Phone Number of the transfer user.
6. Start Date / End Date specifies the starting and ending dates during which this user
ID is valid, and can access the system.
7. Client Protocol Allowed indicates the type of protocols which will be allowed for this user while performing this transfer.
8. Disable User will disable a transfer users account which will cause them to fail to login to the system. If they are already logged in when this is enabled they will not be able to conduct a file transfer.
9. LDAP Status defines if and LDAP managed transfer user account is Active or not.
10. Trace Level would normally be turned on at the request of Technical Support in order to troubleshoot a problem. Leave at “No Tracing” during normal operation.
11. Certificate DN is used to define a transfer user’s certificate DN when conducting
SFTP and SSH transfers using certificate authentication.
12. Lock User will lock a users account
13. Can Change Own Password sets whether a user can change their password.
14. Password Never Expires for the transfer user. If the Global Password Rules are in effect this setting will override these.
15. Change Password at Next Login will set the transfer users account to force a password change the next time they login.
16. Email Address is the user’s email address where MFT Command Center will send notification when a file is available to be processed.
17. Restrict User causes this transfer user to be restricted to an IP and/or Netmask to connect.
18. IP Address or IP Name is the IP or Host Name the transfer user is restricted to using to connect to the system.
19. Netmask is the Netmask the transfer user is restricted to be using when connecting to the system.
2.1.4 PGP Information
1. Allow User to Add PGP Key can be set to allow a transfer user using PGP keys to load their PGP Key to the system through the This Client.
2.2 Manage Users
To modify a particular User’s information select Users > Manage Users. This displays the first
100 users defined. It also displays an expandable box that allows you to enter Selection Criteria for the user (or users) that you wish to modify. When you have found the user that you want to modify, click on the “User Id”. This will display the detailed information for that user, when the modification is complete, press the “Update” button to save the modification.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Adding Server Definitions
3 Adding Server Definitions
Server Definitions contain the information that MFT Internet Server/Command Center needs to communicate with the following server types: MFT Platform Server, FTP, Local servers, SSH and
AS2. The Server definition defines how the supported clients can gain access to a file.
Many different Server definitions can be configured within a single MFT Command Center system. MFT Command Center supports five types of Server Definitions. The servers that you define depend on the product that is installed as well as the location of the files needed for file transfer requests. The five Server Types are:
1. Platform Server – This is used by MFT Internet Server and MFT Command Center.
This definition allows Internet Server File Transfer Clients to access files located on an MFT Platform Server. It also allows MFT Command Center to manage and initiate transfers on MFT Platform Servers.
2. Internet Server - Used by the JMS Interface to associate JMS Initiated file transfers with an Internet Server. Note that the IP address associated with an Internet Server can point to a load balancer that forwards requests to a server in a load balanced group. Servers defined as Internet Server are not used for transfers like the other
Server Types.
3. JMS Server - Allow the end user to send files to a JMS Server or receive files from a
JMS Server. Note that the connectivity information for the JMS Server is defined in the "Configure JMS Server" page. The IP Address/IP Name defined in this definition is ignored.
3. FTP Server - (MFT Internet Server Only) - This is used by the MFT Internet Server.
This allows Internet Server File Transfer Clients to access files located on an FTP server.
4. Local Server - This is used by the MFT Internet Server. It allows Internet Server File
Transfer Clients to access files located on the MFT Internet Server.
5. SSH Server - (MFT Internet Server Only) Allows file transfer clients to access files located on an SSH server.
6. AS2 Server - (MFT Internet Server Only) Allows file transfer clients to access files located on an AS2 server.
3.1 Adding a Server Definition
From the main menu choose Servers > Add Server
3.1.1 Required Parameters
1. Type the Server Name for the proxy server. The value cannot exceed 32 characters.
2. Host Name or IP Address of this server. Maximum value is 80 characters.
3. IP Port defines the IP Port of the remote server.
4. The Server Type defines the Server Type that MFT Internet Server/Command
Center will be communicating with. Note: For adding an SSH server type see section
4.1.3 Adding an SSH Server Definition for additional information.
5. The Server Platform defines the type of platform where the Server is executing. The four platforms supported are UNIX, WINDOWS, z/OS and IBM i, UNISYS2200.
3.1.2 Optional Parameters
Expandable boxes define optional Server Definition parameters.
1. Platform Server Options: Contains default Encryption parameters. This setting is only valid when Server Type is Platform Server.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
8
9
2. FTP Options: Defines FTP properties including case sensitivity, connection type, and
SSL options. This setting is only valid when Server Type is FTP.
3. SSH Options: Allows the selection of an SSH key used for authentication to the
SSH Server. This setting is only valid when Server Type is SSH.
4. AS2 Options: Define server options that are only used when Server Type is AS2.
5. Internet Server Options: This section defines the connectivity parameters required for a Command Center to connect to an Internet Server. This is used only when the
Command Center JMS interface connects to Internet Server to initiate an Internet
Server transfer.
6. Server Options: Allows a Server File Name prefix to be defined. This is used only when Server Type is LOCAL. It defines the directory that is prefixed to the Server File
Name defined on the Transfer definition. This allows you to restrict users to access particular directories.
7. Server Credentials: Allows you to define the default Userid and Password for a MFT
Platform server, SSH server and FTP Server.
8. Additional Server Properties: Allows you to define miscellaneous Server definition fields. The Server File Name Prefix is used only when the Server Type is Local. It defines the directory that is the starting point for all Internet Server transfers.
9. Management Options: Defines Server options that are used only when the Server
Type is defined as Platform Server and the MFT Platform Server should be managed by the MFT Command Center.
10. PGP Information: Defines PGP specific information for this server.
3.1.3 Adding an SSH Server Definition
When you add an SSH server definition to MFT Command Center you must retrieve the SSH server’s public key. To do this, follow the instructions below:
1) Navigate to Servers>Manage Servers and click on the link to the SSH server you added earlier with Server Credentials defined in order to log on to the remote SSH server.
2) Notice the Required Server Information section now contains a “Retrieve public key through this server” pull down list and a Retrieve public key from this ssh server link.
3) Select the server you want to use to retrieve the key and click on the Retrieve public key from this ssh server link. The remote SSH server’s public key will be retrieved and written to the MFT database.
4) Click on the Update button to complete the SSH server definition.
3.2 Manage Servers
To modify a particular Server Definition select:
Servers > Manage Servers
This displays all the Server definitions defined to MFT. It also displays an expandable box that allows you to enter Selection Criteria for the Server (or Servers) that you wish to modify. When you have found the Server that you want to modify, click on the “Server Name”. This will display the detailed information for that Server definition, when the modification is complete, press the
“Update” button to save the modifications to the Server definition.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Platform Server Transfers
4 Setting up and Executing MFT Platform
Server to Platform Server Transfers
For this example we will demonstrate initiating an MFT for Windows Platform Server file transfer to an
MFT for Linux Platform Server. Note that this is only one way of configuring this transfer and more options are available. Please contact TIBCO support if more assistance is needed.
4.1 Assigning the proper Rights
Assign the FTAdminRight, FTTransferRight, and UpdateServerRight to an MFT Command Center user. By assigning these rights to an MFT Command Center user account he will gain the ability to Add/Manage Server definitions and Add/Execute Platform Transfers to the MFT Command
Center database.
Navigate to Users > Add User. For this example we created an MFT Command Center user account named PSToPSAdmin and assigned him the rights listed above (Note: Expand the
Optional User Properties window and remove the check mark from “Change Password at Next
Login” to avoid this from occurring.)
4.2 Add Server Definition
Next we need to add the Server definition for the initiating Platform Server.
Navigate to Servers > Add Server. Fill in the Required Server Information fields and then expand the Server Credentials window to add the remote machines login credentials to be used when the transfer is initiated.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
10
Setting up and Executing MFT Platform Server to
Platform Server Transfers
Command Center Quick Start Guide
Note: Assigning the server credentials in the Server definition makes them available for all users in Command Center. Server Credentials can be assigned to be used by specific MFT Command
Center user accounts by navigating to the Server > Server Credentials > Add Server
Credentials web page.
For this example we have defined the windows server information that has MFT for Windows
Platform Server software installed and running:
11
4.3 Add the Platform Server Transfer to DB
Now you must add the Platform Server transfer to the MFT Command Center database.
Navigate to Management > Platform Transfers > Add/Execute Platform Transfers. Define the
Platform Server to Platform Server transfer details.
In the screenshot below we have used the Platform Server details from the Windows Server definition we defined in Step 2 by selecting this server from the drop down menu for the Server
Name parameter. Then we defined the remote MFT for Linux Platform Server details in the
Responder fields and the login credentials by expanding the Credentials and Security Properties window:
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Platform Server Transfers
Note: MFT Platform Server File Name Tokens can be used in the File Name fields.
Note: The login credentials that were defined in the Server definition for the MFT for Windows
Platform Server can be overridden by configuring different login credentials here for the Initiator.
To save the Platform Server transfer to the database for future use click on the Add button. A message similar to the one below will be displayed:
Note: The transfer can simply be executed at this time and it is not necessary to save the transfer definition to the system.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
12
Setting up and Executing MFT Platform Server to
Platform Server Transfers
Command Center Quick Start Guide
4.4 Execute the Platform Server Transfer
Since the Platform Server to Platform Server transfer was saved to the database MFT Command
Center user PSToPSAdmin would navigate to the Management > Platform Transfers > Manage
Platform Transfers and select the transfer definition to execute.
Below the PSToPSAdmin user selects the transfer definition that was saved in Step 3 by clicking on the T51420000001 link:
The Update/Execute Platform Server web page will open:
13
To push the transfer out to the MFT Windows Platform Server exactly as it was defined he would click the Execute From Database button and a message similar to the one below will be displayed:
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Platform Server Transfers
Note: If any changes to the transfer definition were needed the PSToPSAdmin could edit the fields defined and click the Execute button which would allow the transfer to be run but not save the settings to the database. However, he could click the Update button to save the changes to the database.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
14
5 Setting up and Managing DNI Daemons
To manage DNI (Directory Named Initiation) that is located on a Platform Server from an MFT
Command Center you must have the Platform Server defined in a server definition under the
Server menu. Please see Adding a Server Definition from this manual for more information on
Adding a server.
You first need to setup the DNIDeamon on the Platform Server in order to communicate with MFT
Command Center.
Step 1
: Navigate to the DNI directory where you have your Platform Server installed. Open the configuration file DNIConfig.cfg file:
A. Set the port number the DNIDaemon will use to listen for requests coming in from an
MFTCC Server.
B. Set the AcceptIPAddress for the MFTCC server.
C. Assign a user id and password that will be used for the DNIConfig.cfg file by executing the following command: perl DNIDaemon.pl c:DNIConfig.cfg encrypt
D. Execute the DNIDaemon script by using the following command:
perl DNIDaemon.pl c:DNIConfig.cfg
Step 2
: Navigate to the Add Server menu to add the Platform Server you configured above to the MFT Command Center. Be sure to expand the Management Options window to set the DNI port, user Id, and password you configured in Step 1. See our example below:
15
Step 3
: Once the Platform Server has been successfully added with the DNI settings navigate to the Management > Manage DNI Servers web page. You should see the server you added in the
Results table. Note: You must be a Super User or a user with the UpdateServerRight defined in order to manage the DNI Servers. Below is an example of a Linux Platform Server we configured with DNI management:
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Setting up and Managing DNI Daemons
Step 4
: Click on the name of the server under the Server Name column to manage that servers
DNI templates. Below is an example of what you may see:
Any DNI templates that exist on the Platform Server where the DNIDaemon.pl program is being run from will be displayed in the Results Table.
5.1 Add a DNI Template
If you want to create a new DNI template to run you can use the Template Data section as seen in the screenshot below:
The Template Data window is used to Add and Update DNI templates. To add a new one you type in a template name in the Template Name field and paste in the template scheduling data.
An easy way to generate a new DNI template is to click on an existing template from the
Template Name column, then change the template name, and edit the data in the Contents box,
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
16
then click the Add button. To read more about DNI please refer to the Directory Named Initiation
(DNI) Guide.
5.2 Update a DNI Template
To update an existing DNI template you would click on the template from the Template Name column which will display the data in the Template Data window. Make your changes in the
Contents box and then click on the Update button. Updates to a template will not take effect until the DNI template is restarted.
5.3 Start/Stop a DNI Template
To start a DNI template you would click on the Start link. In the screenshot below you see the
Start link for our linux2win.send template:
Once the template is running this link will change to read Stop as seen in the screenshot below:
To stop a DNI template click on the Stop link as seen above.
5.4 Viewing DNI logs
Each DNI template has logs associated with it. A new log is generated each time a template is started. To view a log for a template click on the View Logs link for that template as seen below:
This will bring you into the Manage DNI Server Logs web page as seen in our example below:
17
To view the details of a log you would click on the Template Name for the log you want to view.
You will be asked if you want to save the log or open the log. If you open the log it will be opened in the present browser window. Note: If you right click on the link you can choose to view the log in a new tab or new browser window.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Collecting Platform Server Audit Records
6 Collecting Platform Server Audit Records
MFT Command Center gives the web Administrator the ability to manage remote MFT Platform
Servers. One example of this is the ability to collect audit records from a remote MFT Platform
Servers creating a centralized location to house audit logs for review. The service responsible for this functionality is the Collector Service. This service is used to pull the remote Platform Server audits into the Command Center’s database. These audits can be used to review transfer details, analysis transfer data, and Re-Submit transfers when necessary. Below is an example with steps to follow to configure MFT Command Center to collect a remote MFT Platform Server’s audit records.
6.1 Configure MFT Command Center node
On the MFT Platform Server a node must be configured pointing to the IP address for MFT
Command Center. Read the MFT Platform Server User Guide for more information on creating a node using the cfnode command. For our example we have created a node on a remote
Windows MFT Platform Server as seen below: cfnode - MFT Platform Server Node Definition Maintenance
Utility
Copyright (c) 1995-2013 TIBCO Software Inc. ALL RIGHTS
RESERVED. TIBCO Software
Inc. Confidential Information.
Version 7.1.1
[MFTCC179]
SystemType = LINUX
Protocol = tcpip
HostName = 10.97.142.179
Server = 46464
SSL = N
Compression = NO
Encryption = NO
SecurityPolicy = Default
ResponderProfile = N
Description = MFT Command Center Node
CommandSupport = ALL
6.2 Add Server Definition
Next we need to add a Server definition for the windows MFT Platform Server to MFT Command
Center.
Navigate to Servers > Add Server. Fill in the Required Server Information fields then expand the
Server Credentials window and the Management Options window to add the remote machines login credentials and configure the Collection details for this Platform Server.
Note: Assigning the server credentials in the Server definition makes them available for all users in Command Center. Server Credentials can be assigned to be used by specific MFT Command
Center user accounts by navigating to the Server > Server Credentials > Add Server
Credentials web page.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
18
19
In the screenshot above we have Enabled Manage Platform Server and setup for the Collector to pull the history for both Initiated and Responder transactions that this server has performed.
Since this is the first time this collection will be taking place we set the Collect History to 30 days.
Note:
1) When you set the Collect Platform Server History you will see the following pop-up:
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Collecting Platform Server Audit Records
Click on the OK button. We will be starting the Collector in the next step.
2) The Collect History is used for the first time the Collection Service is run against the
Platform Server and then it is cleared.
3) The Collection Interval can be set here to override the Collection Service default interval of 10 minutes which will be discussed in the next step.
6.3 Start the Collection Service
The Collection Service will collect audit records from any remote MFT Platform Server setup with a Server definition and configured to be managed by Command Center. To configure the
Collections Service navigate to Management > Manage Services > Collection Service >
Configure Collection Service. In our example below the Collector has been Enabled and scheduled to pull records every 30 minutes unless the Collection Interval has been overridden in the Server definition as ours was set to 10 minutes above:
Click on the Update button and then navigate to Management > Manage Services > Collection
Service > Collection Service Status web page. Click on the Start Collector button and then the
Collector Status button and you should see something similar to the following:
Note:
1) Each time a Platform Server is added and configured to have Audits records collected the
Collection Service must be restarted.
2) If the Collect Platform Server History or the Collection Interval is changed in a Server definition or the Default Collection Interval set for the Collection Service the Collection
Service must be restarted.
6.4 View MFT Platform Server Audit Records
To view the Audit records collected from an MFT Platform Server navigate to the Reports >
Audits > Audit Search web page. These audits may be mixed in with other audits contained in the database. All collected Audit records will start with the letter “C” as seen in the example below:
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
20
If you have many Collected Audit records from many Platform Servers you can control what Audit records are displayed by running a detailed search by expanding the Selection Criteria box and filling in the information needed for your search. Please see the on-line help for more information about the fields available in the Selection Criteria box.
To review the details of a Platform Server file transfer click on the Audit Id link.
21 Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Initiate Platform Transfers Using JMS
7 Initiate Platform Transfers Using JMS
MFT can initiate Platform Transfers using JMS. By placing an xml file in the proper queue
(MFT.Transfer in our example) with the proper JMS Type (Platform-Request), MFT Command
Center will do the following:
- Read and parse the xml data
- Initiate a transfer to the Platform Server defined in the xml file.
- Wait for a response and if told to, write a completion message to the JMS queue.
The following example demonstrates how to send a Platform Server transfer request to a JMS
Queue. This example assumes the JMS Service in Command Center has been configured and is started (refer to the Command Center User Guide for more information). It also assumes a JMS queue named “MFT.Transfer has been created in JMS and defined in Command Center JMS
Service configuration along with Platform Server Transfers request type “Platform-Request”.
Step 1: Add Server Type JMS
Navigate to Servers > Add Servers
Fill in the required fields as shown below:
1) Server Name: This can be any name
2) IP address: This is a required field for Add Server. The field is ignored for JMS since the JMS connectivity information is defined by the Command Center.
3) Server Type: Must be JMS
Step 2: Add Transfer definition
Navigate to Transfers > Add Transfers
Fill in the required fields in the sections as shown below:
Required Transfer Information
1) Client File Name: This can be anything.
2) Server File Name: Set this field to the name of the queue you want to write. In this example enter MFT.Transfer.
3) Directory Transfer: Select No.
4) Description: Add a short description.
5) Authorized User Id: Choose the user id from the drop down lists that will be used to make this file transfer. The user must have transfer right.
6) Authorized Group Id: Defines the Internet Server Group ID that is permitted to use this transfer request being defined.
7) Server Name: Select the JMS server defined in step 1.
8) Transfer Direction: Select Upload to Server.
9) Client Protocols Allowed: Set to ALL
10) Department: If you have a department for this transfer to be assigned set it here if not
`leave it blank.
11) Virtual Alias: Add the alias that the client will use for transfers. For this example we will use JMSPlatform.
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
22
23
Additional Transfer Properties (expand this section)
1) Data Type: This field should be set to text.
2) CRLF: This field should be set to no.
JMS Properties (expand this section)
1) Input Selector: Ignored for upload requests.
2) Output JMSType Property: Defines the JMSType Output Property that is set when writing data to a JMS queue. This value must match the “Request Type” from
Management > Manage Services > JMS Service > Configure JMS Service screen under “Transfer Request Properties” “Platform Server Transfers”. In this example
Platform-Request is used.
3) Output Property: Allows you to create a user defined property that is set when writing data to a JMS queue. This field can be left blank.
4) Max Message Size: Specify a maximum message size. (1K-999K, 1M-10M: default=1M)
5) When you are done click on the Add button.
Step 3: Configure the TransferRequest.xml
Fill in the required parameters found in
<MFTCC_Install>
/server/webapps/<context>/example/JMS/
TransferRequestPlatformServer.xml file.
Step 4: Send TransferRequestPlatformServer.xml to the JMS Queue
Go to the transfer client from which the TransferRequestPlatformServer.xml will be sent. The following example assumes a JMS Queue “MFT.Transfer” has been defined as the Queue Name in Management > Manage Services > JMS Service > Configure JMS Service screen under
“Transfer Request Properties”. MFT Platform Server for Windows is the transfer client in this example; however any client could be used.
FTMSCMD /S /F /DS:10.1.1.1 /PORT:46464 /RI=JMSuser /RW=pwd c:\mftxml\TransferPlatformServerRequest.xml JMSPlatform/MFT.Transfer
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Sending Data to a JMS Queue
8 Sending Data to a JMS Queue
The following example demonstrates how to send data to a JMS Queue through Platform Server
Command Line Interface. It requires both MFT Command Center and MFT Internet Server to be installed and sharing the same database and MFT Platform Server for Windows installed. It assumes the JMS Service has been configured and started in MFT Command Center and a JMS queue named, MFT.Queue1, has been created on JMS.
Step 1: Add Server Definition of Server Type JMS
Navigate to Servers > Add Servers
Fill in the required fields as shown below:
1) Server Name: This can be any name
2) IP address: Type the address 127.0.0.1. Note: This is a required field but is ignored for JMS since the JMS connectivity information is defined in the Configure JMS
Service web page.
3) Server Type: Set to JMS
Step 2: Add Transfer Definition
Navigate to Transfers > Add Transfers
Fill in the required fields in the sections as shown below:
Required Transfer Information
1) Client File Name: This can be anything.
2) Server File Name: Set this field to MFT.Queue1. Note: If you want to make this dynamic you can use the #(FileName) token.
3) Directory Transfer: Select No.
4) Description: Add a short description.
5) Authorized User Id: Choose the user id from the drop down list that will be used to make this file transfer. Note: The user must have TransferRight assigned to his user account.
6) Server Name: Select the JMS server defined in step 1.
7) Transfer Direction: Select Upload to Server.
8) Client Protocols Allowed: Set to ALL
9) Department: If you have a department for this transfer to be assigned set it here if not leave it blank.
10) Virtual Alias: Add the alias that the client will use for transfers. In this example use
JMSUP.
Additional Transfer Properties (expand this section)
11) Data Type: Set this value to Text. This tells the system to write Text data to JMS
(Queues used by the BW Interface require Text data). Binary tells the system to write
Byte data to JMS
12) CRLF: Tells the system how to handle record delimiter
No All data will be written to JMS as a single message.
Yes Data will be split into individual JMS Messages when CRLF is found
LF Data will be split into individual JMS Messages when LF is found
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
24
Sending Data to a JMS Queue Command Center Quick Start Guide
JMS Properties (expand this section)
13) Input Selector: Ignored for upload requests.
14) Output JMSType Property: Set to JMSUpload. Defines the JMS Type Output Property that is written when the file is sent to the JMS queue.
15) Max Message Size: Specify a maximum message size. (1K-999K, 1M-10M: default=1M).
When a message exceeds this size it will be broken up into multiple messages.
16) When you are done click on the Add button.
Step 3: Send data from client to the JMS Queue
Open the Command Prompt and navigate to the Platform Server’s Command Line Interface.
Below is a command using the settings above to send the file to JMS:
ftmscmd /send /file /destination:10.97.142.154 /port=46464 /remoteuserid=jmsuser
/remotepassword=pwd c:\outgoing\testfile.txt JMSUP/MFT.Queue1
Note: Due to the transfer definition parameter, Client Protocols Allowed, being set to ALL this upload can also be performed by an FTP Client, an SSH Client, the Thin Client, and the Desktop
Client if configured.
25 Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
Command Center Quick Start Guide Receiving Data from a JMS Queue
9 Receiving Data from A JMS Queue
The following example demonstrates how to receive data from a JMS Queue. This example assumes the JMS Service in Command Center has been configured and is started (refer to the
Command Center User Guide for more information). It also assumes a JMS queue named
“MFT.Queue1 has been created in JMS.
Note: Sending data to a JMS Queue requires both MFT Command Center and Internet Server.
Step 1: Add Server Type JMS
Navigate to Servers > Add Servers
Fill in the required fields as shown below:
1) Server Name: This can be any name
2) IP address: This is a required field for Add Server. The field is ignored for JMS since the JMS connectivity information is defined by the Command Center.
3) Server Type: Must be JMS
Step 2: Add Transfer definition
Navigate to Transfers > Add Transfers
Fill in the required fields in the sections as shown below:
Required Transfer Information
1) Client File Name: This can be anything.
2) Server File Name: Set this field to the name of the queue you want to write. If you want to make this dynamic you can use the #(FileName) token. In this example enter
MFT.Queue1.
3) Directory Transfer: Select No. Downloads require transfers to be file transfer not directory.
4) Description: Add a short description.
5) Authorized User Id: Choose the user id from the drop down lists that will be used to make this file transfer. The user must have transfer right.
6) Server Name: Select the JMS server defined in step 1.
7) Transfer Direction: Select Download to Client.
8) Client Protocols Allowed: Set to ALL
6) Department: If you have a department for this transfer to be assigned set it here if not leave it blank.
7) Virtual Alias: Add the alias that the client will use for transfers. In this example use
JMSDOWN.
Additional Transfer Properties (expand this section)
8) Data Type: This field is ignored when reading from a JMS queue.
9) CRLF: Tells the system how to handle record delimiter
No All messages will be read from JMS and written as a single record
Yes CRLF delimiters will be added at the end of each JMS message read
LF LF delimiters will be added at the end of each JMS message read
Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
26
JMS Properties (expand this section)
10) Input Selector: Filters data when reading a JMS Queue. Default is to read all data in a queue.
11) Output JMSType Property: This parameter is ignored on download requests and can be left blank.
12) Output Property: This parameter is ignored on download requests and can be left blank.
13) Max Message Size: This field is ignored on a download.
14) When you are done click on the Add button.
Step 3: Receive data from the JMS Queue to a client
Go to the client from which the data will be sent. The following example assumes a JMS Queue
“MFT.Queue1” has been defined in JMS. FTP Command Line is the client in this example; however any client could be used.
FTP to the MFT Internet Server and authenticate with the JMSuser credentials get /JMSDOWN/MFT.Queue1 c:\test.txt
27 Copyright © TIBCO Software Inc. 2003 – 2015. All Rights Reserved.
ಡೌನ್ಲೋಡ್ ಮಾಡಿ
ಸಾರ್ವಜನಿಕ ಲಿಂಕ್ ನವೀಕರಿಸಲಾಗಿದೆ
ನಿಮ್ಮ ಚಾಟ್ಗೆ ಸಾರ್ವಜನಿಕ ಲಿಂಕ್ ಅನ್ನು ನವೀಕರಿಸಲಾಗಿದೆ. You may view and manage your chat links after registration here.
ದಾಖಲೆಯ ಸಾರ್ವಜನಿಕ ಲಿಂಕ್
ಜಾಹಿರಾತು