Thursday, July 4, 2013

While exploring machine translation service in SharePoint
2013 I got the issue saying that “immediate translations for machine
translation service are disabled”. In SharePoint 2013, many features are
depending on the machine translation service synchronous mode. If immediate translations
disabled in the machine translation service all those features will not
function as expected.

In “Maximum number of synchronous translation requests (per
server)” text box in “Maximum Synchronous Translation Requests” section, enter
the values from 1-300. If the value is “0”, then the synchronous transactions
are disabled.

Wednesday, June 26, 2013

Previous post, I have mentioned how to create new machine
translation service. After creating the machine translation service we can
configure the service. We can do this by using Central Administration or Power Shell commands.

By Using Central Admin, Go to Application Management ->
Manage Service Applications

Select Machine Translation Service

In the machine translation service page, “Enable File
Extensions” section, check the file types that we want to translate. If we
uncheck any of the check box that file type will disable for translation.

In “Item Size Limits” section we have three text boxes for
size limit,

“Maximum file size of binary files in KB. Microsoft Word
documents are binary files” box for Microsoft word document size. The range is
between 100-524288. Default value is 51200. Files more than that size will not
be translated.

“Maximum file size of text files in KB. Plain-text, HTML, and
XLIFF documents are text files” box for plain text, HTML docs, XLIFF documents.
The range is between 100-15360. Default value is 5120. Files more than that
size will not be translated.

“Maximum character count for Microsoft Word document” box
for word document. The range is between 10000-10000000. Default value is 500000.
Files more than that size will not be translated.

“Online Translation Connection” Section will help Machine
Translation service to connect online transaction service. Default is “Use
default internet settings”. If we select “Use proxy specified”, we have to
enter proxy server name and port number. If we select “Use proxy specified”
option, we have to restart Machine translation service.

“Translation Processes” section allows us to specify the
number of transaction processes created on the each service application. This
value equals to the number of translations that process simultaneously. Default
value is “1”. If we change the value, we have to restart the service.

In “Translation Throughput” section allows us to specify the
frequency with which groups of translations are started and the number of
translations within each group. we have two text boxes,

In “Frequency with which to start translation” text box, we
have to specify the frequency that which groups of translations to be started. Range
is 1-59. Default value is 15.

In “Number of Translation to start” text box, we have to
mention the number of translations per process. This specifies that the number
of translation started per process every time translations are started. Range is
1-1000 and default value is 200.

“Maximum Translation Attempts”
section represents the number of times a translation tried before its status
set to fail. Range is 1-10 and default value is 2.

In “Maximum Synchronous Translation Requests”, we have to
specify the maximum number of synchronous transaction requests that processed
at a time on each server for service application. Range is between 0-300.
Default value is 10.

“Translation Quota” section limits the usage of the service
queue mode for high throughput values. We have two sections here.

In “Maximum number of items which can be queued within 24-hour
period”, No limit is the default. If we select Limit per 24 hours, we have to
type the maximum of number of items that can be queued in 24-hour period. The value
must be between 100-1000000.

“Maximum number of items which can be queued within a
24-hour period per site subscription” No limit is the
default. If we select Limit per 24 hours, we have to type the maximum of number
of items that can be queued in 24-hour period per site subscription. The value
must be between 100-1000000.

“Completed Job Expiration time” specifies the expiry time
for the completed job history. Value range is 1-1000 and default value is 7
days. We can select “No expiration” without expiry.

“Recycle Threshold” specifies the number of documents
translated by a translation process before it is restarted. Value range is
1-1000 and default value is 100. If we change this value, we have to restart
the service.

“Office 97-2003 Document Scanning” specifies whether we need
to disable security scanning for 97-2003 office documents. We have to enable
this setting only when trust the documents to be converted. Default value is “No”.
Click on “OK” to save the configurations.

By Using Power Shell script we can configure the Machine translation
service, here is the script do that,

We have to check Office Web Apps and an Internet connection on our front-end
servers are properly configured or not. Once we check that by navigating in to
documents, select and open the document using office web app.

In the info section we can “Translate” option to translate the
document.

By clicking that we can see the prompt to change the
language as shown the image below.

Tuesday, June 25, 2013

In SharePoint server 2013 we have many new service
applications. Machine Translation service is one of the new in service
applications. It allows us to translate the site and user content. This service
will have a list of APIs, REST and Client Side Object Model support. By using
API’s content can pre-translate when required or content can be translated on
the fly by the users. Here the process will happen Asynchronously,
Synchronously or using streaming.

Machine translation service will translate the text from one
language to another language. Here the translation process will happened by
using cloud-hosted machine translation service. Machine translation service
will share many components with word automation service timer jobs, Documents
Queue etc. Here is the simple image that explaining Machine translation
service.

Machine translation service will process the translation
requests asynchronously and synchronously. Jobs that submitted to the machine
translation service will process synchronously when translation timer job
executes configurable. Default interval for this is 15 min. We can translate
Asynchronous requests manually by running SharePoint translation Service timer
jobs through Central Admin or using Power Shell script.

We can create new Machine translation service by using
the steps below,

In the “Create New Machine Translation Service Application
form”, enter the Name. In the Application Pool section, if we want to use
existing application, we can select “Use existing application pool”, and select
the app pool wanted to use. Else, Create new Application Pool. In my case Iam creating
new App pool. The account using for App pool must have the full permissions to
User Profile service application.

In the “Partitioned Mode”, we have to select “Run in
partitioned mode” if we are going to provide hosting services for other sites.
Select “Add this service application’s proxy to the farm’s default proxy list”
in the “Add to Default Proxy List” section. When we have multiple web
applications and wanted to use them in different set of services, we don’t have
to check the check box.

In the Database section, we have to specify the DB server
name, DB name and authentication methods. Click on “OK” button.

We can configure the Machine translation service by using
the Power Shell script below,

Here
ServiceAppName is the name of the Translation service, DBName is the database
name for translation service, DBServerName is name of the DB server,
AppPoolName is application pool name. Here
is the sample script to create new translation service,

Follow us in facebook

About Me

Having good experience in SharePoint 2007/2010 and .net applications. Currently, working on SharePoint 2013 and training people on SharePoint. Microsoft certified technology specialist, Microsoft Certified Professional developer in SharePoint 2010.