Revision as of 20:08, 29 October 2019

Vamos realizar a instalação do Perimeter Server.

Procedimento

Arquivos necessários ps_NNNNNNN.jar

Durante a criação deste artigo as versões dos arquivos disponíveis para a instalação são: ps_6000200.jar ou ps_4060400.jar.

Este arquivo é obtido no IBM Sterling B2Ni

Versão padrão: Usar o comando

cp <install_dir>/packages/ps_6000200.jar .

Versão docker: Usar o comando

docker cp b2bii:/ibm/b2bi/install/packages/ps_6000200.jar .

Preparando o arquivo de Resposta

1) Criar o arquivo silent.txt

2) Altere os valores

INSTALL_DIR=
REVERSE_CONNECT=Y
PS_PORT=
PS_SECURE_IF=
PS_EXTERNAL_IF=
MAX_JVM_HEAP=
REMOTE_ADDR=
REMOTE_PORT=

Instalação do Perimeter Server

Executar o comando

/bin/java -jar /<install_dir>/packages/<ps_filename>.jar -f silent.txt

Ajustes pós instalação

Configurando permissões para o Backend server

Edite o arquivo restricted.policy, e adicione os servidores de backend (Sterling B2B) que irão fazer proxy por esses servidores.

Exemplo:

// To restrict or permit the required Host/Server to communicate with the PS, update the “ftphost/htttphost/snode” with that of the Server IP and provide the appropriate PORT number where the Server will listen. //

// For each target FTP Server
permission java.net.SocketPermission "10.117.15.87:33001", "connect"; // Control connection.
permission java.net.SocketPermission "10.117.15.87:lowPort-highPort", "connect"; // Passive data connections.
// 10.117.15.87 indicates IP of the FTP Server for which the permission is granted by PS for communicating with client //

// For each target HTTP Server //
permission java.net.SocketPermission "10.117.15.87:33002", "connect";
// 10.117.15.87 indicates IP of the HTTP Server for which the permission is granted by PS for communicating with client //

// For each target C:D snode //
permission java.net.SocketPermission "snode:1364", "connect";
//  10.117.15.87 indicates IP of the Connect Direct Node for which the permission is granted by PS for communication //

Iniciando e Parando o Perimeter Server

Após a instalação executar os comandos abaixo para o Sterling B2B:

cd <INSTALL_DIR>

Iniciar:

./startupPs.sh ou  ./startPSService.sh

Parar

./stopPs.sh ou ./stopPSService.sh

Ver também

@@ Line 46: / Line 46: @@
   <small>// To restrict or permit the required Host/Server to communicate with the PS, update the “ftphost/htttphost/snode” with that of the Server IP and provide the appropriate PORT number where the Server will listen. //</small>
-  ''// For each target FTP Server''
+  <small>// For each target FTP Server</small>
   permission java.net.SocketPermission "10.117.15.87:33001", "connect"; // Control connection.
   permission java.net.SocketPermission "10.117.15.87:lowPort-highPort", "connect"; // Passive data connections.
-  ''// 10.117.15.87 indicates IP of the FTP Server for which the permission is granted by PS for communicating with client //''
+  <small>''// 10.117.15.87 indicates IP of the FTP Server for which the permission is granted by PS for communicating with client //''</small>
-  // For each target HTTP Server
+  <small>// For each target HTTP Server //</small>
- //
   permission java.net.SocketPermission "10.117.15.87:33002", "connect";
-  // 10.117.15.87 indicates IP of the HTTP Server for which the permission is granted by PS for communicating with client //
+  <small>// 10.117.15.87 indicates IP of the HTTP Server for which the permission is granted by PS for communicating with client //</small>
-  // For each target C:D snode
+  <small>// For each target C:D snode //</small>
- //
   permission java.net.SocketPermission "snode:1364", "connect";
-  //  10.117.15.87 indicates IP of the Connect Direct Node for which the permission is granted by PS for communication //
+  <small>//  10.117.15.87 indicates IP of the Connect Direct Node for which the permission is granted by PS for communication //</small>
 = Iniciando e Parando o Perimeter Server=