Ir al contenido principal

What Ports are being used by the Sage X3 Solution

Fuente original: SAGE

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=222924350018644 

Creado el  | Última modificación el 

Resumen

What Ports are being used by the Sage X3 Solution

Descripción

Causa

  • Ports or network traffic may be blocked by an anti-virus

  • Ports can be blocked by the router or firewall

Solución

 CAUTION: This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions. 

  • The X3 Console will also typically display port information for each X3 component.

  • Some commonly used ports are listed in the table below

PortServiceManaged By Server(typical

1433

SQL InstanceLocal SystemDatabase Server
80Apache(X3 Documentation and X3_PUBS)User AccountApplication Server
1818ADXADMINUser AccountAll Servers
28880X3 WebUser AccountWeb Server
28843SSL X3 WebUser AccountWeb Server
1890X3 Print ServiceUser AccountApplication Server
1805/1806X3 RuntimeUser AccountApplication Server
25SMTP(workflows)Local SystemApplication Server
389LDAPLocal System  Application Server

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  Delete ,  R
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  server  specified in the command. When sending is launched by a work
Leer más

How to upload a file from the client?

You may have a need to upload a file to the server, and in the past you may have used COPSRV routine from ORDSYS. On V6 the limit that this routine had was that, you did not know the file name of the file that is getting transferred to the server, and you had to define the file name for the destination.  But things have changed on newer version. Before we get to the example review online help title "How to manage files in the storage area"  As you noted in the online help, in the new version COPSRV will copy the file to server TMP directory. So in below example I am going to use another routine MOVE from ORDSYS to move the file to my desired location. In this example, I am adding a button to Sales order, for transferring the file. Open  Development, Script dictionary, Windows. Select  OSOH  window. Add a new button.  Save  and  Validate. Open  Setup, Sales, Entry transactions, Orders. Validate  the entry transaction. Now open  Development, Scr
Leer más