Настройка автоматического запуска сервера приложений WebSphere в Windows

1. Необходимо настроить автоматический запуск ноды (сервис Windows)
2. Настройка запуска сервера в WAS

Отслеживание хода исполнения паспорта, Конфигурирование последовательности действий в карте хода выполнения

Отслеживание хода исполнения паспорта

Ход исполнения паспорта показывается двумя способами: на карте хода выполнения как строка узлов в разделе Карта хода выполнения окон прикладных программ Инциденты, Проблемы и Заявки на услуги; как значение в поле Состояние. На карте хода выполнения подсвечен узел, который представляет действие, выполняемое в настоящее время.

Значение Состояние можно изменить вручную, выбрав действие Изменить состояние. Кроме того, чтобы отразить новое состояние, обновляется карта хода выполнения.

По умолчанию последовательность действий на Карте хода выполнения определяется свойствами системы. Вы можете переопределить последовательность действий в этих свойствах системы, чтобы глобально изменить последовательность действий на Карте хода выполнения.

Значения состояния содержатся в доменах SRSTATUS, INCIDENTSTATUS и PROBLEMSTATUS (для приложений Заявки на услуги, Инциденты и Проблемы соответственно). Чтобы просмотреть используемые состояния, перейдите в прикладную программу Домены (Перейти > Конфигурация системы >Конфигурация платформы > Домены), введите SRSTATUS, INCIDENTSTATUS или PROBLEMSTATUS в поле Домен и нажмите клавишу Enter. Значения в этих доменах используются для заполнения Карты хода выполнения.

IBM Maximo® Version 7 Portrait Report Templates

MaximoPortraitReportTemplates.rar

Version:

 7.1.1.5 and later, 7.5 and later

Description:

IBM® Maximo® delivers landscape report templates to enable clients to create custom reports.  Landscape templates are delivered so the maximum number of fields can be displayed on a report.

However, to enable clients to meet their unique business needs, a set of portrait report templates is provided here.

Useful java class: GetStartFinishDateTimeOfWeekOfDay

package custom;
import java.util.Date;
import java.util.Locale;

import com.ibm.icu.util.Calendar;

public class GetStartFinishDateTimeOfWeekOfDay {

  public static Date GetStartDateTimeOfDay(Date reportDate) {

   Calendar cal = Calendar.getInstance(new Locale("ru", "UA"));
   cal.setTime(reportDate);
   cal.set(Calendar.MILLISECONDS_IN_DAY, 0);
   reportDate = cal.getTime();

   return reportDate;

  }

  public static Date GetFinishDateTimeOfDay(Date reportDate) {

   Calendar cal = Calendar.getInstance(new Locale("ru", "UA"));
   cal.setTime(reportDate);
   cal.set(Calendar.MILLISECONDS_IN_DAY, 86399999);
   reportDate = cal.getTime();

   return reportDate;

  }

  public static Date GetStartDateTimeOfWeek(Date reportDate) {

   Calendar cal = Calendar.getInstance(new Locale("ru", "UA"));
   cal.setTime(reportDate);
   cal.setFirstDayOfWeek(Calendar.MONDAY);
   cal.set(Calendar.DAY_OF_WEEK, Calendar.MONDAY);
   cal.set(Calendar.MILLISECONDS_IN_DAY, 0);
   Date startWeekDate = cal.getTime();

   return startWeekDate;

  }

  // last day is Sunday
  public static Date GetFinishDateTimeOfWeek(Date reportDate) {

   Calendar cal = Calendar.getInstance(new Locale("ru", "UA"));
   cal.setTime(reportDate);
   cal.setFirstDayOfWeek(Calendar.MONDAY);
   cal.set(Calendar.DAY_OF_WEEK, Calendar.SUNDAY);
   cal.set(Calendar.MILLISECONDS_IN_DAY, 86399999);
   Date finishWeekDate = cal.getTime();

   return finishWeekDate;

  }

  // last day is Friday
  public static Date GetFinishDateTimeOfWeek_Work(Date reportDate) {

   Calendar cal = Calendar.getInstance(new Locale("ru", "UA"));
   cal.setTime(reportDate);
   cal.setFirstDayOfWeek(Calendar.MONDAY);
   cal.set(Calendar.DAY_OF_WEEK, Calendar.FRIDAY);
   cal.set(Calendar.MILLISECONDS_IN_DAY, 86399999);
   Date finishWeekDate = cal.getTime();

   return finishWeekDate;

  }

}

Hide data conditionally for a specific group

A very typical customization task is to restrict the visibility of data within Maximo/TPAE applications based on certain conditions.
For example you may wish to hide all the purchase orders that have a total costs higher than 1000$ for a specific group. Here is a small tutorial about how you can achieve this.

Open Administration - Conditional Expression Manager application and create the following conditional expression.

• Condition: POCOST
• Description: Total cost is less than 1000
• Type: EXPRESION
• Expression: totalcost<1000

Now go to the Security - Security Groups application. Choose the desired group and open theData Restrictions tab.
Create the following Object Restriction:

• Object: PO
• Type: QUALIFIED
• Reevaluate: true
• Condition: POCOST

If you now logon with a user belonging to the chosen group and open the Purchase Orders application you will see that only POs with a total cost of less than 1000 will be listed.

There are three types of object restrictions that may be used to accomplish different goals:

• Hidden: The objects for which the condition is evaluated to true will be displayed as XXXXX and cannot be selected.
• Qualified: The objects for which the condition is evaluated to false will be hidden.
• Readonly: The objects for which the condition is evaluated to true cannot be updated.

MxLoader - Extract and load data in Maximo with ease

MxLoader is a Microsoft® Excel® spreadsheet that allows to quickly and easily query and load data into IBM Maximo, IBM SmartCloud Control Desk (SCCD) and other TPAE based applications. It brings together the power of the Maximo Integration Framework and the flexibility of Excel allowing to quickly manipulate and import data into any Maximo database. MxLoader runs on Microsoft Excel 2007/2010. It also requires Microsoft XML Core Services 6.0.

Download MxLoader

Deleting user-created applications

• Only applications created with Application Designer can be deleted (new or duplicated).
• You must use a database editor to delete an appli cation.
• Deleting an application does not remove a ny custom tables, fields, or domains created to support the application.
• The application server must be shut down before the application is deleted.

To delete an application, log in to a database editor. Type the following commands in the database editor. Replace the variable <APPLICATION NAME> with the name of the application that you want to delete. The application name must be all uppercase.

delete from maxapps where app='APPLICATION NAME';
delete from maxpresentation where app='APPLICATION NAME';
delete from sigoption where app='APPLICATION NAME';
delete from applicationauth where app=''APPLICATION NAME';
delete from maxlabels where app=''APPLICATION NAME';
delete from maxmenu where moduleapp='APPLICATION NAME' and  menutype !='MODULE';
delete from maxmenu where moduleapp='APPLICATION NAME' and  elementtype='APP' and keyvalue='APPLICATION NAME';
delete from appdoctype where app='APPLICATION NAME'';

The application is deleted from the database. Log out of the database editor.